Gateway Events Are Going To Error State with JMSException
(Doc ID 1568091.1)
Last updated on APRIL 04, 2022
Applies to:
Oracle Communications MetaSolv Solution - Version 6.0.16 and laterInformation in this document applies to any platform.
Symptoms
Gateway events are going to error state with the below exceptions in the logs.
javax.jms.JMSException: Destination is closed. Attempted to reconnect 5 times with the following results: java.lang.NullPointerException
at com.mslv.integration.messaging.JmsSender.send(JmsSender.java:75)
at com.mslv.integration.handlers.OutboundEventHandler.sendOutboundMessage(OutboundEventHandler.java:97)
at com.mslv.integration.IntegrationManager.processOutbound(IntegrationManager.java:200)
at com.mslv.integration.integrationServer.IntegrationServerConsumer.executeEvent(IntegrationServerConsumer.java:268)
at com.mslv.integration.integrationServer.IntegrationServerConsumer.handleEvents(IntegrationServerConsumer.java:204)
at com.mslv.integration.integrationServer.IntegrationServerConsumer.run(IntegrationServerConsumer.java:175)
at com.metasolv.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:725)
at java.lang.Thread.run(Thread.java:568)
Error initializing the MetaSolv Solution Sender: javax.naming.CommunicationException. Root exception is java.net.ConnectException: t3
at com.mslv.integration.messaging.JmsSender.send(JmsSender.java:75)
at com.mslv.integration.handlers.OutboundEventHandler.sendOutboundMessage(OutboundEventHandler.java:97)
at com.mslv.integration.IntegrationManager.processOutbound(IntegrationManager.java:200)
at com.mslv.integration.integrationServer.IntegrationServerConsumer.executeEvent(IntegrationServerConsumer.java:268)
at com.mslv.integration.integrationServer.IntegrationServerConsumer.handleEvents(IntegrationServerConsumer.java:204)
at com.mslv.integration.integrationServer.IntegrationServerConsumer.run(IntegrationServerConsumer.java:175)
at com.metasolv.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:725)
at java.lang.Thread.run(Thread.java:568)
Error initializing the MetaSolv Solution Sender: javax.naming.CommunicationException. Root exception is java.net.ConnectException: t3
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |