Messaging Bridge keeps dying

I am using weblogic 10.3 on sunos and i am seeing this issue where the messaging bridges keep dying ever so often(once or twice a week). I have over 15 servers in the weblogic domain but out of them only 2-3 messaging bridges die at random. The issue is compounded by the fact that the weblogic logs say unable to connect to source destination will retry later but weblogic never retries. I can't see any configuration where i can configure duration and number of retries for messaging bridges. Does anyone know how to fix this problem?

Ok is there a way anyone knows of by which we can reset the messaging bridge from the admin console without having to restart the managed server?

Similar Messages

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!

Keep-alive message bridge connection

Hi,
I have setup messaging bridge between WLS 10.3.0.0 and a JBoss Messaging queque, after about 4 hours of inactivity in a queue bridge was disconneted, is there any way to configure keep-alive connection in WLS bridge ?
Thanks,
Lukasz

You can try to set the IdleTimeMaximum setting on your bridge configuration to a very large number. It specifies the maximum amount of time, in seconds, that a messaging bridge instance remains idle.
In “asynchronous” mode, this is the longest amount of time a messaging bridge instance stays idle before it checks the sanity of its connection to the source. In “synchronous” mode, this is the amount of time the messaging bridge can block on a receive call if no transaction is involved.
-Dongbo

My ipod wont turn on, it keeps dying even if i leave it in charge the whole night and then after it dies it wont turn on the apple logo keeps flashing on and off and it also doesnt let merestore

My ipod touch 5th gen wont turn on. it keeps dying sometimes it would die even if it was in charge, once it dies it doesnt turn on it keeps flashingthe apple logo and so i put it to restore and while it was restoring it said that there was an error and that it couldnt restore my ipod so i took it out of chrage and put it back in and it showed that my ipod was dead so then after a while it turned on and it showed the connect to itunes sign i connexct it to itunes but itunes doesnt let me restore or update. so i took it out of the usb that was plugged to my laptop and it showed that it was charging but it was dead, i left it in chrage for 3 hours and i dont know what happend but now it completly wont turn on

You said "while it was restoring it said that there was an error ".
What was the wording of the error message?
Also:
Not Charge
- See:
iPod touch: Hardware troubleshooting
iPhone and iPod touch: Charging the battery
If you can’t charge your iPhone, iPad, or iPod touch
- Try another cable. The cable for 5G iPod (lightning connector) seems to be more prone to failure than the older cable.
- If a 5G iPod
Iphone 5 lightning port charging problem - SOLUTION!
- Try another charging source
- Inspect the dock connector on the iPod for bent or missing contacts, foreign material, corroded contacts, broken, missing or cracked plastic.
- Make an appointment at the Genius Bar of an Apple store.
Apple Retail Store - Genius Bar

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.

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

