Message bridge example

Hi,
I need the complete example on Message bridge in weblogic server. ie betwenn to weblogic jms server's??
please help me out if some one know how to setup Message bridge between two weblogic servers
Thank

If your Sonic ESB is lik JMS poller then use JCA JMS adapter with BPEL for communication. It is a reliable option.
If the Sonic ESB is a http service then access it as a webservice from BPEL.

Similar Messages

Sync - Async Bridge example

Hello,
Pls provide Sync - Async Bridge example document.
Regards

HI
Sync/async communication enables a synchronous sender system to communicate with a receiver system that cannot process synchronous messages
Refer this blog
/people/ravikumar.allampallam/blog/2005/02/17/bridging-the-sync-async-bridge-with-fork-xi
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi
There is an example of the Sync/Async Bridge in th SWCV: SAP BASIS.
Namespace: http://sap.com/xi/XI/System/Patterns
The Integration Server receives synchronous messages from a sender and send them to a receiver as asynchronous messages. Conversely, it can send the asynchronous response from the receiver back to the sender as a synchronous response.
As soon as a synchronous message is received from the sender system the process uses a special receive step to open the sync/async bridge, sends the received message to the receiver system asynchronously, and waits for the asynchronous response to arrive from the receiver.
The BPE receives the asynchronous response from the receiver, correlates it with the corresponding query, and activates the waiting process, which then sends the response back to the sender synchronously.
This blog also should give you some idea...
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Also go through these links:
http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c4/dc06418752ef6fe10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f9/66bf40ad090366e10000000a1550b0/RN_XI_DE_neu.pdf

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….

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,
Mohanraj

There 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

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
Azad

I'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

Messaging Bridge logging level

Hi,
I am setting -Dweblogic.Debug.DebugMessagingBridgeRuntime=true in the server start-up script.
In the managed server log, the log messages related to messaging bridge are written from DEBUG level.
Is there any way to restrict the messages from WARNING level.
version: weblogic 8.1,SP5
Thanks & Regards

Hi,
The parameter that you set in the startup script is a debug parameter. So,it is showing all the messages in DEBUG level.
The following are the logging levels from lowest to highest impact:
TRACE, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY
For example, if you set a Logger object level to WARNING, the Logger object publishes only WARNING, ERROR, CRITICAL, ALERT, or EMERGENCY messages.
Since you must have selected DEBUG , it is displaying all the levels higher to that which includes WARNING.
(i.e DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY )
We have Log Filtering but with that also I think it will not be possible to remove the WARNING messages.
If possible, can you have a look so that you can have some more information regarding the same.
http://download.oracle.com/docs/cd/E11035_01/wls100/logging/filtering.html
If you find any other way, let me know.
Thanks,
Sreedevi

Significance of async-enabled option of jms-messaging-bridge

Hi Folks !!
I have a question regarding JMS-MESSAGING-BRIDGES:
What difference will async-enabled = true | false will make to the bridge? Which option will be good from performance point of view ?
Thanks in advance.
Edited by: 994778 on Mar 19, 2013 7:05 AM

As you know, the bridge acts as a receiver from the source destination and a sender to the target destination. When async-enabled is set to true, the bridge works as an asynchronous listener to the source destination, while otherwise it acts as a synchronous receiver. In other words, the former is a push mode and the latter is a poll mode. The sync mode does batching while async mode does not. There are a couple of things that you need to consider while determining which mode is better, such as the desired QOS of the bridge, and whether you are bridging between wls destinations or a WLS destination to/from a 3rd party destination. For example, if you requires exactly-once QOS and your source destination is not a WLS JMS destination, you have to use sync mode; actually the bridge internally will switch to sync mode even if you set it to async mode.
You can find the tuning guide for the messaging bridge at
http://docs.oracle.com/cd/E17904_01/web.1111/e13814/bridgetuning.htm#g1153237
Regards,
Dongbo

Messaging Bridge and cluster problem

I am trying to setup the Messaging Bridge between MQ and WLS. Originally, we were going to use the Foreign JMS setup but the loss of transactionality was an issue (QManager cannot be assumed to be on the same box as our cluster). So we moved to the Messaging Bridge in the hopes that it will provide greater stability.
          I am following the example provided here https://messaging-bridge.projects.dev2dev.bea.com/ and setting up 2 JMS Destinations. Setting up the MQ Destination was trivial given that I had done it already with the Foreign JMS setup.
          But the destination that points to the internal WLS JMS Queue is a little trickier given that we are using clusters. I am stuck trying to figure out what Connection URL I should be using. According the the example above, I should use t3://localhost:7001 but in a clustered setup, what do I point to?

