Configure VM Manager Tool stuck in running for too long

Hello,

I’m having some problems while adding VCenters using the VM Managers panel in BFI.
In the past months, I was able to correctly add different VCenters without any problems (using the IBM documentation at this link: https://www.ibm.com/support/knowledgecenter/en/SSKLLW_9.5.0/com.ibm.bigfix.inventory.doc/Inventory/admin/t_adding_new_vm_managers.html), but recently I’ve been having the following issue:
when adding different VCenters, the action fails. Also, when trying to add multiple VCenters at the same time, the first “Configure VM Manager Tool” action state gets to Running while the others are stuck in Evaluating and in the end all VCenters remain in Pending on the VM Manager panel.

Looking at the VMMAN logs, that’s what I could find:

2019-10-09 21:21:36 : (pool-1-thread-6) com.ibm.license.mgmt.datacollector.tasks.VMCollectorTask::processTask():com.ibm.license.mgmt.util.vmmanager.exception.VmManagerException: com.sun.xml.internal.ws.client.ClientTransportException: Errore di trasporto HTTP: javax.net.ssl.SSLHandshakeException: java.net.SocketException: Software caused connection abort: socket write error
	at com.ibm.license.mgmt.vmmanager.vmware.VMwareConnector.disconnect(VMwareConnector.java:115)
	at com.ibm.license.mgmt.datacollector.tasks.VMCollectorTask.processTask(VMCollectorTask.java:168)
	at com.ibm.license.mgmt.datacollector.tasks.CollectorTask.process(CollectorTask.java:89)
	at com.ibm.license.mgmt.scheduler.impl.SchedulerServiceImpl$TimerListenerImpl.runTask(SchedulerServiceImpl.java:245)
	at com.ibm.license.mgmt.scheduler.impl.SchedulerServiceImpl$TimerListenerImpl.timerExpired(SchedulerServiceImpl.java:228)
	at com.ibm.license.mgmt.scheduler.timemanager.impl.TimerManagerImpl$TimerImpl.run(TimerManagerImpl.java:88)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:522)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:319)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:191)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.lang.Thread.run(Thread.java:812)
Caused by: com.sun.xml.internal.ws.client.ClientTransportException: Errore di trasporto HTTP: javax.net.ssl.SSLHandshakeException: java.net.SocketException: Software caused connection abort: socket write error
	at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:129)
	at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:220)
	at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:142)
	at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:107)
	at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:1133)
	at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:1047)
	at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:1016)
	at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:874)
	at com.sun.xml.internal.ws.client.Stub.process(Stub.java:460)
	at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:190)
	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:105)
	at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
	at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:159)
	at com.sun.proxy.$Proxy38.logout(Unknown Source)
	at com.ibm.license.mgmt.vmmanager.vmware.VMMServiceConnection.disconnect(VMMServiceConnection.java:107)
	at com.ibm.license.mgmt.vmmanager.vmware.VMwareConnector.disconnect(VMwareConnector.java:112)
	... 12 more
Caused by: javax.net.ssl.SSLHandshakeException: java.net.SocketException: Software caused connection abort: socket write error
	at com.ibm.jsse2.k.a(k.java:42)
	at com.ibm.jsse2.av.a(av.java:688)
	at com.ibm.jsse2.D.a(D.java:495)
	at com.ibm.jsse2.D.a(D.java:534)
	at com.ibm.jsse2.E.a(E.java:519)
	at com.ibm.jsse2.D.r(D.java:444)
	at com.ibm.jsse2.D.a(D.java:399)
	at com.ibm.jsse2.av.a(av.java:1006)
	at com.ibm.jsse2.av.i(av.java:574)
	at com.ibm.jsse2.av.a(av.java:280)
	at com.ibm.jsse2.av.startHandshake(av.java:431)
	at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:167)
	at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:62)
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1346)
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1321)
	at com.ibm.net.ssl.www2.protocol.https.b.getOutputStream(b.java:53)
	at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:116)
	... 27 more
Caused by: java.net.SocketException: Software caused connection abort: socket write error
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:122)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:166)
	at com.ibm.jsse2.d.a(d.java:170)
	at com.ibm.jsse2.d.a(d.java:89)
	at com.ibm.jsse2.av.b(av.java:175)
	at com.ibm.jsse2.av.a(av.java:556)
	at com.ibm.jsse2.av.a(av.java:806)
	at com.ibm.jsse2.D.a(D.java:308)
	at com.ibm.jsse2.E.c(E.java:62)
	at com.ibm.jsse2.E.a(E.java:70)
	at com.ibm.jsse2.E.a(E.java:114)
	... 39 more

Is there some problem with the VM Manager Tool?

Thanks in advance for the help.

are you able to reach the vm managers from the bigfix server or whichever server you installed the vm managed tool on? You can open a browser and try opening the vm manager url.

Hello Rohit,

it appears that the issue got resolved recently.
There seemed to be a problem with the BigFix Server network traffic overload, unrelated with the VM Manager Tool itself.

Thanks anyway.