Huge WebLogic JMS File Store Files Make WebLogic Servers Fail With Error - javax.transaction.TransactionRolledbackException: start() failed on resource 'WLStore_case_osm01_oms_jms_store_osm01_01': XAER_RMFAIL : Resource manager is unavailable
(Doc ID 1527616.1)
Last updated on JULY 17, 2023
Applies to:
Oracle Communications Order and Service Management - Version 7.0.0 to 7.3.0.0.0 [Release 7.0.0 to 7.3.0]Information in this document applies to any platform.
Check relevance Jan 15, 2016
Symptoms
The WebLogic server failed with the following error:
####<21-Jan-2013 12:17:09 o'clock CET> <Warning> <RMI> <osmwebp01> <osm01_01> <[ACTIVE] ExecuteThread: '93' for queue: 'weblogic.kernel.Default (self-tuning)'> <
javax.transaction.TransactionRolledbackException: start() failed on resource 'WLStore_case_osm01_oms_jms_store_osm01_01': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'WLStore_case_osm01_oms_jms_store_osm01_01' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:946)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:632)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1183)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1117)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:516)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:443)
at weblogic.store.gxa.internal.GXAResourceImpl.enlist(GXAResourceImpl.java:442)
at weblogic.messaging.kernel.internal.KernelImpl.getGXATransaction(KernelImpl.java:536)
at weblogic.messaging.kernel.internal.QueueImpl.send(QueueImpl.java:316)
at weblogic.jms.backend.BEDestinationImpl.sendIssueMessage(BEDestinationImpl.java:1858)
at weblogic.jms.backend.BEDestinationImpl.send(BEDestinationImpl.java:2093)
at weblogic.jms.backend.BEDestinationImpl.wrappedSend(BEDestinationImpl.java:2036)
at weblogic.jms.backend.BEDestinationImpl.invoke(BEDestinationImpl.java:1524)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchAsyncInternal(DispatcherImpl.java:139)
at weblogic.messaging.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:115)
at weblogic.messaging.dispatcher.Request.dispatchAsync(Request.java:1295)
at weblogic.jms.dispatcher.Request.dispatchAsync(Request.java:96)
at weblogic.jms.frontend.FEProducer.doDispatch(FEProducer.java:882)
at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:1015)
at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1399)
at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1460)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:
Changes
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 |