I finally got my Messaging Bridge (Tibco to a WLS Cluster) to work. See my post 3 messages before yours - to which no-one responded... :-(
          So here goes with my suggestion based on what I have done.
          1. Create a Distributed Destination for the WLS queue and "auto deploy" it your cluster. (Read the manual on how to do that, it is quite straightforward).
          2. In the Local Bridge Destination, put :
          Connection URL - nothing
          Initial Context Factory - weblogic.jndi.WLInitialContextFactory
          Connection Factory JNDI Name - <your JMS conection factory name>
          Destination JNDI Name - <the JNDI name given to the Distributed Destination>.
          I hope that works.
          Andy

How to configure Message bridge

          Hi,
          I am trying to setup a JMS Message Bridge for prove of concept purpose in Weblogic
          7.0. Here is my configurations from config.xml:
          <JMSBridgeDestination
          AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          ConnectionFactoryJNDIName="weblogic.jms.testConnectionFactory"
          ConnectionURL="t3://localhost:7001"
          DestinationJNDIName="examples.queue2" Name="LocalBridge"
          UserName="kyang" UserPassword="{3DES}2LeceOSYOaRuCvrFshnBZg=="/>
          ConnectionFactoryJNDIName="weblogic.jms.ClientConnectionFactory"
          ConnectionURL="t3://localhost:7001"
          DestinationJNDIName="examples.queue1"
          Name="MQWeblogicDestination" UserName="kyang"/>
          <JMSConnectionFactory DefaultDeliveryMode="Persistent"
          DefaultTimeToDeliver="200" DefaultTimeToLive="1000"
          JNDIName="weblogic.jms.ClientConnectionFactory"
          LoadBalancingEnabled="false" MessagesMaximum="100"
          Name="ClientConnectionFactory" OverrunPolicy="KeepNew"
          ServerAffinityEnabled="false" Targets="examplesServer"/>
          <JMSConnectionFactory DefaultDeliveryMode="Non-Persistent"
          DefaultTimeToDeliver="200" DefaultTimeToLive="1000"
          FlowControlEnabled="false"
          JNDIName="weblogic.jms.testConnectionFactory"
          Name="testConnectionFactory" OverrunPolicy="KeepNew" Targets="examplesServer"/>
          <MessagingBridge Name="MyMessaging Bridge" Selector="*"
          SourceDestination="LocalBridge"
          TargetDestination="MQWeblogicDestination" Targets="examplesServer"/>
          I used a test client get InitialContext with url:"t3://localhost:7001" and send
          the message to "examples.queue2" which is "MyJMSQueue".
          From the monitor screen I found the message was put on "MyJMSQueue" but the message
          was nerver delieveried to the "examples.queue1".
          From the log, I got following message:
          <Jun 20, 2002 10:05:53 AM CDT> <Info> <MessagingBridge> <200012> <Bridge "MyMess
          aging Bridge" suceesfully found the two adapters configured for it.>
          Do you have any suggestions?
          Thanks a lot!


Don't worry about the log messages about
          "comp/env/wls-connector-resref".
          It is not a problem for the Messaging Bridge feature.
          The real problem is that you have an invalid selector for the
          MessagingBridge. A bridge selector has the same syntax as a JMS message
          selector. As you can see from the JMS specification, a message selector
          syntax is based on a subset of the SQL92 conditional expression syntax.
          I would suggest you try the bridge feature without any selection first
          and add the selector later.
          Dongbo
          Kenny Yang wrote:
          >
          > Mr.Xiao,
          > Thanks! Things are getting better after I made changes according to your suggestion.
          > Now the status is showing: Forwarding Messages. But I still have following exceptions
          > from the logging window:
          >
          > <Jun 20, 2002 1:38:50 PM CDT> <Info> <MessagingBridge> <200020> <Bridge "MyMessa
          > ging Bridge" is stopped.>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <MessagingBridge> <200033> <Bridge "MyMessa
          > ging Bridge" is getting the connections to the two adapters.>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <Connector> <190011> <Unable to locate cont
          > ext: java:/comp/env/wls-connector-resref>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <Connector> <190010> <Unable to determine R
          > esource Principal for Container Managed Security Context.>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <Connector> <190011> <Unable to locate cont
          > ext: java:/comp/env/wls-connector-resref>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <Connector> <190010> <Unable to determine R
          > esource Principal for Container Managed Security Context.>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <Connector> <190035> <There was/were 1 phys
          > ical connection(s) created with the following Meta Data: Product name of EIS ins
          > tance: Java Messaging Service Product version of EIS instance: 1.0.2 Maximum num
          > ber of connections supported from different processes: 0 User name for connectio
          > n: kyang>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <Connector> <190011> <Unable to locate cont
          > ext: java:/comp/env/wls-connector-resref>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <Connector> <190010> <Unable to determine R
          > esource Principal for Container Managed Security Context.>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <MessagingBridge> <200031> <Bridge "MyMessa
          > ging Bridge" is configured to allow degradation of its quality of service in cas
          > es where the configured quality of service is not reachable.>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <MessagingBridge> <200030> <Bridge "MyMessa
          > ging Bridge" is configured to work in "Atmost-once" mode and it is actually work
          > ing in "Atmost_once" mode.>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <MessagingBridge> <200028> <Bridge "MyMessa
          > ging Bridge" starts transferring messages.>
          > <Jun 20, 2002 1:38:55 PM CDT> <Info> <MessagingBridge> <200026> <Bridge "MyMessa
          > ging Bridge" encountered some problems to one of its adapters or underlying syst
          > ems. It stopped transferring messages and will try to reconnect to the adapters
          > shortly. (Exception caught was java.lang.reflect.UndeclaredThrowableException)
          > java.lang.reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTarg
          > etException: javax.resource.ResourceException: Error creating asynchronous consu
          > mer or setting message lisenter
          > at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBase
          > Connection.java:1086)
          > at weblogic.jms.adapter.JMSBaseConnection.setMessageListenerInternal(JMS
          > BaseConnection.java:984)
          > at weblogic.jms.adapter.JMSBaseConnection.setMessageListener(JMSBaseConn
          > ection.java:892)
          > at weblogic.jms.adapter.JMSConnectionHandle.setMessageListener(JMSConnec
          > tionHandle.java:121)
          > at java.lang.reflect.Method.invoke(Native Method)
          > at weblogic.connector.common.internal.ConnectionWrapper.invoke(Connectio
          > nWrapper.java:92)
          > at $Proxy131.setMessageListener(Unknown Source)
          > at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(Messagin
          > gBridge.java:842)
          > at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
          > java:922)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
          > >
          >
          > where can I get the context:"comp/env/wls-connector-resref"?