MQ Series, Messaging Bridge, weblogic 7.0

          Hi all,
          I have seen other postings about this with some clues as to why I am having this
          problem, but I still can't seem to resolve. I have already tried to gleen some
          clues from the documentation that comes with the beta bridge to be used with 6.1
          (wls_mqseries.pdf). Has anyone configure Weblogic 7.0 successfully with the new
          Messaging Bridge? If so, could you summarize your steps and settings?
          I used the JMSAdmin tool to bind the factory and queue objects and setup the destinations
          on the WLS console, but the log keeps spitting out the following:
          <Jul 26, 2002 11:28:21 AM EDT> <Warning> <Connector> <190032> << Weblogic Messag
          ing Bridge Adapter (XA) > ResourceAllocationException of javax.resource.Resource
          Exception: Failed to start the connection on createManagedConnection.>
          javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
          F
          ailed to start the connection
          at weblogic.connector.common.internal.ConnectionPool.makeResources(Conne
          ctionPool.java:993)
          at weblogic.connector.common.internal.ConnectionPool.getConnection(Conne
          ctionPool.java:1762)
          at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
          n(ConnectionPoolManager.java:163)
          at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
          ection(ConnectionManagerImpl.java:25)
          at weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMS
          BaseConnectionFactory.java:97)
          at weblogic.jms.bridge.internal.MessagingBridge.getConnections(Messaging
          Bridge.java:699)
          at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
          java:899)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
          <Jul 26, 2002 11:28:21 AM EDT> <Error> <Connector> <190006> <Error granting conn
          ection request.>
          <Jul 26, 2002 11:28:21 AM EDT> <Info> <MessagingBridge> <200042> <Bridge "MQ Ser
          ies Bridge" failed to connect to the source destination and will try again in
          55
          seconds. (javax.resource.spi.ResourceAllocationException: CreateManagedConnecti
          on Error: Failed to start the connection)>
          I can only tell that at startup, WLS is trying to establish a connection. Question:
          Connection to what? I haven't specified an MQ Series host or Queue Manager name
          anywhere yet.
          Thanks for your help,
          Mike Wright


          Tom,
          Thanks. The white paper seemed to have the info I needed.
          Now I just need to figure out why the lookup of the MQ objects return javax.naming.Reference
          rather than the actual object. I do have the ibm jar files in the classpath.
          Thanks,
          Mike
          Tom Barnes <[email protected]> wrote:
          >Have you read through the latest integrating foreign providers white-paper?
          > It is
          >available on dev2dev, or you can find it here:
          >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jms&item=9364&utag=
          >
          >Tom
          >
          >Mike Wright wrote:
          >
          >> Dongbo,
          >>
          >> I'm sorry, I didn't want to mislead you to think I didn't read the
          >docs prior
          >> to posting the question. I do have the bridge and both destinations
          >defined.
          >> Here are the settings I am using for the "source" destination.
          >>
          >> Name: MQJMS Bridge Destination Source
          >> Adapter JNDI Name: eis.jms.WLSConnectionFactoryJNDIXA
          >> Adapter Classpath:
          >>
          >> Connection URL: t3://10.9.0.21:9003
          >> Initial Context Factory: weblogic.jndi.WLInitialContextFactory
          >> Connection Factory JNDI Name: mqConnectionFactory
          >> Destination JNDI Name: mqDestSource
          >> Destination Type: Queue
          >>
          >> User Name:
          >>
          >> Using the JMSAdmin tool, I defined the connection factory and queue
          >objects which
          >> were bound to the JNDI tree, obviously.
          >> In order to connect using the IBM connection factory, you have to get
          >an instance
          >> of it and call the setter methods to specify the host, port, mode,
          >channel, etc.
          >> etc. Is weblogic trying to make a connection to MQ Series? How would
          >Weblogic
          >> know these settings without specifying anywhere?
          >>
          >> IBM connection factory: com.ibm.mq.jms.MQQueueConnectionFactory
          >> IBM Queue: com.ibm.mq.jms.MQQueue
          >>
          >> Thanks,
          >>
          >> Mike
          >>
          >> "Dongbo Xiao" <[email protected]> wrote:
          >> >Please see my comments inline.
          >> >
          >> >"Mike Wright" <[email protected]> wrote in message
          >> >news:[email protected]...
          >> >>
          >> >> Hi all,
          >> >>
          >> >> I have seen other postings about this with some clues as to why
          >I am
          >> >having this
          >> >> problem, but I still can't seem to resolve. I have already tried
          >to
          >> >gleen
          >> >some
          >> >> clues from the documentation that comes with the beta bridge to
          >be
          >> >used
          >> >with 6.1
          >> >> (wls_mqseries.pdf). Has anyone configure Weblogic 7.0 successfully
          >> >with
          >> >the new
          >> >> Messaging Bridge? If so, could you summarize your steps and settings?
          >> >>
          >> >
          >> >Here is the online doc
          >> >http://edocs.bea.com/wls/docs70/adminguide/msgbridge.html
          >> >
          >> >
          >> >> I used the JMSAdmin tool to bind the factory and queue objects and
          >> >setup
          >> >the destinations
          >> >> on the WLS console, but the log keeps spitting out the following:
          >> >>
          >> >> <Jul 26, 2002 11:28:21 AM EDT> <Warning> <Connector> <190032> <<
          >Weblogic
          >> >Messag
          >> >> ing Bridge Adapter (XA) > ResourceAllocationException of
          >> >javax.resource.Resource
          >> >> Exception: Failed to start the connection on createManagedConnection.>
          >> >> javax.resource.spi.ResourceAllocationException: CreateManagedConnection
          >> >Error:
          >> >> F
          >> >> ailed to start the connection
          >> >> at
          >> >weblogic.connector.common.internal.ConnectionPool.makeResources(Conne
          >> >> ctionPool.java:993)
          >> >> at
          >> >weblogic.connector.common.internal.ConnectionPool.getConnection(Conne
          >> >> ctionPool.java:1762)
          >> >> at
          >> >weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
          >> >> n(ConnectionPoolManager.java:163)
          >> >> at
          >> >weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
          >> >> ection(ConnectionManagerImpl.java:25)
          >> >> at
          >> >weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMS
          >> >> BaseConnectionFactory.java:97)
          >> >> at
          >> >weblogic.jms.bridge.internal.MessagingBridge.getConnections(Messaging
          >> >> Bridge.java:699)
          >> >> at
          >> >weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
          >> >> java:899)
          >> >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
          >> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
          >> >> <Jul 26, 2002 11:28:21 AM EDT> <Error> <Connector> <190006> <Error
          >> >granting conn
          >> >> ection request.>
          >> >> <Jul 26, 2002 11:28:21 AM EDT> <Info> <MessagingBridge> <200042>
          ><Bridge
          >> >"MQ Ser
          >> >> ies Bridge" failed to connect to the source destination and will
          >try
          >> >again
          >> >in
          >> >> 55
          >> >> seconds. (javax.resource.spi.ResourceAllocationException:
          >> >CreateManagedConnecti
          >> >> on Error: Failed to start the connection)>
          >> >>
          >> >> I can only tell that at startup, WLS is trying to establish a connection.
          >> >Question:
          >> >> Connection to what? I haven't specified an MQ Series host or Queue
          >> >Manager name
          >> >> anywhere yet.
          >> >>
          >> >
          >> >As you can see from the doc I mentioned earlier, you have to configure
          >> >the
          >> >source
          >> >and the target of the bridge (as two JMSBridgeDestination instances)
          >> >and the
          >> >bridge itself (as a MessagingBridge instance). In the JMSBridgeDestination
          >> >instance,
          >> >you have to specify a couple of attributes, including url, initial
          >context
          >> >factory,
          >> >connection factory JNDI, destination JNDI and destination type.
          >> >
          >> >I don't know what you configured from the console, but the bridge
          >instance
          >> >tried to connect to the source destination. Again, I don't know what
          >> >is the
          >> >source
          >> >you configured, therefore not sure if the bridge was trying to connect
          >> >to
          >> >MQSeries or WLS JMS.
          >> >
          >> >Hope this helps.
          >> >Dongbo
          >> >
          >> >
          >

