My Oracle Support Banner

<BEA-381501> <JmsAsyncMessageTable timed out message with id Error When JMS Business Service With Request Response Model Timed Out (Doc ID 1085649.1)

Last updated on JANUARY 10, 2020

Applies to:

Oracle Service Bus - Version 2.1 to 10.3.1 [Release Aqualogic Service Bus to AS10gR3]
Information in this document applies to any platform.


In OSB/ALSB, JMS Business service is configured for Request - Response model (with Correlation ID / Message ID Pattern). When Business Service sends a message to a Queue (SourceQueue) and waits for a message in another queue (DestQueue) with the same message id / correlation ID,  Business service gets timeout with the following error message in the server log, even though the message reaches the DestQueue before the timeout setting of Business Service is reached:

Error message in the server log:

####<Mar 18, 2010 9:21:47 AM VET> <Warning> <WliSbTransports> <cssoad02> <AdminServer> <Thread-16> <> <> <> <1268920307680> <BEA-381501> <JmsAsyncMessageTable timed out message with id ID:P<825171.1268920288380.0>>

After the business service timed-out, it prints the following message in the server log (for the same message):

####<Mar 18, 2010 9:21:48 AM VET> <Warning> <WliSbTransports> <cssoad02> <AdminServer> <[STUCK] ExecuteThread: '53' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1268920308350> <BEA-381505> <JmsAsyncResponseMDB.onMessage() received a message with an unknown message Id ID:P<825171.1268920288380.0>; dropping message...>


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.