MQ 6 WLS 9.2 JMS Message Bridge Error

I tried to set up a JMS message bridge between MQ 9.2 and WLS 9.2 collocated on the same server following the BEA example:
          1.Create local queue on MQ
          2.Bind queue using JMSAdmin
          3.Create JMS bridge betwen a source destination using JNDI name in #2 and a local WLS queue.
          Here is the WLS config:
          <messaging-bridge>
          <name>MQ-WLSBridge</name>
          <target>adminServer</target>
          <source-destination>MQ-WLSSource</source-destination>
          <target-destination>MQ-WLSTarget</target-destination>
          <selector></selector>
          <quality-of-service>Exactly-once</quality-of-service>
          <qos-degradation-allowed>true</qos-degradation-allowed>
          <durability-enabled>true</durability-enabled>
          <idle-time-maximum>60</idle-time-maximum>
          <async-enabled>true</async-enabled>
          <started>true</started>
          <preserve-msg-property>false</preserve-msg-property>
          </messaging-bridge>
          <jms-bridge-destination>
          <name>MQ-WLSTarget</name>
          <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
          <classpath></classpath>
          <connection-factory-jndi-name>com.MetaSolv.Security.QueueConnectionFactory</connection-factory-jndi-name>
          <connection-url>t3://localhost:7005</connection-url>
               <destination-jndi-name>WLSMessageQueue</destination-jndi-name>
          </jms-bridge-destination>
          <jms-bridge-destination>
          <name>MQ-WLSSource</name>
          <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
          <classpath></classpath>
          <connection-factory-jndi-name>QCF</connection-factory-jndi-name>
          <initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
          <connection-url>file:///usr/mqm/java/jndi</connection-url>
          <destination-jndi-name>MQMessageQueus</destination-jndi-name>
          </jms-bridge-destination>
          I used a standalone JMS client and was able to connect to the MQ queue using the above JNDI name, factory so the MQ side was set up properly.
          When I start up WLS, I saw that
          <The messaging bridge "MQ-WLSBridge" has been successfully deployed.>
          and the exception:
          <MessagingBridge> <BEA-200042> <Bridge MQ-WLSBridge failed to connect to the source destination and will try again in 20 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: javax.resource.ResourceException: Failed to start the connection
               at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1458)
               at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1438)
               at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:403)
               at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:242)
               at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
               at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
               at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
               at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1057)
               at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:346)
               at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:294)
               at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:277)
               at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:606)
               at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:271)
               at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
               at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
               at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
               at weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMSBaseConnectionFactory.java:92)
               at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:809)
               at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1042)
               at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
               at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
               at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
          )>
          There is no error in the MQ logs. What is the problem?
          CS

