RR business service on ALSB

Question

Hello,
I created a business service on ALSB.
It is defined as a JMS service that uses MQSeries queues for request-response interaction with the mainframe with as response correlation pattern "JMSMessageID".
It works fine as long as the mainframe produces its responses within the specified response timeout.
When the mainframe puts a response on the response queue after the time-out has expired, the message stays on the response queue forever, as the ALSB reads it, and performs a rollback, with as message like:
<Warning> <WliSbTransports> <PC51460> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0041427CE96A1767ADA0> <> <1216200008067> <BEA-381542> <JmsAsyncResponseMDB.onMessage() received a message with an unknown message Id ID:414d51204d51534e545455202020202017d76f48200e0918; marking TX for rollback...>
How to handle this time-out problem?
Thanks,
Ronny

Answer 1

Hi Ronny,
we have the same problem you described.
We are using OSB 10.3.1 and we implemented the same pattern request-respond RR.
We are exposing a third-party system in a service oriented manner as web services.
Those web services are proxy services that route to a common local proxy named CommonService.
The CommonService proxy uses a business service CommonJmsRR that publishes into a JMS queue (named IN) the request and waits for the answer listening from another JMS queue (named OUT). On that business service we defined 'Is Response Required: ENABLED', 'Response Timeout: 60 secs' and we use JMSCorrelationID as Response Correlation Pattern.
On WLS we defined the IN/OUT queues with a given 'time to live' threshold, so after the time-out has expired, the message will stay on the response queue for the time defined in the ‘time to live’ setting.
On log file we see many many occurrences of this error even within the same sec:
<BEA-381542> <JmsAsyncResponseMDB.onMessage() received a message with an unknown message Id 60f4746300000131647c888700000779; marking TX for rollback...>
Did you solve this time-out problem?
Thanks in advance
ferp