My Oracle Support Banner

Messages Are Getting Stuck and Not Reaching The SARM (Doc ID 1495028.1)

Last updated on MARCH 10, 2023

Applies to:

Oracle Communications ASAP - Version 5.2.3 and later
Information in this document applies to any platform.

Symptoms

On ASAP 5.2.3 the following was observerd,

Messages are getting Stuck at the weblogic SRT queue and frequently the user faces the problem of messages not reaching the SARM. Around 6k orders are pending at SRT queue in this example.

From the weblogic Logs:

 

Error Message:

 

####<Aug 22, 2012 11:18:12 AM IST> <Error> <WebLogicServer> <HOSTNAME> <WLS_ADMIN_SERVER_NAME> <[ACTIVE] ExecuteThread: '59' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1345614492005> <BEA-000337> <[STUCK] ExecuteThread: '56' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "1,855" seconds working on the request "weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl@fb103e", which is more than the configured time (StuckThreadMaxTime) of "1,800" seconds. Stack trace:

                java.lang.Object.wait(Native Method)

                java.lang.Object.wait(Object.java:474)

                weblogic.common.CompletionRequest.getResult(CompletionRequest.java:109)

                weblogic.store.gxa.internal.GXATransactionImpl.commitStoreIO(GXATransactionImpl.java:99)

                weblogic.store.gxa.internal.GXATransactionImpl.doOperationCallbacks(GXATransactionImpl.java:215)

                weblogic.store.gxa.internal.GXAResourceImpl.commit(GXAResourceImpl.java:1448)

                weblogic.transaction.internal.XAServerResourceInfo.commit(XAServerResourceInfo.java:1333)

                ….

####<Aug 22, 2012 12:15:41 PM IST> <Error> <JDBC> <HOSTNAME> <WLS_ADMIN_SERVER_NAME> <[ACTIVE] ExecuteThread: '27' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1345617941115> <BEA-001112> <Test "ping" set up for pool "System.<ENV_ID>.ApplicationType.ServiceActivation.Application.1-0;5-2;ASAP.Comp.RPCConnectionPool" failed with exception: "java.sql.SQLException: JZ006: Caught IOException: com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already closed.".>

 

 

Changes

 None                                                                          

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


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