Dear Guru’s,
Every now and then I noticed that our scheduled job doesn’t run due to KNIME Executor dies.
Below is the error message in the log. I would then need to restart the service in order to make it works again. Any idea how to prevent this?
We’re using Server version 4.14.1/Connector 4.14.2 in Windows
ERROR : pool-3-thread-1 : : CoreTokenHandler : : : Could not refresh core tokens: connection is already closed due to connection error; cause: java.net.SocketException: Connection reset
com.rabbitmq.client.AlreadyClosedException: connection is already closed due to connection error; cause: java.net.SocketException: Connection reset
at com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:257)
at com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:426)
at com.rabbitmq.client.impl.ChannelN.basicPublish(ChannelN.java:704)
at com.rabbitmq.client.impl.ChannelN.basicPublish(ChannelN.java:679)
at com.rabbitmq.client.impl.ChannelN.basicPublish(ChannelN.java:669)
at com.rabbitmq.client.impl.recovery.AutorecoveringChannel.basicPublish(AutorecoveringChannel.java:192)
at com.knime.enterprise.executor.amqp.RabbitMQMessagePublisher.publishMessage(RabbitMQMessagePublisher.java:61)
at com.knime.enterprise.executor.amqp.CoreTokenHandler.acquireTokens(CoreTokenHandler.java:116)
at com.knime.enterprise.executor.amqp.CoreTokenHandler.refreshTokens(CoreTokenHandler.java:190)
at com.knime.enterprise.executor.amqp.CoreTokenHandler.lambda$1(CoreTokenHandler.java:200)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)