Messaging bridge issues
Hi,
I am seeing below errors in the managed server logs. Messaging bridges are getting disconnected and getting connected.
what is the reason for these errors and what they signify.
####<Mar 8, 2010 8:47:48 AM GMT> <Warning> <MessagingBridge> <clfyhp> <managed01> <ExecuteThread: '1' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-200026> <Bridge "com.test.jms.bridge.att.fault" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.common.LostServerException: weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection reset].)>
####<Mar 8, 2010 8:47:48 AM GMT> <Warning> <MessagingBridge> <clfyhp> <managed01> <ExecuteThread: '1' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-200026> <Bridge "com.test.jms.bridge.att.dc" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.common.LostServerException: weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection reset].)>
####<Mar 8, 2010 8:47:48 AM GMT> <Warning> <MessagingBridge> <clfyhp> <managed01> <ExecuteThread: '1' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-200026> <Bridge "com.test.jms.bridge.att.assoc" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.common.LostServerException: weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection reset].)>
####<Mar 8, 2010 8:47:52 AM GMT> <Error> <MessagingBridge> <clfyhp> <managed01> <ExecuteThread: '29' for queue: 'MessagingBridge'> <<WLS Kernel>> <BEA1-1CF44DC9EBD56D27B005> <BEA-200015> <An error occurred in bridge "com.test.jms.bridge.att.fault" during the transfer of messages (java.lang.Exception: javax.resource.ResourceException: Error sending message
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1384)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:664)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at sun.reflect.GeneratedMethodAccessor269.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
at $Proxy8.send(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1402)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:941)
at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:1019)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
-------------- Linked Exception ------------
javax.resource.ResourceException: Error sending message
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1384)
at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:697)
at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80)
at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:657)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:654)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at sun.reflect.GeneratedMethodAccessor269.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
at $Proxy8.send(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1402)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:941)
at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:1019)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
-------------- Linked Exception 2 ------------
weblogic.jms.common.LostServerException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection reset]
at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:425)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:383)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:186)
at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:677)
at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80)
at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:657)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:654)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at sun.reflect.GeneratedMethodAccessor269.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
at $Proxy8.send(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1402)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:941)
at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:1019)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
).>
####<Mar 8, 2010 8:48:24 AM GMT> <Warning> <MessagingBridge> <clfyhp> <managed01> <ExecuteThread: '9' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200026> <Bridge "com.test.jms.bridge.att.gene" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: javax.resource.ResourceException: Error sending message
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1384)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:664)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at sun.reflect.GeneratedMethodAccessor269.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
at $Proxy8.send(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1267)
at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1190)
at weblogic.jms.adapter.JMSBaseConnection$29.run(JMSBaseConnection.java:1989)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1985)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2686)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
-------------- Linked Exception ------------
javax.resource.ResourceException: Error sending message
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1384)
at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:697)
at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80)
at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:657)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:654)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at sun.reflect.GeneratedMethodAccessor269.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
at $Proxy8.send(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1267)
at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1190)
at weblogic.jms.adapter.JMSBaseConnection$29.run(JMSBaseConnection.java:1989)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1985)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2686)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
-------------- Linked Exception 2 ------------
weblogic.jms.common.JMSException: Error sending message
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:403)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:186)
at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:677)
at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80)
at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:657)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:654)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at sun.reflect.GeneratedMethodAccessor269.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
at $Proxy8.send(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1267)
at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1190)
at weblogic.jms.adapter.JMSBaseConnection$29.run(JMSBaseConnection.java:1989)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1985)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2686)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[weblogic.utils.NestedException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection timed out] - with nested exception:
[weblogic.jms.common.JMSException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection timed out]]]
at weblogic.jms.dispatcher.DispatcherImpl_816_WLStub.dispatchSyncTranFuture(Unknown Source)
at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:408)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:383)
... 23 more
-------------- Linked Exception 3 ------------
weblogic.jms.common.JMSException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection timed out]
at weblogic.jms.dispatcher.Request.getResult(Request.java:218)
at weblogic.jms.frontend.FEProducer.send(FEProducer.java:606)
at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:685)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsyncInternal(DispatcherImpl.java:132)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:123)
at weblogic.jms.dispatcher.Request.execute(Request.java:884)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection timed out]
at weblogic.jms.dispatcher.Request.getResult(Request.java:208)
... 8 more
Caused by: weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection timed out]
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:725)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:664)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
... 2 more
--------------- nested within: ------------------
weblogic.utils.NestedException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection timed out] - with nested exception:
[weblogic.jms.common.JMSException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection timed out]]
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:164)
at weblogic.jms.dispatcher.DispatcherImpl_816_WLStub.dispatchSyncTranFuture(Unknown Source)
at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:408)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:383)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:186)
at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:677)
at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80)
at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:657)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:654)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at sun.reflect.GeneratedMethodAccessor269.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
at $Proxy8.send(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1267)
at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1190)
at weblogic.jms.adapter.JMSBaseConnection$29.run(JMSBaseConnection.java:1989)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1985)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2686)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: weblogic.utils.NestedException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection timed out]
at weblogic.rmi.internal.BasicFutureResponse.sendThrowable(BasicFutureResponse.java:57)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:828)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsyncInternal(DispatcherImpl.java:132)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:123)
at weblogic.jms.dispatcher.Request.execute(Request.java:884)
... 2 more
--------------- nested within: ------------------
weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[weblogic.utils.NestedException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection timed out] - with nested exception:
[weblogic.jms.common.JMSException: ; nested exception is:
weblogic.utils.net.SocketResetException - with nested exception:
[java.net.SocketException: Connection timed out]]]
at weblogic.jms.dispatcher.DispatcherImpl_816_WLStub.dispatchSyncTranFuture(Unknown Source)
at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:408)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:383)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:186)
at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:677)
at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:80)
at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:657)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:654)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at sun.reflect.GeneratedMethodAccessor269.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:149)
at $Proxy8.send(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.onMessageInternal(MessagingBridge.java:1267)
at weblogic.jms.bridge.internal.MessagingBridge.onMessage(MessagingBridge.java:1190)
at weblogic.jms.adapter.JMSBaseConnection$29.run(JMSBaseConnection.java:1989)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.onMessage(JMSBaseConnection.java:1985)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2686)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
.)>
There is an application called "SMSExport" give a search on Google and you will find one. This application exports all your text messages in .txt format to a folder of your choice on the memory card. You can then copy and paste the .txt files to your PC for permanent storage.
Rohinton Contractor
Similar Messages
-
Resource Allocation Issue in Weblogic messaging bridges
Hi,
We are using
Weblogic version à WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 WebLogic Temporary Patch for CR250915 04/18/2006 22:21:33
Java JDK version à 1.4.2_11
Oracle version à 9.2.08
Solaris version à Solaris 5.8
The weblogic application is deployed on Unix Solaris.
We have configured 8 message bridges within weblogic between the 8 Topics in weblogic (source JMS destination) and 8 topics in the External EMS server (Target JMS destination) .
The properties set for the message bridges are
1] AsyncEnabled ="true"
2] DurabilityEnabled ="true"
3] QualityOfService="Exactly-once"TransactionTimeout="10"
4] TransactionTimeout="10"
The source and target JMS destinations are bridge using the resource adapter of jms-xa-adp (connector module)
The properties for the Source JMS Destination are
1] ConnectionFactory = weblogic.jms.client.JMSXAConnectionFactory
The properties for the Target JMS Destination are
1] InitialContextFactory = com.tibco.tibjms.naming.TibjmsInitialContextFactory
2] ConnectionFactory = XATopicConnectionFactory
The EMS client version library is EMS version client library à 4.2.0
The message Bridge Thread Pool Size is à 12
When the weblogic is started, all the bridges comes up properly and are forwarding message to the target, however after some time (1 to 2 days) we observe some that some of the bridges are going down and we get see following error in the weblogic logs
####<May 26, 2010 12:00:56 AM GMT> <Warning> <Connector> <ngun015> <zlw1rdbs12-a> <ExecuteThread: '6' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-190032> << Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
####<May 26, 2010 12:00:56 AM GMT> <Info> <MessagingBridge> <ngun015> <zlw1rdbs12-a> <ExecuteThread: '6' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200042> <Bridge RefDataCompanyBridge failed to connect to the source destination and will try again in 60 seconds. (javax.resource.ResourceException: Failed to start the connection)>
Can you please help us resolve the above issue?
Thanks,
MohanrajThere seems to be couple of known issues with WLS 8.1 and Tibco EMS.. Check with support whether your issue is related to any of the below:
Message bridge will stop responding and WLS has to be restarted to overcome this.
There is a known bug on WLS 8.1. Bug 8062571 is for the issue.
Should the connection be interrupted by a problem on the Tibco side, the messaging bridge never tries to reconnect. the problem can be that Tibco EMS is restarted for some reason or that the maximum number of messages that Tibco EMS can handle is reached.
Unpublished bug8066979 is available for WebLogic Server 8.1 SP6 and later
Unpublished bug8172940 is available for WebLogic Server 9.2 MP2 and later
Note you can get more info about bridge problems by following the below steps:
To debug the bridge you can enable debugging for the messaging bridge using either of the followings methods:
* Add the following lines to your WebLogic start script (before the weblogic.Server line):
-Dweblogic.debug.DebugMessagingBridgeStartup=true
-Dweblogic.debug.DebugMessagingBridgeRuntime=true
* Add the following statements to the ServerDebug entry in your configuration file (config.xml) for the server that the messaging bridge is running on:
DebugMessagingBridgeStartup="true"
DebugMessagingBridgeRuntime="true"
Once debugging is enabled for the messaging bridge, the debugging messages are sent to the server log by default. However, if you want them to appear in the Administration Console, add “DumpToConsole” to the statements show above. For example:
-Dweblogic.debug.DebugMessagingBridgeStartupDumpToConsole=true
Edited by: atheek1 on May 30, 2010 5:19 AM -
Hi- I am having an issue- When I turn my computer on- I get the message "Bridge has encountered a pr
Hi- I am having an issue- When I turn my computer on- I get the message "Bridge has encountered a problem & is unable to read the cache- try purging central cache in cache preferences to correct situation" When I open Photoshop CS5 it say "repousse file is bad or corrupt" "the material file is bad or corrupt" Also all of my actions have disappeared - even the default actions... HELP because as of now, no one has any answers except to buy a support contract....
I use windows & the problem is with photoshop cs5First Aid is to reset preferences. Hold down the Ctrl key and Start Bridge. You will get a reset window with 3 options. You can choose all 3.
If you moved files or used a registry cleaner you many have lost links. In that case the Cleaner Tool and reinstall is recommended. -
My bridge is not working normally and keep given me this message : bridge encountered a problem and is unable to read the cache . Please try purging the central cache in cache preferences to correct the situation
And did you then actually purge the cache?
Please realize that you have given ZERO details.
BOILERPLATE TEXT:
Note that this is boilerplate text.
If you give complete and detailed information about your setup and the issue at hand,
such as your platform (Mac or Win),
exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
your settings in Photoshop > Preference > Performance
the type of file you were working on,
machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
what troubleshooting steps you have taken so far,
what error message(s) you receive,
if having issues opening raw files also the exact camera make and model that generated them,
if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
etc.,
someone may be able to help you (not necessarily this poster, who is not a Windows user).
a screen shot of your settings or of the image could be very helpful too.
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks! -
Weblogic Message Bridge Producing Duplicate JMS Messages
We have a message bridge that we use to integrate with TIBCO. The message bridge is deployed on a WL cluster. We see duplicate JMS messages produced by the bridge when it is deployed on the cluster. We don't see this behavior when only one ManagedServer in the cluster is active,.
TIBCO version: 4.4.3 V5
WLS: 10.3.3 with patch for bug BUG8732539 (BQC6)
java -version
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2121-linux-x86_64, compiled mode)
We are also seeing a lot of exceptions related to
<May 27, 2011 4:11:57 PM PDT> <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
However the bridge is active. We are monitoring the message-out count on TIBCO and we observed that we see duplicates whenever there a message is re-delivered. We opened a case with Oracle support and they suggested patch 10258751 which didn't help. The next suggestion was a patch for "Bug 11852771 - [WLS10.3.2]MISSING AND DUPLICATE IN JMS QUEUE MESSAGE MONITORING" but I don't think it will help since our JMS consumers are getting duplicate messages and this is not just a UI issue.
Here is the message behavior when we send a single message:
Timelines
11:34:17 --> Message sent to TIBCO EMS queue
11:34:17 --> WL MS3 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:17 --> WL MS1 says it got the message and committed the transaction
11:34:17 --> Message is visible in the JMS queue in the admin console
11:34:17 --> TIBCO EMS has still not received an ACK from WL for the message
11:34:31 --> TIBCO EMS resends the same JMS message to WL
11:34:31 --> WL MS2 says it got the message and committed the transaction
11:34:31 --> WL MS1 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are two messages in the JMS queue)
11:34:31 --> TIBCO EMS has still not received an ACK from WL for the message
11:34:54 --> TIBCO EMS resends the same JMS message to WL
11:34:31 --> WL MS4 says it got the message and committed the transaction
11:34:31 --> WL MS2 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are three messages in the JMS queue)
11:34:31 --> TIBCO EMS receives an ACK from WL for the message
MS04
####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: true
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-6A59E8FE76C4FC4CA149
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <MS04> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<193654.1306521294611.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
MS03
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257342> <BEA-000000> <Bridge MessageBridge1 Successfully got connection to the target destination>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1: both source and target adapters support XA = true>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 supportsMDBTX = false supportsXA = true async = true>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 WorkMode = Exactly-once>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntimeVerbose> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 Entering processMessages() ------ >
####<May 27, 2011 11:34:17 AM PDT> <Error> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-3AA29116A4CA622834EA> <> <1306521257343> <BEA-200015> <An error occurred in bridge "MessageBridge1" 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/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:948)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:200)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:948)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
... 8 more
).>
####<May 27, 2011 11:34:17 AM PDT> <Warning> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257344> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
.)>
MS02
####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271386> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: true
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-679AF074F381152F047C
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271392> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<196075.1306521271386.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:54 AM PDT> <Error> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
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:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:225)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
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:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
... 2 more
).>
####<May 27, 2011 11:34:54 AM PDT> <Warning> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
MS01
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257536> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: false
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-72BC818FE2BB8C2655C6
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257542> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<195581.1306521257536.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:31 AM PDT> <Error> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
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:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:224)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
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:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
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:201)
... 1 more
).>
####<May 27, 2011 11:34:31 AM PDT> <Warning> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
.)>@Tom, thanks for your hints and sorry for my delayed response. Here are my answers to your queries…
-- Does messaging work, without any exceptions, when only one bridge is active?
It works fine when only one node of the cluster is active. -- I'm not familiar with Tibco monitoring, but I suspect that the "message-out count on TIBCO" stat doesn't always imply that there's a duplicate message. It could mean that an initial message delivery attempt failed, it's transaction rolled back, and the message was redelivered. Redelivery after a failure is normal - the original delivered message, if one actually made it onto a WebLogic queue, should be discarded by WebLogic when its failed transaction eventually rolls back (before its ever handed to a consumer application).
You are absolutely right. The mismatch in count was due to redelivery attempts. We could see that as soon as we turned on trace in TIBCO-- The posted stack traces look like they may be JVM stdout/stderr scrapes, which are often automatically truncated, for example, see the "... 8 more" listed at the bottom of one of the stack traces below. There might be more information in the full stack trace for the "Resource manager is unavailable" exception. Full traces are logged in each WebLogic Server's log files.
I tried redirecting the output and even set "stdout Stack Trace Depth:" to -1 but I am not albe to see the complete trace.-- The setTransactionTimeout NullPointerException error message looks like it is collateral damage from the original reported "Resource manager is unavailable" exception that's thrown earlier during the enlistResource() step. If you are truly getting duplicates, then I think this is a clue that the bridge is somehow (stupidly) trying to proceed with forwarding the message despite the fact that there's no current transaction on the thread...
I have a case open with Oracle support and we have extensive debugging turned on. Here is what the engineer came back with. There is an issue with XA transactions in JCA adapter when it talks to third party providers like TIBCO. Since the resource names are not unique across the cluster, a XA transaction is started on multiple nodes in the cluster for the same message. All transactions abort but the message is persisted and TIBCO redelivers the message since the connection is severed when the transaction aborts. We were able to reproduce this scenario at will with our setup and Oracle was able to reproduce the issue too. -- Can you check the state of the message on the WebLogic Q? The fact that a message is shown on the WL console doesn't necessarily mean that the state of the message is visible (it could be waiting for the transaction to commit - something that apparently never happens). On the console: Services -> Messaging -> JMS Modules -> [module name] -> [destination name].
Our consumer was getting duplicate messages. This confirms that the console was not giving us incorrect information. The console showed that 2/3/4 messages were in "current" state when we expected only one message. -- Make sure that the bridge's Tibco destination is a Tibco queue not a Tibco topic (it's happened).
Yeah we made sure it was a Queue. -- Can you post your bridge and destination stanzas from your config.xml?
Will try to do this shortly but have to strip out lot of information. -- I vaguely recall that there was a problem with untyped connection factories in Tibco at one point (not sure). You might want to try changing the Tibco configuration to spin-up "XA Queue Connection Factory" instead of just an "XA Connection Factory" (plus modify the bridge configuration accordingly).
We tried this but it didn't eliminate this issue. One thing we did notice however was that the number of rollbacks were greatly reduced.
Here is the workaround that Oracle is suggesting: Create pinned destinations and assign it to a distributed queue. This will keep the transactions local and hence eliminate the duplicate transactions and rollback. We tried it and it eliminated the dups issue. However I discovered another bug during my testing. Our cluster messaging mode is "Unicast" and message forwarding from zero consumer queues to queues with consumers fails. We have four/five nodes in the cluster and two consumer threads. I observed that the zero consumer queues always forward to one queue in the cluster that has consumers. The forwarding stalls when I bring down the node that has consumers. Again, we were able to reproduce this issue at will and Oracle has acknowledged that it is a bug. They've reported that Unicast fails without any warning whereas Multicast fails with a warning in the log. We have observed this message forwarding stalling even with UDQs.
I have another case open for an issue where our message bridges that transfer messages from TIBCO to WLS stalls after sometime. The status is shown as active but it is not doing anything. The server instance shows stuck threads trying to roll back a message. TIBCO logs indicate that it is receiving a request to rollback a transaction but it is not finding the transaction to rollback. The only way to recover from this condition is to restart the cluster. I am fairly confident that he root case for this issue is again the XA transaction issue. I changed our UDQ to pinned destination in one environment and we are no longer seeing dups or bridge stalling there. Hopefully Oracle can resolve the message forwarding issue.Thanks again…. -
Hello All,
I am trying to hook up 2 Queues as source and target destinations for the WLS8.1
Messaging Bridge[MB] functionality.
So when I send a message to Q1[source destination], the MB forwards the message
to Q2[target destination].
I have 1 MDB deployed and listening on Q2.
I verify the messages received via the admin console in wls8.1 as well as the
MDB I have deployed.
Thus, the MB works.
However, when I deploy a MDB on Q1 as well, the message is lost(not forwaded to
Q1 by the MB).
Assuming that the source destination is of type Queue, and this behaviour is expected,
I went to test with a Topic as source destination for the MB and a Queue as the
target destination for the MB.
However, I failed to receive any messages in the dest[Q2] via the MB.
This is with / without a MDB listening on the Topic[source destination].
One MDB is always listening on the Queue[target destination].
MB does not work.............
Can anyone help ?
TIA.
There is no native code specific to this use case, except
perhaps for IBM code, and I know of no issues.
Raja wrote:
> I have tested Messaging Bridge(jms-xa-adp.rar),Foreign JMS provider in WLS8.1-SP1
> on windows NT m/c.Can any body tell me whether there will any problem while setting
> up and running the same test on Solaris.
>
> Thanks in advance,
> Raja
-
WLS 8.1 SP5 Message bridge doesn't refresh connection after idle time out
Hi,
I am seeing in the log after enabling the debug flags that message bridge intermittently stops refreshing the connection without logging further info and causing a production failure.Bridge is forwarding the message from WLS 8.1..5 DQ to the remote MQ 6.0 queue.
Below is the snippet which doesn't come in the log which suggests that bridge stops refreshing the connection.
<BEA-200027> <Bridge "CASLDNSenderBridge" works in asynchronous mode and has not received messages for the predefined maximum idle time. The connections to the adapters will be interrupted and reestablished.>
The above message does appear everytime but intermittently it stops and the messages put after this leading to the exceptions.The bridge has been configured in asynchronous mode and the idle time out is configured as 60 secs.
Can somebody please let me know if there is any known issue with 8.1 SP5 where message bridge stops refreshing connection intermittently or how to debug this further.I would normally suggest raising the issue with support, but I recall hearing that 8.1 is nearing the end of its support cycle, so I'm not sure that's an option for you. Other options:
- try upgrading to a newer SP, or better yet, a new version of WebLogic
- try changing to synchronous forwarding
- examine thread dumps from when the bridge appears to be stalled
- post the exception that bridge is throwing when it tries to connect
- try patching MQ (the problem could be on the MQ side, and perhaps an older version of the bridge may not be fully capable of handling all of MQs minor quirks)
- write a program to (A) detect inactivity on the src destination, and (B) somehow restart the bridge and/or all of WL when this occurs
Tom -
When restarting server after a crash, Messaging bridges are not starting
Hi,
We have Messaging bridge configured with Exactly-Once QOS to read messages from IBM Websphere MQ to Weblogic distributed Queue. We are using Weblogic 10gR3.
1. We killed the weblogic server which was reading message from source destination(IBM MQ). We did this to check whether any message is lost when a server crashes.
2. Then we restarted the weblogic application server and checked the weblogic messaging bridge status.
3. The messaging bridge was not started properly and the following Exception was thrown.
####<Apr 22, 2010 4:09:11 PM BST> <Error> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-056A9014D88E2BE368B7> <> <12312323333> <BEA-200015> <An error occurred in bridge "BRIDGE" during the transfer of messages (javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'eis/jms/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:941)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:630)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1182)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1116)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:511)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:438)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy87.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1427)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
.).>
####<Apr 22, 2010 4:09:11 PM BST> <Warning> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1271948951881> <BEA-200026> <Bridge "BRIDGE" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.bridge.internal.MessagingBridgeException.)>
####<Apr 22, 2010 4:09:12 PM BST> <Info> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1271948952726> <BEA-200020> <Bridge "BRIDGE" is stopped.>
Please give your suggestions to fix this issue.
Thanks!
Edited by: user11340353 on 28-Apr-2010 06:34Hi,
*The server was started in warning mode and the JTA was declared unhealthy. I saw 2 transaction alive for more than 2000 seconds which is uncommon.
*The resource adaptor was started properly.
*We are using file store. But will it make a difference?
Thanks! -
Message Bridge Destination points to old IP, after failover with HA pair
Hi
Weblogic Version in use is 7.0sp7
We have this Messaging Bridge configured, between two instances of Weblogic server (Each weblogic server exists on Different Weblogic domains)
Both the weblogic servers run on the same machine.
So we have configured the message bridge destination with localhost, instead of an IP or DNS name in it.. viz.
t3://localhost:8001
t3://localhost:8020 respectively
where 8001 and 8020 are the listen ports of the respective weblogic servers.
This machine is a HA pair, controlled by vcs cluster server.
Which means when we failover from one node to another of the HA pair, the transition(which also involves the IP change from node A to node B) should be ideally transparent to weblogic.
But when it comes to these messaging bridge destinations
The Messaging bridge resolves the localhost in the Message Bridge destination to the old node IP, after the failover is done using vcs cluster server.
To me it looks like weblogic is caching the IP details somewhere and probably reusing it, unaware of the fact that the IP of the machine has changed after the failover.
I tried configuring the message bridge destination with addresses like t3://<DNSname>:8001 and 8020 respectively. But stiil it tries to connect to the IP of the old node only.
I did come across this patch in Weblogic 7.0 sp5, which is pretty close to the issue that i am encountering..
CR126201 In a multiple-server domain, if a Managed Server was rebooted to use a different address or port
number, the JTA subsystem failed to update the address information. This would cause the
following exception when the changed server was rebooted:
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: t3://ip_address:port_number:
Destination unreachable;
nested exception is: java.net.ConnectException: Connection
refused; No available router to destination
Would really appreciate if someone can help with this issue.
Regards
AzadI'm not quite sure what the correct solution might be, but a possible work-around might be to hard-code the two addresses directly into the bridge URL. For example: t3://host:7010,host:7020. WebLogic will try each address in turn, starting from the first one until one succeeds or all fail.
Another solution might be to configure an "external listen address" on each server. This is the address that "reconnectable" external clients (such as EJBs or a bridge ) will use for reconnect in place of the server's actual listen address.
Tom -
JMS Message Bridge - WLS to MQ
Hi,
Subsequent to my last posts on Foreign JMS Server setup (where I had to receive a msg from a remote MQ Queue), now I have a requirement to post messages to an remote MQ Queue for a diff application.
As a POC, I configured the JMS Message Bridge with bridge source as my local JMS queue and bridge destination as the Remote MQ Queue and it works fine as expected !!
just have couple of questions on that -
1. For a long time, I was struggling with this error on server startup
<BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
Then I realized from the server log that the actual reason was authentication failure in MQ Queue Manager :
JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager '' with connection mode 'Client' and host name '77.40.190.130'. Please check if the supplied username and password are correct on the QueueManager you are connecting to AND
JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
Since this MQ setup is managed by someone else, when they pass on the .binding file after creating queuemanager, queue, etc, Should I also ask them for the username and password for the QM?? I am not sure if this is a part of the .binding file.
2. Some doubts around the QOS. As I understood, I am using the No-Transaction Adapter. This means I can use QOS as either "Atmost once" or "Duplicate OK". The latter seems to be ok so that I dont lost messages in any case. But I am yet to find out if the other application is ok to handle duplicates.
But is there a restriction/limitation to use "Exactly Once" ?? I noticed that there is also an XA-Transaction Adapter in WLS. Is it not possible to use that with MQ?
Thanks in advance.
best regards,
MuraliIn your binding file QCF or XAQCF definition , you will see a Channel field since you are using a client mode to connect to the queue manager. This channel is called a Server Connection Channel [ SVRCONN]. At the queue manager side of things, when this SVRCONN is defined, MQ Admin teams tend to define an attribute called MCAUSER. In this setup the userid used for authorisation at queue manager is the following in the below precedence:
1. If MCAUSER is defined in the channel, that will be the user id and it overrides any security context sent from client application. This user id should have sufficient permissions to connect to queue manager , get , put. The MQ admin teams on certain platforms will be able to get the exact permission that is missed from the queue manager error logs when a 2035 security exception occurs.
2. If no MCAUSER is defined then the userid passed in the createConnection JMS call will be the user context used.
I am not exactly sure of the behaviour when no MCAUSER and no user id in createConnection calls, but i think it takes the user of the MQ Listener process which starts the SVRCONN channel instance when a client initiates the connection.
So for your situation, it will be worth start checking with how the MQ side configuration is. This issue tends to be a very common issue with client applns connecting to qmgr. -
Messaging Bridge status using WLST
Hi,
I am trying to build a WLST script which tells the state of n number of messaging bridges that I have on AdminServer.
connect('uname','pswd','t3://localhost:7001');
serverRuntime();
bd= cmo.getMessagingBridgeRuntime();
print bd.getName()
print bd.getState();
I am having issues in finding the mbean instance, error is as follows
AttributeError: getMessagingBridgeRuntime
would be of great help if you already have this script which is working or help me in solving this.
I am using weblogic 10.3.1It can be done using weblogic.Admin utility, below is the script...you can modify this according to requirement...
java weblogic.Admin -url t3://$admURL -username weblogic -password $admpasswd GET -pretty -type MessagingBridgeRuntime -mbean $domain:ServerRuntime=$mserver,Name=$bridge,Type=MessagingBridgeRuntime,Location=$mserver -property Description -property Name -property State | grep -v MBeanName -
I am using weblogic 10.3 on sunos and i am seeing this issue where the messaging bridges keep dying ever so often(once or twice a week). I have over 15 servers in the weblogic domain but out of them only 2-3 messaging bridges die at random. The issue is compounded by the fact that the weblogic logs say unable to connect to source destination will retry later but weblogic never retries. I can't see any configuration where i can configure duration and number of retries for messaging bridges. Does anyone know how to fix this problem?
Ok is there a way anyone knows of by which we can reset the messaging bridge from the admin console without having to restart the managed server?
-
Message bridge exception when using bridging to MQ
hi ... was wondering if anyone could suggest what might be causing this.
I have a weblogic 8.1 queue bridged to a MQ5.3 queue. I was successfully able
to put messages (using the container to handle the XA) into the weblogic Q and
have the bridge successfully pass the msg onto the MQ Q. However I have started
getting the following error msgs on random occasions.(and the bridge is not able
to transfer the msgs across). Any suggestions as to what might be causing this?
Please let me know if you need any additional info.
thanks,
Rajat
<Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200033> <Bridge "JeInputBridge"
is obta
ining connections to the two adapters.>
<Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200032> <Bridge "JeInputBridge"
is conf
igured to disallow degradation of its quality of service in cases where the configured
quality of se
rvice is unreachable.>
<Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200030> <Bridge "JeInputBridge"
is conf
igured to work in "Exactly-once" mode, and it is actually working in "Exactly-once"
mode.>
<Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200028> <The bridge
"JeInputBridge" has
started transferring messages.>
<Nov 14, 2003 11:10:08 AM EST> <Error> <MessagingBridge> <BEA-200015> <An error
occurred in bridge "
JeInputBridge" during the transfer of messages (javax.resource.ResourceException:
Exception during e
nListResource).>
<Nov 14, 2003 11:10:08 AM EST> <Warning> <MessagingBridge> <BEA-200026> <Bridge
"JeInputBridge" enco
untered some problems in one of its adapters or underlying systems. It stopped
transferring messages
and will try to reconnect to the adapters shortly. (The exception caught was
weblogic.jms.bridge.in
ternal.MessagingBridgeException.)>
<Nov 14, 2003 11:10:09 AM EST> <Info> <MessagingBridge> <BEA-200020> <Bridge "JeInputBridge"
is stop
ped.>
I suggest that you contact BEA Customer Support so that somebody can spend more time working
directly with you and solving the problem.
Sorry for not being able to help you more.
Dongbo
Rajat wrote:
> hi Dongbo ... i checked the MQ error logs and found the followign error:
>
> ----- amqccita.c : 2758 -------------------------------------------------------
> 11/17/03 10:33:24 AM
> AMQ9208: Error on receive from host AHEWVTBHALLRA1-1 (169.242.174.24).
>
> EXPLANATION:
> An error occurred receiving data from AHEWVTBHALLRA1-1 (169.242.174.24) over
> TCP/IP. This may be due to a communications failure.
> ACTION:
> The return code from the TCP/IP (read) call was 131 (X'83'). Record these
> values and tell the systems administrator.
>
> I did a test and found out that the error above is logged when i shut down the
> WLS and NOT when i get the message bridge exception. The MQ system Admin feels
> that there is bug in WLS as shuttting down WLS should gracefully terminate the
> MQ connection and not throw any exceptions on MQ. So looks like this another thing
> i would need your help on. Any other suggestions on what to do regarding the message
> bridge exception ?
>
> Thanks,
> Rajat
>
> Dongbo Xiao <[email protected]> wrote:
> >Hi Rajat,
> >Did you look at the log or tracing on the MQSeries side as I suggested?
> >If you don't see any suspicious error messages on the MQSeries side,
> >I would suggest that
> >you contact the BEA Customer Support.
> >Thanks,
> >Dongbo
> >
> >Rajat wrote:
> >
> >> hi Dongbo,
> >>
> >> The problem occurs regardless of whether i stop the bridge and restart
> >it. As
> >> mentioned earlier, this problem does not occur all the time. This morning
> >i started
> >> up WLS and the it was giving the error. I then stopped it and restarted
> >WLS ...it
> >> started working fine. I then stopped the bridge and restarted the bridge..and
> >> the errror happened. I then stopped the WLS and restarted it ...and
> >the problem
> >> was still there.... i then stopped and restarted WLS and everything
> >started working
> >> fine. On one occasion a few days ago... the bridge was working fine..and
> >then
> >> all of a sudden started giving this error...and after a while it started
> >working
> >> again. Pls suggest next steps.
> >>
> >> Thanks,
> >> Rajat
> >>
> >> Dongbo Xiao <[email protected]> wrote:
> >> >
> >> >Hi Rajat,
> >> >
> >> >I have looked at your log file after Tom bought to me attention of
> >the
> >> >problem you are
> >> >having.
> >> >The error message regarding the adapter at the startup
> >> >(NoSuchMethodException) is not a problem. It is just an info message.
> >> >I also noticed that the Input bridge had been stopped and restarted
> >before
> >> >the error
> >> >occurred. Did you get the same error if you did not stop and restart
> >> >the bridge?
> >> >Looks like the connection was somehow closed on the MQSeries side
> >after
> >> >the bridge
> >> >established a connection to it but before the bridge sent any message
> >> >over.
> >> >If the problem only occurs after you stop and restart the bridge,
> >it
> >> >more likely is
> >> >a bug on the WLS side. Otherwise, I would suggest that you check
> >the
> >> >log (or tracing)
> >> >of the queue manager on the MQSeries side and see if you can spot
> >some
> >> >problem on the
> >> >MQSeries side.
> >> >
> >> >Thanks,
> >> >Dongbo
> >> >
> >> >Rajat wrote:
> >> >
> >> >> hi Tom... i looked over the FAQs but did not spot anything that
> >i was
> >> >doing wrong.
> >> >> I have attatched the stack trace with the JMS debugging. (Sorry
> >for
> >> >the large
> >> >> file... but i spotted some failure msgs regarding the adapter at
> >startup
> >> >and i
> >> >> would like you to take a look ..). I have two bridges setup...
> >> >> - JeInputBridge - connects weblogic Q to MQ Q
> >> >> - JeReplyBridge - connects MQ Q to weblogic Q
> >> >>
> >> >> I am using the eis.jms.WLSConnectionFactoryJNDIXA adapter and am
> >using
> >> >the QOS
> >> >> = "Exactly-Once"
> >> >>
> >> >> The weird thing is that the JeReplyBridge has never shown this error....
> >> >but the
> >> >> JeInput bridge sometimes works fine... then starts giving the error.
> >> >On occassions,
> >> >> it will keep trying and eventually start working... and sometimes
> >i
> >> >have to restart
> >> >> the weblogic server several times before it starts working.
> >> >>
> >> >> Any suggestions/advice will be much appreciated.
> >> >> Thanks,
> >> >> Rajat
> >> >>
> >> >> Tom Barnes <[email protected]> wrote:
> >> >> >The information below is too generic to interpret. Were stack
> >traces
> >> >> >printed out? Anyhow, I suggest that your start with the
> >> >> >7.0 messaging bridge FAQ (it also applies to 8.1) to get
> >> >> >more information about how to diagnose bridge issues:
> >> >> >
> >> >> >http://edocs.bea.com/wls/docs70/faq/msgbridge.html
> >> >> >
> >> >> >Rajat wrote:
> >> >> >
> >> >> >> hi ... was wondering if anyone could suggest what might be causing
> >> >> >this.
> >> >> >>
> >> >> >> I have a weblogic 8.1 queue bridged to a MQ5.3 queue. I was successfully
> >> >> >able
> >> >> >> to put messages (using the container to handle the XA) into the
> >> >weblogic
> >> >> >Q and
> >> >> >> have the bridge successfully pass the msg onto the MQ Q. However
> >> >I
> >> >> >have started
> >> >> >> getting the following error msgs on random occasions.(and the
> >bridge
> >> >> >is not able
> >> >> >> to transfer the msgs across). Any suggestions as to what might
> >be
> >> >causing
> >> >> >this?
> >> >> >> Please let me know if you need any additional info.
> >> >> >>
> >> >> >> thanks,
> >> >> >> Rajat
> >> >> >>
> >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200033>
> >> >> ><Bridge "JeInputBridge"
> >> >> >> is obta
> >> >> >> ining connections to the two adapters.>
> >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200032>
> >> >> ><Bridge "JeInputBridge"
> >> >> >> is conf
> >> >> >> igured to disallow degradation of its quality of service in cases
> >> >where
> >> >> >the configured
> >> >> >> quality of se
> >> >> >> rvice is unreachable.>
> >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200030>
> >> >> ><Bridge "JeInputBridge"
> >> >> >> is conf
> >> >> >> igured to work in "Exactly-once" mode, and it is actually working
> >> >in
> >> >> >"Exactly-once"
> >> >> >> mode.>
> >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200028>
> >> >> ><The bridge
> >> >> >> "JeInputBridge" has
> >> >> >> started transferring messages.>
> >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Error> <MessagingBridge> <BEA-200015>
> >> >> ><An error
> >> >> >> occurred in bridge "
> >> >> >> JeInputBridge" during the transfer of messages (javax.resource.ResourceException:
> >> >> >> Exception during e
> >> >> >> nListResource).>
> >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Warning> <MessagingBridge> <BEA-200026>
> >> >> ><Bridge
> >> >> >> "JeInputBridge" enco
> >> >> >> untered some problems in one of its adapters or underlying systems.
> >> >> >It stopped
> >> >> >> transferring messages
> >> >> >> and will try to reconnect to the adapters shortly. (The exception
> >> >> >caught was
> >> >> >> weblogic.jms.bridge.in
> >> >> >> ternal.MessagingBridgeException.)>
> >> >> >> <Nov 14, 2003 11:10:09 AM EST> <Info> <MessagingBridge> <BEA-200020>
> >> >> ><Bridge "JeInputBridge"
> >> >> >> is stop
> >> >> >> ped.>
> >> >> >
> >> >>
> >> >> ------------------------------------------------------------------------
> >> >> Name: myserver.log
> >> >> myserver.log Type: Text Document (application/x-unknown-content-type-txtfile)
> >> >> Encoding: base64
> >> >
> >
-
Message bridge connecting to MQ shows active/forwarding messages but fails to deliver
Created a message bridge between active MQ and weblogic.
Status shows active >>forwarding messages
when i put a message in the queue i see the following error in the logs
<Aug 21, 2013 5:13:29 PM PDT> <Warning> <MessagingBridge> <BEA-200026> <Bridge "
Bridge-1" encountered some problems in one of its adapters or underlying systems
. It stopped transferring messages and will try to reconnect to the adapters sho
(The exception caught was javax.resource.ResourceException: Error sending
message.)>
Weblogic10.3We resolved this issue by using the latest Active MQ jar.Earlier we were using 5.4.3 now when using the latest version this issue got resolved
-
Weblogic Messaging Bridge stops working
Hi, we are having a Weblogic Integration Domain (WLI 8.1). This domain has several JMS distibuted destinations and Messaging Bridges. In Production environment, the Messaging bridge stops then and there and lot of messages get piled up in the queues. The following exception is found in logs. Can someone help with the suggestion on this please .. It is quite urgent for us ..
####<Sep 26, 2011 11:34:34 AM EEST> <Warning> <MessagingBridge> <servername.com> <ccpeIntMServer1> <ExecuteThread: '4' for queue: '
weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-200026> <Bridge "MessagingBridge1" encountered some problems in one of its adapters or underl
ying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.common
.LostServerException: java.net.SocketException: Broken pipe.)>
####<Sep 26, 2011 11:34:34 AM EEST> <Info> <MessagingBridge> <servername.com> <ccpeIntMServer1> <ExecuteThread: '22' for queue: 'we
blogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200020> <Bridge "MessagingBridge1" is stopped.>
####<Sep 26, 2011 11:34:34 AM EEST> <Warning> <MessagingBridge> <servername.com> <ccpeIntMServer1> <ExecuteThread: '1' for queue: '
weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-200026> <Bridge "JMSMessagingBridge1" encountered some problems in one of its adapters or under
lying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.common.LostServerException: java.net.SocketException: Broken pipe.)>
####<Sep 26, 2011 11:34:34 AM EEST> <Info> <MessagingBridge> <servername.com> <ccpeIntMServer1> <ExecuteThread: '20' for queue: 'we
blogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200020> <Bridge "JMSMessagingBridge1" is stopped.>This is a very generic description of your issue, I think you should open a support case to help you troubleshoot.
Maybe you are looking for
-
Executing a report program in background from another program
Hi Experts, I developed a report to display material change history based on change date range. Report is taking much time (around 15-20 mins) as I'm hitting CDPOS and CDHDR tables. User wants to execute the report in foreground because he/she can gi
-
How to create a Folder Tree in Exchange Server from a Java progarm.
hi all, I am using Microsoft Exchange Server 2000. I have a requirement of creating the following things from a Java program. 1) Creating a Folder Tree 2) Creating a Mailbox Store 3) Creating a Public Store 4) Creating a Recipient Policy 5) Creating
-
IPod 160 GB Please Help! Any Ideas?
Hi, I have an iPod classic 160 gb, its about 5 or 6 years old and its just been sitting in a drawer for years because when I got this as my fourth replacement ipod, mine either melted (twice) or everytime they would send me a new one it would die on
-
8961 call features don't work on CME
Dear all, I installed the 8961 using sip on CME 8.8, and I have configured the feature-buttons on the template which includes call pickup, call park and transfers, and these feature buttons can display on the screen. But when I use these buttons, I g
-
My iMac is getting slower and slower
My Mac (3.2GHz Intel Core i3 4GB Memory) is about 4 years old and has been getting slower and slower over the last 5 or 6 months. An earlier post recommended using 'Etracheck' which I have done and attached the information below. I think I may have a