C S <> wrote:
          > I tried to set up a JMS message bridge between MQ 9.2 and WLS 9.2
          > collocated on the same server following the BEA example: 1.Create local
          > queue on MQ 2.Bind queue using JMSAdmin
          > 3.Create JMS bridge betwen a source destination using JNDI name in #2 and
          > a local WLS queue.
          >
          > Here is the WLS config:
          > <messaging-bridge>
          > <name>MQ-WLSBridge</name>
          > <target>adminServer</target>
          > <source-destination>MQ-WLSSource</source-destination>
          > <target-destination>MQ-WLSTarget</target-destination>
          > <selector></selector>
          > <quality-of-service>Exactly-once</quality-of-service>
          > <qos-degradation-allowed>true</qos-degradation-allowed>
          > <durability-enabled>true</durability-enabled>
          > <idle-time-maximum>60</idle-time-maximum>
          > <async-enabled>true</async-enabled>
          > <started>true</started>
          > <preserve-msg-property>false</preserve-msg-property>
          > </messaging-bridge>
          >
          > <jms-bridge-destination>
          > <name>MQ-WLSTarget</name>
          >
          <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
          > <classpath></classpath>
          >
          <connection-factory-jndi-name>com.MetaSolv.Security.QueueConnectionFactory</connection-factory-jndi-name>
          > <connection-url>t3://localhost:7005</connection-url>
          > <destination-jndi-name>WLSMessageQueue</destination-jndi-name>
          > </jms-bridge-destination>
          > <jms-bridge-destination>
          > <name>MQ-WLSSource</name>
          >
          Hello,
          First of all, your classpath doesn't seem to be correct. You need to add the
          MQ jars in the bridge classpath. (DONT use the server classpath for
          this!!!)
          Secondly, enable debugging in Weblogic, which will give you some
          information: -Dweblogic.Debug.DebugMessagingBridgeStartup=true -Dweblogic.Debug.DebugMessagingBridgeRuntime=true -Dweblogic.Debug.DebugMessagingBridgeRuntimeVerbose=true
          IF you have more questions, pls reply also be mail.
          Bart
          Schelstraete Bart
          [email protected]
          http://www.schelstraete.org
          http://www.linkedin.com/in/bschelst

Advantage of Messaging Bridge

          Hi,
          We are using WebLogic as our application server. We want to send JMS messages
          to an external MQSeries listener. And we also want the JMS listener within WebLogic
          can received JMS messages sent by MQSeries. Besides using Messaging Bridge, we
          can also use MQSeries classes within WebLogic JVM. For example, we can create
          an MQSeries message listener inside WebLogic.
          Could anyone tell us what the advantage of using Messaging Bridge instead of MQSeries
          classes?
          Thanks.
          Ye Chen


