Message Bridge to Cluster
Hey guys,
I'm trying to configure a message bridge to a cluster of servers. When configuring the destination portion of the bridge, I entered server 1 connection url and messages went to that one server. I shut the server down to see if the bridge would send messages to any of the other servers and it didn't.
So in the destination bridge connection url I entered all the addresses of the servers in the cluster and got the following error when restarting the JMS server:
<Feb 22, 2010 2:00:09 PM EST> <Warning> <Connector> <BEA-190032> << eis/jms/WLSC
onnectionFactoryJNDIXA > ResourceAllocationException thrown by resource adapter
on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.R
esourceException: ConnectionFactory: failed to get initial context (InitialConte
xtFactory =weblogic.jndi.WLInitialContextFactory, url = t3://localhost:9015,t3:/
/localhost:9016,t3://localhost:9017, user name = null) ">
Do I need a separate bridge for each server or how would I configure the bridge to randomly pick a server to send message to?
In the cluster there is a distributed queue module targeted to all the machines in the cluster.
Thanks for viewing and any helpful replies
Changed the connection url to the cluster url address fixed problem :)
But its still not working :(
Think the problem now is my cluster jms server. It's currently targeted to my first server in the cluster, which is the one I'm shutting down. In the articles I've read supposely the jms sever will move to another server within the cluster?
Help!
Thanks
Similar Messages
-
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 -
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…. -
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 -
Messaging Bridge & Managed Server
Hi,
I am trying to use the messaging bridge in a cluster
(WLS61SP3 with CR081404_61sp3.jar + CR081511_61sp3.jar),
but I am getting the following error on startup of one
of my managed servers (error attached).
What am I doing wrong here?
Regards,
-Per
[error.txt]
Hi,
Came up with the idea of putting the jmsadapter.jar archive (included in the jms-xa-adp.rar
archive) in the system classpath,
of my managed servers.
This was mentioned in a previous posting I found, and now it seems to be working...
-Per
####<12.sep.02 09:34:18 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! creating bridge
bridgeOne>
####<12.sep.02 09:34:21 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge bridgeOne's
source properties are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = t3://localhost:7011
DestinationType = Queue
DestinationJNDIName = XmlQueue2
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = connFac>
####<12.sep.02 09:34:21 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge bridgeOne's
target properties are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = t3://localhost:8011
DestinationType = Queue
DestinationJNDIName = queue
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = connFac>
####<12.sep.02 09:34:21 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge bridgeOne
is successfully initialized>
####<12.sep.02 09:34:21 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200004> <Messaging Bridge "bridgeOne" has been successfully
deployed.>
####<12.sep.02 09:34:25 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200012> <Bridge
"bridgeOne" suceesfully found the two adapters configured for it.>
####<12.sep.02 09:34:25 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging STARTUP! BridgeBridge bridgeOne forwarding policy is AUTO>
####<12.sep.02 09:34:25 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200033> <Bridge
"bridgeOne" is getting the connections to the two adapters.>
####<12.sep.02 09:34:25 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Getting source connection>
####<12.sep.02 09:34:26 CEST> <Notice> <WebLogicServer> <6S19FHGZN2CM> <serverone>
<ListenThread> <system> <> <000202> <ListenThread listening on port 7011>
####<12.sep.02 09:34:26 CEST> <Notice> <WebLogicServer> <6S19FHGZN2CM> <serverone>
<SSLListenThread> <system> <> <000202> <SSLListenThread listening on port 7012>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:28 CEST> <Info> <Management> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'1' for queue: '__weblogic_admin_rmi_queue'> <system> <> <141060> <Reconnected
to Admin Server running at http://6S19FHGZN2CM:7001 from Managed Server - serverone.>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190035> <There was/were 1 physical
connection(s) created with the following Meta Data: Product name of EIS instance:
Java Messaging Service Product version of EIS instance: 1.0.2 Maximum number of
connections supported from different processes: 0 User name for connection: system>
####<12.sep.02 09:34:29 CEST> <Notice> <Cluster> <6S19FHGZN2CM> <serverone> <main>
<system> <> <000102> <Listening for multicast messages (cluster MyCluster) on
port 7011 at address 224.0.0.1>
####<12.sep.02 09:34:29 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Successfully got connection to the
source destination>
####<12.sep.02 09:34:29 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Getting target connection>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:29 CEST> <Notice> <WebLogicServer> <6S19FHGZN2CM> <serverone>
<main> <system> <> <000330> <Started WebLogic Managed Server "serverone" for domain
"dmsdomain" running in Production Mode>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:30 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190035> <There was/were 1 physical
connection(s) created with the following Meta Data: Product name of EIS instance:
Java Messaging Service Product version of EIS instance: 1.0.2 Maximum number of
connections supported from different processes: 0 User name for connection: system>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Successfully got connection to the
target destination>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne: both source and target adapters support
XA = true>
####<12.sep.02 09:34:30 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200032> <Bridge
"bridgeOne" is configured not to allow degradation of its quality of service in
cases where the configured quality of service is not reachable.>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne supportsMDBTX = true supportsXA = true
async = true>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne WorkMode = Exactly-once>
####<12.sep.02 09:34:30 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200030> <Bridge
"bridgeOne" is configured to work in "Exactly-once" mode and it is actually working
in "Exactly-once" mode.>
####<12.sep.02 09:34:30 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200028> <Bridge
"bridgeOne" starts transferring messages.>
####<12.sep.02 09:35:29 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <> <> <200027> <Bridge "bridgeOne"
works in asynchronous mode and has not received messages for the predefined maximum
idle time. The connections to the adapters will be interrupted and re-established.>
####<12.sep.02 09:35:29 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <> <> <200020> <Bridge "bridgeOne"
is stopped.>
####<12.sep.02 09:35:29 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <> <> <200033> <Bridge "bridgeOne"
is getting the connections to the two adapters.>
"Per Mengshoel" <[email protected]> wrote:
>
>Hi,
>
>I got the patch, but didn't quite succeed in configuring
>it... I am getting exceptions in the managed server's log.
>
>Ideas?
>-Per
>
>####<12.sep.02 08:44:58 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! creating
>bridge
>bridgeOne>
>####<12.sep.02 08:44:59 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge
>bridgeOne's
>source properties are:
> AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
> Classpath=null
> ConnectionURL = t3://localhost:7011
> DestinationType = Queue
> DestinationJNDIName = XmlQueue2
> InitialContextFactory = weblogic.jndi.WLInitialContextFactory
> ConnectionFactoryJNDIName = connFac>
>####<12.sep.02 08:44:59 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge
>bridgeOne's
>target properties are:
> AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
> Classpath=null
> ConnectionURL = t3://localhost:8011
> DestinationType = Queue
> DestinationJNDIName = queue
> InitialContextFactory = weblogic.jndi.WLInitialContextFactory
> ConnectionFactoryJNDIName = connFac>
>####<12.sep.02 08:44:59 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge
>bridgeOne
>is successfully initialized>
>####<12.sep.02 08:44:59 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200004> <Messaging Bridge "bridgeOne" has been successfully
>deployed.>
>####<12.sep.02 08:44:59 CEST> <Info> <HTTP> <6S19FHGZN2CM> <serverone>
><main>
><system> <> <101133> <Initializing WEB server serverone>
>####<12.sep.02 08:45:01 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200012>
><Bridge
>"bridgeOne" suceesfully found the two adapters configured for it.>
>####<12.sep.02 08:45:02 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006>
><Messaging
>Bridge Debugging STARTUP! BridgeBridge bridgeOne forwarding policy is
>AUTO>
>####<12.sep.02 08:45:02 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200033>
><Bridge
>"bridgeOne" is getting the connections to the two adapters.>
>####<12.sep.02 08:45:02 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006>
><Messaging
>Bridge Debugging RUNTIME! Bridge bridgeOne Getting source connection>
>
>####<12.sep.02 08:45:02 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200042>
><Bridge
>"bridgeOne" failed to connect to the source destination and will try
>again in
>20 seconds. (java.lang.Exception: javax.resource.ResourceException: Problem
>granting
>connection request to a ManagedConnectionFactory which does not exist
>in connection
>pool. Check your MCF's hashcode()
> at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:149)
> at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:20)
> at weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMSBaseConnectionFactory.java:97)
> at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:696)
> at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:901)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>)>
>
>
>"Dongbo Xiao" <[email protected]> wrote:
>>This is a known problem in the adapter deployment area.
>>Contact BEA customer support and ask about CR083563.
>>
>>Dongbo
>>
>>"Per Mengshoel" <[email protected]> wrote in message
>>news:[email protected]...
>>>
>>> Hi,
>>>
>>> I am trying to use the messaging bridge in a cluster
>>> (WLS61SP3 with CR081404_61sp3.jar + CR081511_61sp3.jar),
>>> but I am getting the following error on startup of one
>>> of my managed servers (error attached).
>>>
>>> What am I doing wrong here?
>>>
>>> Regards,
>>> -Per
>>>
>>>
>>
>>
>
-
Targeting a message bridge in 10.0
I have created a JMS message bridge in version 10.0 that is bridging a topic and a queue (topic-->queue). I'm running in a cluster and I want to make sure that the bridge is always running. The documentation implies that you can target a bridge to a migratable target but when I go to the target tab on the bridge I only see my cluster available, not the migratable targets. It is not really clear how the bridge is deployed when you target a cluster, nor does is appear to survive migration of the JMS service or restarting of servers in the cluster.
Am I doing something wrong or is it not possible to treat a bridge as a "pinned" service?Tony
that I am abe to see the shift key to constrain movement in the timeline and the viewer does not work, I have also resorted to markers on the timeline.
Tony -
Messaging Bridge/Resource adapter problem on Solaris?
Has anyone successfully used the supplied resource adapter and messaging bridge
on Solaris? We seem to have problems getting the resource adapter to be bound
properly. After creating a connector through the admin console (using any of the
weblogic supplied jms-*-adp.rar files) the element shows up in the JNDI tree but
has no object information associated with it - which I assume means it is not
bound. The following error shows up in the weblogic log file:
####<Jan 24, 2003 6:28:03 PM CST> <Error> <Connector> <fssun02> <AdminServer>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <kernel identity>
<> <190004> <ManagedConnectionFactory not found for jndiName eis/jms/WLSConnectionFactoryJNDINoTX.>
We are using WL 7.0.1.0 and Solaris 2.8 (8). With the same configuration on Win
2K everything works properly. Classpath's etc all seem to be correct. Any ideas?
thanks,
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 -
Hi friends,
I've a strange problem. I've posted a problem on another newsgroup concerning remote lookup as you can see below.
I'm working on WLS8.1sp2. 2 clusters (front-end with webapps and back-end with ejbs with a firewall without nat between they). Message bridges deployed on back end.
When that problem during loockup(see below) occurs I noticed also this exception regarding message bridge:
####<Jun 6, 2005 6:26:38 PM CEST> <Warning> <MessagingBridge> for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-200026> <Bridge "Bridge1-SourceWLXQueueSend > TargetWLSQueueSend" 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:
java.io.EOFException.)>
####<Jun 6, 2005 6:26:38 PM CEST> <Error> <MessagingBridge> <ExecuteThread: '120' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <BEA1-009BCF7999A0A21B1158> <BEA-200015> <An error occurred in bridge "Bridge1-SourceWLXQueueSend > TargetWLSQueueSend" during the transfer of messages (javax.resource.ResourceException: Error receiving message).>
I'm working on weblogic server 81.sp2.
I've 2 clusters (front-end cluster with web apps and back-end cluster with ejbs) with 2 active server per cluster.
Randomically when I try to make a lookup on the back-end cluster with a servlet deployed in the front-end cluster I received the following error:
javax.naming.CommunicationException. Root exception is java.rmi.ConnectExceptio
n: Unable to get direct or routed connection to: '7425491688784079753S:cihpas04:
[7200,7200,-1,-1,7200,-1,-1,0,0]:cihpas03:7100,cihpas03:7300,cihpas03:7500,cihpa
s04:7200,cihpas04:7400,cihpas04:7600:cie:CIEServer2'
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.j
ava:108)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:244)
at weblogic.jndi.internal.ServerNamingNode_812_WLStub.lookup(Unknown Sou
rce)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:343)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:336)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at Cie.servlet.SSCE.CIE045_Ping_Servlet.service(CIE045_Ping_Servlet.java
:157)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Can you help me for both problems?tnx in advancegabriele.folchi,
did you ever resolved this issue ? -
JMS Messaging Bridge Problems with WLS 8.1 sp2
Thank you in advance for your help.
I am trying to configure a JSM Messaging Bridge to connect an MQ Q to a Weblogic
Q. I have this working wonderfully in an environment without clustering but once
I try to deploy to a cluster, I am having two major problems.
1) When the managed servers are restarted, the messaging bridges immediately complain
about not being able to find the resource adaptor. After I manually un-target
the messaging bridge from the cluster and re-target them, they find the resource
adaptor but cannot connect to the source... which leads to my next problem.
2) The messaging bridges cannot connect to the source destination whether it is
an MQ Q or a Weblogic JMS Q does not matter. Here are the log entries that I
see relative:
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Got Notification:weblogic.management.AttributeAddNotification:
Deployments from <null> to [Caching Stub]Proxy for eBusDev02:Location=secaServer01,Name=seca_OES_ADV_REPLY
Messaging Bridge,Type=MessagingBridgeConfig - weblogic.management.AttributeAddNotification[source=eBusDev02:Location=secaServer01,Name=secaServer01,Type=ServerConfig].>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! creating bridge seca_OES_ADV_REPLY Messaging
Bridge.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
is deployed as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Initializging bridge seca_OES_ADV_REPLY Messaging
Bridge as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
source configurations are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = file:/e:/private/JNDI/eBusDev02
DestinationType = Queue
DestinationJNDIName = jms.oes.MQ-ADV-REPLYQ
InitialContextFactory = com.sun.jndi.fscontext.RefFSContextFactory
ConnectionFactoryJNDIName = jms.oes.MQ-QCF
.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
target configurations are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = t3://30.135.10.63:8103,30.135.10.63:8104
DestinationType = Queue
DestinationJNDIName = jms/oes/ADV-REPLYQ
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = jms/oes/QCF
.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
is successfully initialized.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
has been successfully initialized as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Activating bridge seca_OES_ADV_REPLY Messaging
Bridge.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
has been successfully activated..>
####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200033>
<Bridge "seca_OES_ADV_REPLY Messaging Bridge" is obtaining connections to the
two adapters.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
Getting source connection.>
####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200042>
<Bridge seca_OES_ADV_REPLY Messaging Bridge failed to connect to the source destination
and will try again in 15 seconds. (java.lang.NullPointerException)>
I know the queues are up and I am pretty sure my MQ client configuration is correct.
Is there anyway to get more information about the NullPointerException or the
error being encountered?
Given that you have ruled out message backlogs, my first suspicion is that the leak has something to do with connection allocation. Does JMS stats reveal an application generated connection leak? Check to see if the current number of connections/sessions stays steady.
If this doesn't help, you can use a third party tool like OptimizeIt to get periodic snap-shots of memory usage and identify the leaked object (or create a reproducer and have customer support do it). A possible work-around is to modify your app to pool JMS connections/sessions for re-use - greatly reducing the number of connections created per day.
Tom -
Hi Tom,
Message Bridge is configured to transfer messages from AQ to DQ.
When the Message Bridge is deployed on Admin Server & Cluster, it works successfully. But, a closer look reveals that it’s the instance deployed on the Admin Server (and not the ones on the cluster) which is doing the job of looking up AQ & DQ and transferring messages from AQ to DQ. Monitoring Message Bridge instances on the cluster shows "WARN: failed to look up the source adapter." The corrective action for this is "Check if the adapter is deployed or the JNDI name in the source JMSBridgeDestination instance is correct.". But the adapter is correctly deployed and the JNDI name of the AQ is correctly bound, else the Message Bridge wouldn't have shown "Forwarding messages." for Admin Server's Message Bridge instances. The same set of configuration (MB destinations and MB) is shared by the Message Bridge instances on Admin Server & Cluster. So, the question of incorrect configuration of the JMS destinations i.e. AQ & DQ doesn't arise.
Can you point out where the problem could be ? ?:|
Cheers
DipsPatch for this problem should be added to the front of your WLS instance's CLASSPATH prior to any weblogic classes. This issue is resolved in WLS 8.1 SP3 and this is the recommended path to resolution, the patch should be used only if one can't upgrade to SP3.
CR126671
Setup a cluster configuration on 8.1SP1 with at least on managed server in the cluster. Deploy the bridge adapter jms-xa-adp.rar to the cluster. Configure a bridge and target it to the cluster.Bridge never receives Add
Notification for the adapter. However, if you retarget the adapter to the individual servers in the cluster it works fine.
Dips -
Message Bridge error:Connection Factory
Hi
I am trying to build a Message Bridge accross two domains which are using the same version of Weblogic Server(8.1).
I am running into this error..
<Warning> <Connector> <BEA-190032> << Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException of javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = , user name =) on createManagedConnection.>
Please could anybody help me with this.Hi,
This exception indicates a failure to establish a JNDI context for either the source or target destination host. Check if the the bridge's configured URLs for both are correct. I'm not 100% sure, but it is likely that no URL need be configured for destination's that are in the same cluster as the bridge.
For more information, I suggest looking at the Messaging Bridge FAQ, which contains some troubleshooting tips. You can find a link to it here:
http://dev2dev.bea.com/technologies/jms/index.jsp
Tom Barnes, BEA -
Message Bridge error "Received message with no URI property"
I have created a message bridge between two weblogic JMS servers on different domains.
Message bridge has source and destinations.
I have tested each ques seperately with MDB deployed on each server.
When i am putting message on source que then i am getting this error "Received message with no URI property"
It would be grat help if some could tell me what might be going wrong.
Thanks
AkashHi,
This exception indicates a failure to establish a JNDI context for either the source or target destination host. Check if the the bridge's configured URLs for both are correct. I'm not 100% sure, but it is likely that no URL need be configured for destination's that are in the same cluster as the bridge.
For more information, I suggest looking at the Messaging Bridge FAQ, which contains some troubleshooting tips. You can find a link to it here:
http://dev2dev.bea.com/technologies/jms/index.jsp
Tom Barnes, BEA -
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 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
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!
Maybe you are looking for
-
Can i use a 85 watt charger with a new macbook air
Can i use a 85 watt charger with a new macbook air that comes with a 45 watt charger. One says its 14.8 volts and the other is 20 volts.
-
All of the other Digital Asset Management (DAM) software packages that I have used manage offline storage. Some have built-in capability to burn CD/DVD's; others just recognize that it has been done. However, all of them track the offline media by se
-
HT204053 Why can I not get my cell to verify where email is ??
You help me out a lot! Thank you
-
How to store pdf file to presentation or application server, as i mentioned
hi, I have used SO_NEW_DOCUMENT_ATT_SEND_API1 function module to send employ details through mail generating individual pdf files for each.but i need a copy of all files on to my computer also which has send through mail, what should i do?, can any o
-
How to wipe computer in bios options
Hi my name is Hemi and I recently tried to update my HP envy m6 to windows 8.1, but while halve way through, it overheated and shut down. I turned it back on, then it said restoring previous version of windows, then died. No when I start up all that