After Securing JMS Queue , SOA JMS Adapter Unable To Create Queue Consumer Due To JMSException
(Doc ID 2346389.1)
Last updated on MAY 15, 2023
Applies to:
Oracle SOA Suite - Version 11.1.1.7.0 to 12.2.1.3.0 [Release 11gR1 to 12c]Information in this document applies to any platform.
Symptoms
On : 11.1.1.7.0 version, Technology Adapters
After securing JMS Queue , SOA JMS Adapter unable to create Queue consumer due to JMSException
ERROR
-----------------------
[2017-12-19T19:47:13.692+00:00] [<server>] [ERROR] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ] [APP: soa-infra] [J2EE_APP.name: soa-infra] [J2EE_MODULE.name: fabric] [WEBSERVICE.name: JmsReader] [WEBSERVICE_PORT.name: execute_pt] [composite_instance_id: nnnn] [composite_name: <name>] [component_name: <name>] JCABinding=> <name>[ OpaqueMessageConsumer::Consume(empty,opaque) ] Could not invoke operation 'Consume' against the 'JMS Adapter' due to: [[
BINDING.JCA-12135
ERRJMS_ERR_CR_QUEUE_CONS.
ERRJMS_ERR_CR_QUEUE_CONS.
Unable to create Queue consumer due to JMSException.
Please examine the log file to determine the problem.
]]
...
[2017-12-19T19:47:13.884+00:00] [<server>] [ERROR] [OWS-04086] [oracle.webservices.service] [tid: [ACTIVE].ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: ] [APP: soa-infra] [composite_instance_id: nnnnnn] [composite_name: <name>] [component_name:<name>] javax.xml.rpc.soap.SOAPFaultException: weblogic.sca.api.ScaException: java.lang.RuntimeException: BINDING.JCA-12563[[
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Consume' failed due to: ERRJMS_ERR_CR_QUEUE_CONS.
ERRJMS_ERR_CR_QUEUE_CONS.
Unable to create Queue consumer due to JMSException.
Please examine the log file to determine the problem.
".
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.generateSoapFaultException(WebServiceEntryBindingComponent.java:1280)
at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComponent.processIncomingMessage(WebServiceEntryBindingComponent.java:1053)
at oracle.integration.platform.blocks.soap.FabricProvider.processMessage(FabricProvider.java:113)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1187)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1123)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:581)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:235)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:195)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:487)
at oracle.integration.platform.blocks.soap.FabricProviderServlet.doPost(FabricProviderServlet.java:544)
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Update the access policy on JMS queue
2. test the application and see the error
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 |
| References |