1) MQ, of course, can not understand a WL dest as a target. To accomplish
          this, encode an MQ destination into a message property (and not ReplyTo), have the MQ
          side respond to this MQ destination, and bridge from the MQ response dest
          into a WL response dest. Alternatively to the bridge, encode a WL dest
          into the property and have the MQ side use the WL client library directly.
          2) If your WL client needs to post synchronous receives into
          MQ land, what is preventing you from directly using the MQSeries JMS client
          libraries to do this? Just treat it like any other MQ client.
          A bridge solution improves high-availability, as the MQ side
          need not be up 100% of the time for the WL side to function, but your app
          may not need this. A bridge solution also is helpful in handling the
          cross-vendor transactions, if you need exactly once, but again, you
          can do this on your own...
          Tom
          Ye Chen wrote:
          > Hi,
          >
          > Thank you for your response.
          >
          > In our case, we have two different systems locating in different VMs: one running
          > WebLogic server, the other running MQSeries server. We want JMS messages can be
          > exchanged between these two system. But the MQSeries part can only understand
          > and send MQSeries' JMS messages. That means our WebLogic part must have the ability
          > to send and receive MQSeries' JMS messages.
          >
          > We did try the Messaging Bridge approach but we need to send synchronous messages
          > which means the sender will wait for the response message of receiver. We met
          > the following two problems.
          > 1. If we use temporary destination (temporary queue/topic), it seems Messaging
          > Bridge cannot handle temporary destinations at all.
          > 2. If we use a non-temporary destination and set it as the ReplyTo property of
          > the JMS message. For example, the WebLogic server sends out a message and set
          > the ReplyTo as the Topic "WebLogicReplyToDest". When the message is passed through
          > Messaging Bridge and received by the MQSeries listener, the listener cannot understand
          > that WebLogic destion. So the response cannot be sent back.
          >
          > Do you have any idea about how to send synchronous messages using Messaging Bridge?
          >
          > Thanks.
          >
          > Ye
          >
          > "Dongbo Xiao" <[email protected]> wrote:
          > >The messaging bridge has built-in capability of retry, transaction, and
          > >start/stop. With the retry policy, the bridge will re-establish the
          > >connection
          > >to the remote server after detecting a failure, therefore the bridge
          > >can
          > >tolerate temporary down time of the remote server. You can choose a
          > >proper quality of services according to the nature and requirement of
          > >your
          > >application. If needed, transaction will be involved automatically. You
          > >can also start and stop the bridge at any time. All of those can be done
          > >in
          > >your listener's code but just more work. With proper configuration you
          > >get all of those automatically in the bridge.
          > >
          > >However, the bridge only moves messages from one destination to another.
          > >You have to have a client listening to the target destination and doing
          > >your
          > >application logic.
          > >
          > >You can also use Message Driven Bean (MDB) within WebLogic to listen
          > >to
          > >a MQSeries destination. MDB has retry logic and transaction capability
          > >as
          > >well. However, I don't know if you can have the similar support from
          > >MQSeries for an external MQSeries listener listening to a WebLogic Server
          > >destination. You can also use a MDB in WebLogic, which listens to the
          > >WebLogic server destination and sends the messages to a MQSeries
          > >destination.
          > >Then you have to handle the retries of connection to the MQSeries queue
          > >manager yourself for sending the messages.
          > >
          > >Hope this helps.
          > >
          > >Dongbo
          > >
          > >"Ye Chen" <[email protected]> wrote in message
          > >news:[email protected]...
          > >>
          > >> Hi,
          > >>
          > >> We are using WebLogic as our application server. We want to send JMS
          > >messages
          > >> to an external MQSeries listener. And we also want the JMS listener
          > >within
          > >WebLogic
          > >> can received JMS messages sent by MQSeries. Besides using Messaging
          > >Bridge, we
          > >> can also use MQSeries classes within WebLogic JVM. For example, we
          > >can
          > >create
          > >> an MQSeries message listener inside WebLogic.
          > >>
          > >> Could anyone tell us what the advantage of using Messaging Bridge instead
          > >of MQSeries
          > >> classes?
          > >>
          > >> Thanks.
          > >>
          > >> Ye Chen
          > >>
          > >>
          > >
          > >

Modifying Message Bridge at Runtime

I'm trying to modify a message bridge at runtime. The message bridge is
          between two local Queues.
          What I'm trying to do is basically create an alias that points to one of
          many queues.
          For example, I want my workflow to always look up the queue with JNDI
          name A, but at runtime I want messages sent to A to really go to one of
          B,C,D. So, I create a message bridge from A to B, then want to change at
          runtime from A to C or A to D.
          Now, the message bridge works for the configuration that is setup when
          the server starts, but at runtime, changing the message bridge
          configuration via the admin console does not work. The messages are not
          forwarded after I do this. If I stop and start the server, the messages
          are forwarded to the new destination correctly.
          This is a very critical component of our evaluation of the product, and
          is a must for us to use it in our system. We need the most runtime
          configuration/parameterization as possible since we will be in a 24/7
          environment.
          How can I get this to work? Is this a bug, or was runtime configuration
          never intended for such a change?
          Thanks


