JMS Transport Proxy Service is Disabled But Messages Are Still Consumed
(Doc ID 2384286.1)
Last updated on JANUARY 14, 2021
Applies to:
Oracle Service Bus - Version 11.1.1.9.0 and laterInformation in this document applies to any platform.
Symptoms
On : 11.1.1.9.0 version and later
For proxy services utilizing the JMS transport, OSB receives messages from destinations by using an MDB. These MDBs get generated and deployed during activation of the service configuration. OSB creates a random, unique name for the J2EE application that gets deployed to WLS. When this proxy service is in disabled state Ideally disabled service should not be consume messages. but during the issue time messages are lost and threads are seen consuming messages.
ERROR
### <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> com.bea.wli.sb.transports.TransportException: [OSB Kernel:380020]Service (ProxyService PL_Integration/Resources/Proxy Service/Wizard/PS_PL_Wizard_JMSResponse) has been disabled.
at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:310)
at com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.java:132)
at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:310)
at com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.java:132)
Changes
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 |
Changes |
Cause |
Solution |