2 non-clustered weblogic servers, 1 MQ queue. Messaging bridge fairness

Hey all,
          More of a general question. Has anyone ever had 2 non-clustered
          servers, each with a messaging bridge, pulling from one queue? If so, how is
          the fairness of the machines pulling.
          Assuming same machines / same configurations for the weblogic servers,
          should it be
          approximately fair?
          Just want to verify that if the pulling machine sees more messages after
          pulling it's batch,
          it doesn't keep the channel locked or antyhing, before we pursue this
          option.
          Thanks much,
          Greg


Hi Greg,
          The consumer fairness is up to the JMS provider, which sees the bridge
          as a regular consumer no different from any other client consumer.
          If the queue being pulled from is a WebLogic 6.0 or greater queue then
          fairness will be observed. (I'm not sure about earlier versions.) Of
          course, this "fairness" is proportional to the rates at which the
          consumers consume.
          There is no such guarantee for other providers. And in fact, we (BEA)
          have noticed that some of the other well-known JMS vendors do
          not exhibit fairness.
          Tom, BEA
          Greg Kaestle wrote:
          > Hey all,
          >
          > More of a general question. Has anyone ever had 2 non-clustered
          > servers, each with a messaging bridge, pulling from one queue? If so, how is
          > the fairness of the machines pulling.
          > Assuming same machines / same configurations for the weblogic servers,
          > should it be
          > approximately fair?
          >
          > Just want to verify that if the pulling machine sees more messages after
          > pulling it's batch,
          > it doesn't keep the channel locked or antyhing, before we pursue this
          > option.
          >
          > Thanks much,
          > Greg
          >
          >

Message bridge exception when using bridging to MQ

          hi ... was wondering if anyone could suggest what might be causing this.
          I have a weblogic 8.1 queue bridged to a MQ5.3 queue. I was successfully able
          to put messages (using the container to handle the XA) into the weblogic Q and
          have the bridge successfully pass the msg onto the MQ Q. However I have started
          getting the following error msgs on random occasions.(and the bridge is not able
          to transfer the msgs across). Any suggestions as to what might be causing this?
          Please let me know if you need any additional info.
          thanks,
          Rajat
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200033> <Bridge "JeInputBridge"
          is obta
          ining connections to the two adapters.>
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200032> <Bridge "JeInputBridge"
          is conf
          igured to disallow degradation of its quality of service in cases where the configured
          quality of se
          rvice is unreachable.>
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200030> <Bridge "JeInputBridge"
          is conf
          igured to work in "Exactly-once" mode, and it is actually working in "Exactly-once"
          mode.>
          <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200028> <The bridge
          "JeInputBridge" has
          started transferring messages.>
          <Nov 14, 2003 11:10:08 AM EST> <Error> <MessagingBridge> <BEA-200015> <An error
          occurred in bridge "
          JeInputBridge" during the transfer of messages (javax.resource.ResourceException:
          Exception during e
          nListResource).>
          <Nov 14, 2003 11:10:08 AM EST> <Warning> <MessagingBridge> <BEA-200026> <Bridge
          "JeInputBridge" enco
          untered some problems in one of its adapters or underlying systems. It stopped
          transferring messages
          and will try to reconnect to the adapters shortly. (The exception caught was
          weblogic.jms.bridge.in
          ternal.MessagingBridgeException.)>
          <Nov 14, 2003 11:10:09 AM EST> <Info> <MessagingBridge> <BEA-200020> <Bridge "JeInputBridge"
          is stop
          ped.>


