Application Integration Architecture (AIA) Message Resubmission Utility Fails for Remote Faults on Cluster with Error "Invalid MessageID"

(Doc ID 2005418.1)

Last updated on JANUARY 27, 2017

Applies to:

Oracle Application Integration Architecture Foundation Pack - Version and later
Information in this document applies to any platform.


AIA Foundation Pack + RUP 2 Patch (17553612)
2 Node Cluster
Java Message Service (JMS) Queues are Uniform Distributed Queues

Current Behavior:
When there is a remote fault that occurs in the Flow, the message is rolled back to the JMS _ErrorQ. The same MessageID is visible in the AIA Resubmission utility User Interface (UI)

When re-submitting the message from AIA Resubmission Utility UI, Error is noted on the UI as "Invalid MessageID"

SOA_Server1.out shows the following ERROR


<FINEST><2015-03-18T01:35:07:453-0400><pool-14-thread-1><><doQueueResubmit><Line:37> - ENTRY
<INFO><2015-03-18T01:35:07:456-0400><pool-14-thread-1><><doQueueResubmit><Line:50> - Got Queue :AIAJMSModule!AIA_CRTCUST_OUT_JMSQ_ErrorQ
<INFO><2015-03-18T01:35:07:478-0400><pool-14-thread-1><><doQueueResubmit><Line:61> - Started QReceiver..weblogic.jms.client.WLConsumerImpl@364a6205
<INFO><2015-03-18T01:35:07:480-0400><pool-14-thread-1><><doQueueResubmit><Line:64> - Retrieved Message :null
<INFO><2015-03-18T01:35:07:481-0400><pool-14-thread-1><><doQueueResubmit><Line:71> - Error ! Please check the passed in Message ID.
<WARNING><2015-03-18T01:35:07:485-0400><pool-14-thread-1><><doQueueResubmit><Line:76> - <THROW>
<****Throwing: Invalid MessageID
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(


Steps to Reproduce:
1. On a Clustered Enviornment, Install AIA Foundation Pack and RUP 2 Patch
2. Deploy a Service that is built using AIA Service Constructor which uses JMS Queue in the flow
    Any AIA Process Integration Pack (PIP) that uses the AIA Error Handling and uses JMS Queues in the flow
3. Make that flow to fail because of some remote fault
4. From AIA Resubmission Utility UI, resubmit the message to see the error

Additional Information:
1. The same Code line works without any errors in a Standalone Environment
2. If Node1 of the Cluster is brought Down, then the messages are getting successfully without any errors from the Other node.
3. When both the Nodes are up, then this Error message is seen when accessing the Message
from a particular JMS Node.

Expected Behavior:
The Resubmission Utility UI has to submit the message when both the nodes of the Cluster are up.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms