JMS Adapter In SOA Composite Rejecting Messages When Priority is Set Higher Than 9
(Doc ID 2194280.1)
Last updated on JANUARY 14, 2019
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
JMS Adapter in SOA Composite is rejecting messages after Consuming from Oracle AQ. Getting below Error Message in SOA Suite 12.1.3 and Same BPEL Service with JMS Adapter was working fine in Oracle SOA Suite 10G. But it is not working in SOA Suite 12.1.3.
Priority Set on Oracle AQ is default 50. Same priority was set earlier also when this Code was running in BPEL10G. Now when the priority is reduced below 9 on AQ then it works fine in 12.1.3.
detail Error Message:
<[composite_name: Dispatcher_BoxFacility_Far_Events_New] [composite_version: 1.0] [endpoint_name: JmsAQBoxFacility_AQConsumer] JmsAdapterMessage_setHeaderJMSPriority: Cannot set message priority to '-41' since it is outside the valid range: 0..9>
<[composite_name: Dispatcher_BoxFacility_Far_Events_New] [composite_version: 1.0] [endpoint_name: JmsAQBoxFacility_AQConsumer] JmsConsumer_sendInboundMessage: [destination = XXCU_E4_OUT_EVENT_CB, subscriber = null]: Error (null) while preparing to send XMLRecord JmsXMLRecord
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