I suggest that you contact BEA Customer Support so that somebody can spend more time working
          directly with you and solving the problem.
          Sorry for not being able to help you more.
          Dongbo
          Rajat wrote:
          > hi Dongbo ... i checked the MQ error logs and found the followign error:
          >
          > ----- amqccita.c : 2758 -------------------------------------------------------
          > 11/17/03 10:33:24 AM
          > AMQ9208: Error on receive from host AHEWVTBHALLRA1-1 (169.242.174.24).
          >
          > EXPLANATION:
          > An error occurred receiving data from AHEWVTBHALLRA1-1 (169.242.174.24) over
          > TCP/IP. This may be due to a communications failure.
          > ACTION:
          > The return code from the TCP/IP (read) call was 131 (X'83'). Record these
          > values and tell the systems administrator.
          >
          > I did a test and found out that the error above is logged when i shut down the
          > WLS and NOT when i get the message bridge exception. The MQ system Admin feels
          > that there is bug in WLS as shuttting down WLS should gracefully terminate the
          > MQ connection and not throw any exceptions on MQ. So looks like this another thing
          > i would need your help on. Any other suggestions on what to do regarding the message
          > bridge exception ?
          >
          > Thanks,
          > Rajat
          >
          > Dongbo Xiao <[email protected]> wrote:
          > >Hi Rajat,
          > >Did you look at the log or tracing on the MQSeries side as I suggested?
          > >If you don't see any suspicious error messages on the MQSeries side,
          > >I would suggest that
          > >you contact the BEA Customer Support.
          > >Thanks,
          > >Dongbo
          > >
          > >Rajat wrote:
          > >
          > >> hi Dongbo,
          > >>
          > >> The problem occurs regardless of whether i stop the bridge and restart
          > >it. As
          > >> mentioned earlier, this problem does not occur all the time. This morning
          > >i started
          > >> up WLS and the it was giving the error. I then stopped it and restarted
          > >WLS ...it
          > >> started working fine. I then stopped the bridge and restarted the bridge..and
          > >> the errror happened. I then stopped the WLS and restarted it ...and
          > >the problem
          > >> was still there.... i then stopped and restarted WLS and everything
          > >started working
          > >> fine. On one occasion a few days ago... the bridge was working fine..and
          > >then
          > >> all of a sudden started giving this error...and after a while it started
          > >working
          > >> again. Pls suggest next steps.
          > >>
          > >> Thanks,
          > >> Rajat
          > >>
          > >> Dongbo Xiao <[email protected]> wrote:
          > >> >
          > >> >Hi Rajat,
          > >> >
          > >> >I have looked at your log file after Tom bought to me attention of
          > >the
          > >> >problem you are
          > >> >having.
          > >> >The error message regarding the adapter at the startup
          > >> >(NoSuchMethodException) is not a problem. It is just an info message.
          > >> >I also noticed that the Input bridge had been stopped and restarted
          > >before
          > >> >the error
          > >> >occurred. Did you get the same error if you did not stop and restart
          > >> >the bridge?
          > >> >Looks like the connection was somehow closed on the MQSeries side
          > >after
          > >> >the bridge
          > >> >established a connection to it but before the bridge sent any message
          > >> >over.
          > >> >If the problem only occurs after you stop and restart the bridge,
          > >it
          > >> >more likely is
          > >> >a bug on the WLS side. Otherwise, I would suggest that you check
          > >the
          > >> >log (or tracing)
          > >> >of the queue manager on the MQSeries side and see if you can spot
          > >some
          > >> >problem on the
          > >> >MQSeries side.
          > >> >
          > >> >Thanks,
          > >> >Dongbo
          > >> >
          > >> >Rajat wrote:
          > >> >
          > >> >> hi Tom... i looked over the FAQs but did not spot anything that
          > >i was
          > >> >doing wrong.
          > >> >> I have attatched the stack trace with the JMS debugging. (Sorry
          > >for
          > >> >the large
          > >> >> file... but i spotted some failure msgs regarding the adapter at
          > >startup
          > >> >and i
          > >> >> would like you to take a look ..). I have two bridges setup...
          > >> >> - JeInputBridge - connects weblogic Q to MQ Q
          > >> >> - JeReplyBridge - connects MQ Q to weblogic Q
          > >> >>
          > >> >> I am using the eis.jms.WLSConnectionFactoryJNDIXA adapter and am
          > >using
          > >> >the QOS
          > >> >> = "Exactly-Once"
          > >> >>
          > >> >> The weird thing is that the JeReplyBridge has never shown this error....
          > >> >but the
          > >> >> JeInput bridge sometimes works fine... then starts giving the error.
          > >> >On occassions,
          > >> >> it will keep trying and eventually start working... and sometimes
          > >i
          > >> >have to restart
          > >> >> the weblogic server several times before it starts working.
          > >> >>
          > >> >> Any suggestions/advice will be much appreciated.
          > >> >> Thanks,
          > >> >> Rajat
          > >> >>
          > >> >> Tom Barnes <[email protected]> wrote:
          > >> >> >The information below is too generic to interpret. Were stack
          > >traces
          > >> >> >printed out? Anyhow, I suggest that your start with the
          > >> >> >7.0 messaging bridge FAQ (it also applies to 8.1) to get
          > >> >> >more information about how to diagnose bridge issues:
          > >> >> >
          > >> >> >http://edocs.bea.com/wls/docs70/faq/msgbridge.html
          > >> >> >
          > >> >> >Rajat wrote:
          > >> >> >
          > >> >> >> hi ... was wondering if anyone could suggest what might be causing
          > >> >> >this.
          > >> >> >>
          > >> >> >> I have a weblogic 8.1 queue bridged to a MQ5.3 queue. I was successfully
          > >> >> >able
          > >> >> >> to put messages (using the container to handle the XA) into the
          > >> >weblogic
          > >> >> >Q and
          > >> >> >> have the bridge successfully pass the msg onto the MQ Q. However
          > >> >I
          > >> >> >have started
          > >> >> >> getting the following error msgs on random occasions.(and the
          > >bridge
          > >> >> >is not able
          > >> >> >> to transfer the msgs across). Any suggestions as to what might
          > >be
          > >> >causing
          > >> >> >this?
          > >> >> >> Please let me know if you need any additional info.
          > >> >> >>
          > >> >> >> thanks,
          > >> >> >> Rajat
          > >> >> >>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200033>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is obta
          > >> >> >> ining connections to the two adapters.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200032>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is conf
          > >> >> >> igured to disallow degradation of its quality of service in cases
          > >> >where
          > >> >> >the configured
          > >> >> >> quality of se
          > >> >> >> rvice is unreachable.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200030>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is conf
          > >> >> >> igured to work in "Exactly-once" mode, and it is actually working
          > >> >in
          > >> >> >"Exactly-once"
          > >> >> >> mode.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Info> <MessagingBridge> <BEA-200028>
          > >> >> ><The bridge
          > >> >> >> "JeInputBridge" has
          > >> >> >> started transferring messages.>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Error> <MessagingBridge> <BEA-200015>
          > >> >> ><An error
          > >> >> >> occurred in bridge "
          > >> >> >> JeInputBridge" during the transfer of messages (javax.resource.ResourceException:
          > >> >> >> Exception during e
          > >> >> >> nListResource).>
          > >> >> >> <Nov 14, 2003 11:10:08 AM EST> <Warning> <MessagingBridge> <BEA-200026>
          > >> >> ><Bridge
          > >> >> >> "JeInputBridge" enco
          > >> >> >> untered some problems in one of its adapters or underlying systems.
          > >> >> >It stopped
          > >> >> >> transferring messages
          > >> >> >> and will try to reconnect to the adapters shortly. (The exception
          > >> >> >caught was
          > >> >> >> weblogic.jms.bridge.in
          > >> >> >> ternal.MessagingBridgeException.)>
          > >> >> >> <Nov 14, 2003 11:10:09 AM EST> <Info> <MessagingBridge> <BEA-200020>
          > >> >> ><Bridge "JeInputBridge"
          > >> >> >> is stop
          > >> >> >> ped.>
          > >> >> >
          > >> >>
          > >> >> ------------------------------------------------------------------------
          > >> >> Name: myserver.log
          > >> >> myserver.log Type: Text Document (application/x-unknown-content-type-txtfile)
          > >> >> Encoding: base64
          > >> >
          > >

