Raghav B (Customer) asked a question.
<DATE> 1:24:48 PM PDT SEVERE [com.boomi.util.retry.Retryable call] Connect to LocalWorkerJvm[<ACCOUNT ID>:worker-<WORKER-ID>-<DATE>]: <IP ADDRESS>:20001 (INIT) failed, will retry after backoff: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: <IP ADDRESS>; nested exception is:
java.net.ConnectException: Connection refused (Connection refused)]
<DATE> 1:27:12 PM PDT SEVERE [com.boomi.util.LogUtil doLog] Failed launching new worker worker-<WORKER-ID>-<DATE> for Account[<ACCOUNT ID>]
java.util.concurrent.TimeoutException: Timed out waiting for LocalWorkerJvm[<ACCOUNT ID>:worker-<WORKER-ID>-<DATE>]: <IP ADDRESS>:20001 (INIT) startup
at com.boomi.execution.forker.worker.WorkerPool.launchNewWorkerImpl(WorkerPool.java:641)
at com.boomi.execution.forker.worker.WorkerPool.access$100(WorkerPool.java:69)
at com.boomi.execution.forker.worker.WorkerPool$3.run(WorkerPool.java:575)
at com.boomi.util.ExecutorUtil$CCLRunnable.run(ExecutorUtil.java:765)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: com.boomi.execution.forker.worker.AccountWorkers$ConnectException: Could not connect to <IP ADDRESS>:20001
at com.boomi.execution.forker.worker.AccountWorkers$WorkerJvm.createConn(AccountWorkers.java:1229)
at com.boomi.execution.forker.worker.AccountWorkers$WorkerJvm.getWorker(AccountWorkers.java:1122)
at com.boomi.execution.forker.worker.WorkerPool.launchNewWorkerImpl(WorkerPool.java:635)
... 6 more
Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: <IP ADDRESS>; nested exception is:
java.net.ConnectException: Connection refused (Connection refused)]
at java.management.rmi/javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:370)
at java.management/javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
at java.management/javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:229)
at com.boomi.execution.forker.worker.AccountWorkers$WorkerJvm$1.execute(AccountWorkers.java:1182)
at com.boomi.execution.forker.worker.AccountWorkers$WorkerJvm$1.execute(AccountWorkers.java:1177)
at com.boomi.util.retry.Retryable.call(Retryable.java:93)
at com.boomi.execution.forker.worker.AccountWorkers$WorkerJvm.createConn(AccountWorkers.java:1227)
... 8 more
Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: <IP ADDRESS>; nested exception is:
java.net.ConnectException: Connection refused (Connection refused)]
at jdk.naming.rmi/com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:137)
at java.naming/com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.java:207)
at java.naming/javax.naming.InitialContext.lookup(InitialContext.java:409)
at java.management.rmi/javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1839)
at java.management.rmi/javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1813)
at java.management.rmi/javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:302)
... 14 more
Caused by: java.rmi.ConnectException: Connection refused to host: <IP ADDRESS>; nested exception is:
java.net.ConnectException: Connection refused (Connection refused)
at java.rmi/sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:623)
at java.rmi/sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:209)
at java.rmi/sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:196)
at java.rmi/sun.rmi.server.UnicastRef.newCall(UnicastRef.java:343)
at java.rmi/sun.rmi.registry.RegistryImpl_Stub.lookup(RegistryImpl_Stub.java:116)
at jdk.naming.rmi/com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java:133)
... 19 more
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:412)
at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:255)
at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:237)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.base/java.net.Socket.connect(Socket.java:609)
at java.base/java.net.Socket.connect(Socket.java:558)
at java.base/java.net.Socket.<init>(Socket.java:454)
at java.base/java.net.Socket.<init>(Socket.java:231)
at java.rmi/sun.rmi.transport.tcp.TCPDirectSocketFactory.createSocket(TCPDirectSocketFactory.java:40)
at java.rmi/sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:617)
... 24 more
Hi,
Are you able to share more context? Have workers ever worked in this cloud or is it new? This error could be thrown for any number of reasons. It either means something is not allowing the connection (ie firewall), the worker failed to spin up, the worker is taking too long to spin up, or the worker launcher never even worked/started the spin up. Are there any worker logs for this worker? When you are on that machine, do you see a JVM spin up? Since it is a local worker, it is probably less likely the network(though not impossible). Just this error is not going to help get the root cause though.
Thank you,
Matt
Hi Matt,
We have opened a support case with Boomi Support and provided all the logs. if possible take a look at the case
AS updated in a new comment Atom Worker is trying to re use a port causing the issue.
Here the problem is Atom Worker is trying to use an already in use port: 20001 , since the port is already in use , it in not allowing to use it and failing to launch atom worker and timing out.
to better understand the problem you need to check on server side what is happening with ports and associated process.
why Boomi Atom worker is trying to use a port which is already in use.
And we see the one Atom worker is using two ports. we are seeing the issue on two different environments on daily basis. it is causing lot of issues.
@Raghav B (Customer)
Given the Support Case it is probably best to continue working through Support to drive this resolution. I have reached out to Support with a few observations and they should be in touch shortly.
Thank you!
Matt