Massage deliver issue from MQ to Weblogic [message #675540] |
Thu, 04 April 2019 04:22 |
oramoin
Messages: 9 Registered: June 2008
|
Junior Member |
|
|
Hi All,
Following are the Environment Details:
Websphere MQ server Details:
Name: WebSphere MQ
Version: 7.5.0.7
WebLogic 12.2.1.3.0:
Managed servers is running in two different physical machines with the name COM_MS1 and COM_MS2.
Cluster is managed by an administration WebLogic server instance installed only in the first machine COM_MS1.
We have configured a bridge between MQ to WebLogic with "TestDQ" distributed queue, Bridge is working fine but when we send a massage from MQ to Weblogic distributed queue its throwing an error.
####<Apr 4, 2019 1:12:46,126 PM PKT> <Error> <MessagingBridge> <OSM_Test_APP> <COM_MS1> <[ACTIVE] ExecuteThread: '52' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-00B7BB1CC8F8B3DB3271> <13abf1ea-f982-4c2c-a346-84acc74e7d38-00006589> <1554365566126> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-200015> <An error occurred in bridge "MQToOSM-UATBridge@COM_MS1" during the transfer of messages (java.lang.Exception: javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = "eis/jms/internal/WLSConnectionFactoryJNDIXA", javax.transaction.SystemException: start() failed on resource 'eis/jms/internal/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/internal/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/internal/WLSConnectionFactoryJNDIXA' is unavailable
weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1079)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1160)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:678)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:652)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:420)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:360)
Caused by: weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Error enlisting GXA transaction
at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:99)
at weblogic.jms.dispatcher.Request.getResult(Request.java:64)
at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:1166)
at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1590)
at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1664)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:1015)
... 37 more
Caused by: weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Error enlisting GXA transaction
at weblogic.messaging.dispatcher.Request.getResult(Request.java:513)
at weblogic.jms.dispatcher.Request.getResult(Request.java:62)
... 41 more
Caused by: weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Error enlisting GXA transaction
at weblogic.utils.StackTraceDisabled.unknownMethod()
Caused by: weblogic.messaging.kernel.KernelException: Error enlisting GXA transaction
... 1 more
Caused by: weblogic.store.gxa.GXAException: Transaction already rolled back, or the transaction manager has timed out this resource.
... 1 more
Caused by: weblogic.transaction.RollbackException: Tx marked rollback due to unexpected internal exception
start() failed on resource 'eis/jms/internal/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occurred in the transaction branch
error log file attached for more refernce.
Regards
Moin
-
Attachment: COM_MS1.log
(Size: 520.99KB, Downloaded 3286 times)
|
|
|