Xdm keeps dying

After a recent upgrade to Solaris 9 the xdm keeps dying and restarted after about 5-10 minutes. I can speed this up by stopping and starting the script in the /etc/rc2.d/ directory but it still dies after about 5 minutes with no real error message to go on.

Stu
On another related subject... if my computer is 'chuffed' I don't understand about Apples approach to repairs and stuff... It was my understanding that if a piece of hardware was under a year old and suffered from a technical fault it was the responsibility of the company to replace/repair for free? Apple seem to only do 90 days? IS that right?
If I need a new part will I have to pay for parts and service even though I've had it less than a year (7 months)
Your Imac has 90 days phone support and 1 year parts and labour. If you phone after the 90 days is up they will ask for a credit card #, now if they find out it is a hardware issue you will not be charged.
Now if it won't power on at all I would thing it is a hardware issue, if it was a bad hard drive or corrupted software then it should turn on but not find the drive or the OS on the drive. Call Apple again and tell them you want it fixed or take it in you are still covered.
You should also think about extended warrentee which gives you a total of three years phone support and three years parts and labour. Keep us posted, Bob :~))

Why does my fully charged iPad 2 battery keep dying at 50% charge? I have updated to iOS 7 and this started happening. What could be the cause of it?

My iPad's battery keeps dying. When I plug it in and put it back on, the screen shows a drained battery. After a few moments it boots up. However, when I check the battery charge, it's at 52% or so. Can someone tell me what's causing this? And what can I do to fix it?