Hi Steven,
          This use for the bridge was not anticipated.
          The bridge's destination fields are marked "non-dynamic"
          on the console and in the mbean javadoc, but perhaps it
          is still possible to make the bridge do what you require.
          Did you try stopping and restarting just the bridge, rather
          than rebooting the whole server? If that doesn't work (and
          I'm told it likely won't), you can
          try undeploying and redeploying the bridge (set the target
          of the bridge to nothing, then set it back to its intended
          host server.) Both of these methods can be done fully
          programmatically via JMX mbeans. I think they can
          even be scripted via weblogic.Admin (but I'm not sure how.)
          Tom, BEA
          P.S. Instead of the bridge, you could write your own
          forwarding mechanism - which would give you full flexibility.
          There is example forwarding code in appendices for
          the JMS Performance Guide whitepaper on dev2dev:
          http://dev-test.bea.com:90/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp
          P.P.S. Instead of one bridge, you could have multiple: one
          per remote destination. Then, if you need to change
          the remote destination, undeploy the current bridge
          and deploy the desired bridge. This can be
          done via the console or programmatically.
          P.P.P.S. If this issue is really a "deal-breaker", I suggest
          making sure that your BEA sales-person knows this, so that
          they have the opportunity to make suggestions.
          Steven Ostrowski wrote:
          > I'm trying to modify a message bridge at runtime. The message bridge is
          > between two local Queues.
          >
          > What I'm trying to do is basically create an alias that points to one of
          > many queues.
          >
          > For example, I want my workflow to always look up the queue with JNDI
          > name A, but at runtime I want messages sent to A to really go to one of
          > B,C,D. So, I create a message bridge from A to B, then want to change at
          > runtime from A to C or A to D.
          >
          > Now, the message bridge works for the configuration that is setup when
          > the server starts, but at runtime, changing the message bridge
          > configuration via the admin console does not work. The messages are not
          > forwarded after I do this. If I stop and start the server, the messages
          > are forwarded to the new destination correctly.
          >
          > This is a very critical component of our evaluation of the product, and
          > is a must for us to use it in our system. We need the most runtime
          > configuration/parameterization as possible since we will be in a 24/7
          > environment.
          >
          > How can I get this to work? Is this a bug, or was runtime configuration
          > never intended for such a change?
          >
          > Thanks
          >

Using Messaging Bridge with Distributed Destinations

I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
          * WLS Server1:
          * JMS Server1:
          * inbound queue
          * outbound queue
          * JMS Server2:
          * inbound queue
          * outbound queue
          * WLS Server 2:
          * JMS Server3:
          * inbound queue
          * outbound queue
          A distributed destination is configured for the inbound and outbound queues.
          Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
          Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
          Any suggestions?


Hi Rob,
          Consumers on distributed destinations are always pinned
          to a single physical destination on creation. Only
          producers can round-robin each message. When a
          distributed destination is used as a source destination,
          you will need to configure a bridge per distributed
          destination. Alternatively, you can enable
          forwarding between the physical queues, which automatically
          forwards messages from physical queues with
          no consumers to physical queues that have consumers
          (but the extra hop impacts performance). For more information,
          consult the JMS documentation.
          Tom
          Rob McArthur wrote:
          > I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
          > * WLS Server1:
          > * JMS Server1:
          > * inbound queue
          > * outbound queue
          > * JMS Server2:
          > * inbound queue
          > * outbound queue
          > * WLS Server 2:
          > * JMS Server3:
          > * inbound queue
          > * outbound queue
          >
          > A distributed destination is configured for the inbound and outbound queues.
          >
          > Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
          >
          > Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
          >
          > Any suggestions?
          >
          >

When opening Bridge (CS6) I get the following 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" I tried and after selecting purge cache it does not a

When opening Bridge (CS6) I get the following 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" I tried and after selecting purge cache it does not allow me to select OK. Also Bridge keeps saying "Building Criteria" with the spinning wheel and nothing happens. I tried uninstalling and reinstalling to no avail. Please help:)

Maybe a Preferences reset can help:
Numerous program settings are stored in the Adobe Bridge preferences file, including display, Adobe Photo Downloader, performance, and file-handling options.
Restoring preferences returns settings to their defaults and can often correct unusual application behavior.
Press and hold the Ctrl key (Windows) or the Option key (Mac OS) while starting Adobe Bridge.
In the Reset Settings dialog box, select one or more of the following options:
Reset Preferences
Returns preferences to their factory defaults. Some labels and ratings may be lost. Adobe Bridge creates a new preferences file when it starts.
Purge Entire Thumbnail Cache
Purging the thumbnail cache can help if Adobe Bridge is not displaying thumbnails properly. Adobe Bridge re-creates the thumbnail cache when it starts.
Reset Standard Workspaces
Returns Adobe predefined workspaces to their factory default configurations.
Click OK, or click Cancel to open Adobe Bridge without resetting preferences.

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

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!

Message bridge example

Similar Messages

Maybe you are looking for