For proper reporting of the battery’s state of charge, be sure to go through at least one charge cycle per month (charging the battery to 100% and then completely running it down).
From Here > http://www.apple.com/batteries/ipad.html

New message window keeps popping up

The new message window keeps popping up without prompting, usually twice in a row. I notice
this particularly when I first open the Mail program. The funny thing is that you can't actually type in any text in the new message window. Any ideas???

It seemed to work itself out after several days.

I keep getting a notification that says "Google Talk authentication failed"...does anyone know how to get rid of this? I tried looking for it in the apps but not really sure what google talk is or how to get rid of this message that keeps popping up.

How do i get rid of the message that keeps popping up that says "google talk authentication failed"????

funwidowlady,
Good afternoon! I'm glad I can be here to help with this error. In the device this application is identified only as 'Talk', so that be more familiar to you. First I recommend opening the 'Market' app on your phone, then Menu>My Apps to see if this application requires an update. It will display a list on top of all applications that need to be updated. If nothing exists, tap 'Home' and go into 'Settings>Applications>Manage Applications>Talk, then tap 'Clear Cache' and 'Clear Data' to remove the history of that application and stop the notifications. The app will remain on your phone for future use, if you desire to take advantage of it. Read more about Google Talk here
Thank you!
AdamE_VZW
Follow us on Twitter @VZWSupport

TS1292 I bought a 4 pack of $25 Itunes gift cards and only 2 will activate. For the second two it just keeps asking for my login. No error message just keeps repeating the login

I bought a 4 pack of $25 Itunes gift cards and only 2 will activate. For the second two it just keeps asking for my login. No error message just keeps repeating the login. Is there any way to fix this or did I just lose $50

Report this here:
iTunes Store Support
http://www.apple.com/emea/support/itunes/contact.html

What to do?? -What to do?? - I just updated my iTunes to ver 11.2.1 because of the annoying messages they keep sending out. Now I can't play the movies and TV series I've purchased and were watchable before - This movie can be played only on displays that

What to do?? - I just updated my iTunes to ver 11.2.1 because of the annoying messages they keep sending out.
Now I can't play the movies and TV series I've purchased and were watchable before.
Comes up with "This movie can be played only on displays that support HDCP (High-bandwidth Digital Content Protection)."
The cheek of the matter is everytime I tried to get Apple support it comes up with a request for me to pay $54 for their support package, to fix a problem I didn't have until I complied to one of their update requests.
End of Rant!!! - Anyone know how to fix please?

Well, I wonder about all the responses...:)
Anyhow, I wound up "fixing" the problem by using the System Restore disks for the Mini. It's now running Tiger 10.4.11 (with all updates) and I copied my iTunes library over. It all works now. <shrug> I have no idea what the problem was, and I'm a bit leery of upgrading it to Leopard, so I think I'll just leave well enough alone.
Richard

Messaging Bridge keeps dying

Similar Messages

Maybe you are looking for