How to Montior Messaging Bridge weblogic 10.1?

I got few message bridges in wlS 10.1 environment . i am unable to find where the option to monotor bridge. ( wls docs showing got to server -> services-> bridge) "This page summarizes the messaging bridge instances that have been explicitly targeted to this Server" but its telling no items to display. I went throug the following steps but no luck
Monitor messaging bridge instances
To monitor the status of all configured messaging bridges in your domain:
In the left pane of the console, expand Environment and select Servers.
Select the specific server instance where the messaging bridge is configured.
In the right pane, select the top Services tab, then select Bridge.
Select the bridge instance whose status you want to monitor.
Same thing i do in 8.1 is servrver -> services->bridge under this tab there is optin "Monitor all messaging bridge runtimes" when we click on this it shows about ste status of all bridges configured for this sever (Active /Inactive)
Can some one help same option in wls 10.1
Thanks
Subba
Edited by: Subba R Kancharla on Feb 1, 2010 1:31 PM

Perhaps you're running into a bug, please consider opening a case with customer support. As a work-around, you might want to try using Java or WLST to find and display the bridge's JMX runtime mbean (MessagingBridgeRuntime).
Tom

Similar Messages

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

How to monitor Message Bridge runtime using WLST

Hi Readers,
I would like to monitor Message Bridge runtime on weblogic 8.1 using WLST script.
Can anybody tell if there is any possibility? Is there a MBEAN avaialble for Messaging Bridge.?
Edited by: user13254842 on 09-Sep-2010 23:17

Hi,
I don't recall whether the console provides a way to monitor the bridge, or whether the MessagingBridgeRuntimeMBean hangs off of some parent mbean, but you can obtain arbitrary mbeans using standard JMX query calls.
Some scratch code that I have:
private static MBeanServerConnection getConnection(
    String urlStr,
    String username,
    String password,
    String mbeanServer
) throws Exception {
    // This code implicitly requires weblogic classes to be in the classpath
    // in order to run efficiently, but its possible to get it to work without
    // any WL at all.   See
    //   http://e-docs.bea.com/wls/docs90/jmx/accessWLS.html#1118690
    // The code could be changed to automatically detect if WL is in
    // the classpath, and switch to "iiop" mode if it isn't.
    URI url = new URI(urlStr);
    Hashtable h = new Hashtable();
    h.put(Context.SECURITY_PRINCIPAL, username);
    h.put(Context.SECURITY_CREDENTIALS, password);
    h.put(
      JMXConnectorFactory.PROTOCOL_PROVIDER_PACKAGES,
      JMX_PROTOCOL_PROVIDER
    JMXServiceURL serviceURL = new JMXServiceURL(
       url.getScheme(), url.getHost(), url.getPort(), JMX_JNDI_ROOT + mbeanServe
    JMXConnector connector = JMXConnectorFactory.connect(serviceURL, h);
    return connector.getMBeanServerConnection();
conn = getConnection(url, user, pass, "weblogic.management.mbeanservers.domainruntime")
String type = "JMSServerRuntime";    // not sure may need to add "MBean" or strip off "Runtime", bridge = "MessagingBridgeRuntime"
Set xxx =    conn.queryMBeans(new ObjectName("*:Type=" + type + ",*"), null);Hope this helps,
Tom
Edited by: TomB on Jun 10, 2009 2:57 PM

How to configure Message bridge

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


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

Message bridge example

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

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

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

Weblogic 81 Messaging Bridge Logs

Hi All,
Do you know how can I change the weblogic logs only for the Messaging Bridge from Info level to Error level - I dont want to change the weblogic server log level to Error. Messaging Bridge is logging a lot of info at Info level which I dont want. I tried to use - changing Debug to Error but no luck.
-Dweblogic.Debug.DebugMessagingBridgeStartup=true
-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
Thanks much,
- Anand

I've heard that 9x and later logging has ways to configure log message suppression for a specific log message number or perhaps even specify a log level for a specific log message handler like bridge logging, but I don't know if there's something similar to 8.1. Here are a couple 9+ links:
http://www.gexperts.com/blog/archives/2008/06/entry_356.html
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/logging/filtering.html
Tom

Error occured in Messaging bridge in weblogic to MQ Series

Hi,
I am trying to send the message from weblogic JMS to MQ Server Queue using Message Bridging. All the configuration has been done in both Weblogic and MQ Server. Once creating the bridge, i am getting the following error.
<Feb 22, 2006 9:37:18 PM GMT+05:30> <Warning> <Connector> <BEA-190032> << Weblog
ic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAl
locationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
--Please give me the suggestion to fix this.
Thanks in Advance,
Sureshkannan Nagarajan

Hi,
I am trying to send the message from weblogic JMS to MQ Server Queue using Message Bridging. All the configuration has been done in both Weblogic and MQ Server. Once creating the bridge, i am getting the following error.
<Feb 22, 2006 9:37:18 PM GMT+05:30> <Warning> <Connector> <BEA-190032> << Weblog
ic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAl
locationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
--Please give me the suggestion to fix this.
Thanks in Advance,
Sureshkannan Nagarajan

Error occured in Message Bridging in Weblogic to MQ Server

Hi,
I am trying to send the message from weblogic JMS to MQ Server Queue using Message Bridging. All the configuration has been done in both Weblogic and MQ Server. Once creating the bridge, i am getting the following error.
<Feb 22, 2006 9:37:18 PM GMT+05:30> <Warning> <Connector> <BEA-190032> << Weblog
ic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAl
locationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
--Please give me the suggestion to fix this.
Thanks in Advance,
Sureshkannan Nagarajan

Hello Priya
If u r loading thru flat file
1. Check the correct path in infopackage
2. Check if it is opened,if it is then close it and run package again
If loading thru R/3
1. Check DS is not opened in change mode
2. Check if RSA3 is able to extract data...if it is then check in RSA7 and chk IDOC status...
3. Are you running init..then make sure no document is posted in R/3 side...
Thanks
Tripple k

Weblogic Message Bridge Producing Duplicate JMS Messages

We have a message bridge that we use to integrate with TIBCO. The message bridge is deployed on a WL cluster. We see duplicate JMS messages produced by the bridge when it is deployed on the cluster. We don't see this behavior when only one ManagedServer in the cluster is active,.
TIBCO version: 4.4.3 V5
WLS: 10.3.3 with patch for bug BUG8732539 (BQC6)
java -version
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2121-linux-x86_64, compiled mode)
We are also seeing a lot of exceptions related to
<May 27, 2011 4:11:57 PM PDT> <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
However the bridge is active. We are monitoring the message-out count on TIBCO and we observed that we see duplicates whenever there a message is re-delivered. We opened a case with Oracle support and they suggested patch 10258751 which didn't help. The next suggestion was a patch for "Bug 11852771 - [WLS10.3.2]MISSING AND DUPLICATE IN JMS QUEUE MESSAGE MONITORING" but I don't think it will help since our JMS consumers are getting duplicate messages and this is not just a UI issue.
Here is the message behavior when we send a single message:
Timelines
11:34:17 --> Message sent to TIBCO EMS queue
11:34:17 --> WL MS3 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:17 --> WL MS1 says it got the message and committed the transaction
11:34:17 --> Message is visible in the JMS queue in the admin console
11:34:17 --> TIBCO EMS has still not received an ACK from WL for the message
11:34:31 --> TIBCO EMS resends the same JMS message to WL
11:34:31 --> WL MS2 says it got the message and committed the transaction
11:34:31 --> WL MS1 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are two messages in the JMS queue)
11:34:31 --> TIBCO EMS has still not received an ACK from WL for the message
11:34:54 --> TIBCO EMS resends the same JMS message to WL
11:34:31 --> WL MS4 says it got the message and committed the transaction
11:34:31 --> WL MS2 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are three messages in the JMS queue)
11:34:31 --> TIBCO EMS receives an ACK from WL for the message
MS04
####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: true
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-6A59E8FE76C4FC4CA149
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <MS04> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<193654.1306521294611.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
MS03
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257342> <BEA-000000> <Bridge MessageBridge1 Successfully got connection to the target destination>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1: both source and target adapters support XA = true>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 supportsMDBTX = false supportsXA = true async = true>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 WorkMode = Exactly-once>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntimeVerbose> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 Entering processMessages() ------ >
####<May 27, 2011 11:34:17 AM PDT> <Error> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-3AA29116A4CA622834EA> <> <1306521257343> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'eis/jms/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:948)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:200)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:948)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
... 8 more
).>
####<May 27, 2011 11:34:17 AM PDT> <Warning> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257344> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
.)>
MS02
####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271386> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: true
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-679AF074F381152F047C
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271392> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<196075.1306521271386.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:54 AM PDT> <Error> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:225)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
... 2 more
).>
####<May 27, 2011 11:34:54 AM PDT> <Warning> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
MS01
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257536> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: false
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-72BC818FE2BB8C2655C6
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257542> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<195581.1306521257536.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:31 AM PDT> <Error> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:224)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
... 1 more
).>
####<May 27, 2011 11:34:31 AM PDT> <Warning> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
.)>

@Tom, thanks for your hints and sorry for my delayed response. Here are my answers to your queries…
-- Does messaging work, without any exceptions, when only one bridge is active?
It works fine when only one node of the cluster is active. -- I'm not familiar with Tibco monitoring, but I suspect that the "message-out count on TIBCO" stat doesn't always imply that there's a duplicate message. It could mean that an initial message delivery attempt failed, it's transaction rolled back, and the message was redelivered. Redelivery after a failure is normal - the original delivered message, if one actually made it onto a WebLogic queue, should be discarded by WebLogic when its failed transaction eventually rolls back (before its ever handed to a consumer application).
You are absolutely right. The mismatch in count was due to redelivery attempts. We could see that as soon as we turned on trace in TIBCO-- The posted stack traces look like they may be JVM stdout/stderr scrapes, which are often automatically truncated, for example, see the "... 8 more" listed at the bottom of one of the stack traces below. There might be more information in the full stack trace for the "Resource manager is unavailable" exception. Full traces are logged in each WebLogic Server's log files.
I tried redirecting the output and even set "stdout Stack Trace Depth:" to -1 but I am not albe to see the complete trace.-- The setTransactionTimeout NullPointerException error message looks like it is collateral damage from the original reported "Resource manager is unavailable" exception that's thrown earlier during the enlistResource() step. If you are truly getting duplicates, then I think this is a clue that the bridge is somehow (stupidly) trying to proceed with forwarding the message despite the fact that there's no current transaction on the thread... 
I have a case open with Oracle support and we have extensive debugging turned on. Here is what the engineer came back with. There is an issue with XA transactions in JCA adapter when it talks to third party providers like TIBCO. Since the resource names are not unique across the cluster, a XA transaction is started on multiple nodes in the cluster for the same message. All transactions abort but the message is persisted and TIBCO redelivers the message since the connection is severed when the transaction aborts. We were able to reproduce this scenario at will with our setup and Oracle was able to reproduce the issue too.  -- Can you check the state of the message on the WebLogic Q? The fact that a message is shown on the WL console doesn't necessarily mean that the state of the message is visible (it could be waiting for the transaction to commit - something that apparently never happens). On the console: Services -> Messaging -> JMS Modules -> [module name] -> [destination name]. 
Our consumer was getting duplicate messages. This confirms that the console was not giving us incorrect information. The console showed that 2/3/4 messages were in "current" state when we expected only one message. -- Make sure that the bridge's Tibco destination is a Tibco queue not a Tibco topic (it's happened). 
Yeah we made sure it was a Queue. -- Can you post your bridge and destination stanzas from your config.xml?  
Will try to do this shortly but have to strip out lot of information. -- I vaguely recall that there was a problem with untyped connection factories in Tibco at one point (not sure). You might want to try changing the Tibco configuration to spin-up "XA Queue Connection Factory" instead of just an "XA Connection Factory" (plus modify the bridge configuration accordingly). 
We tried this but it didn't eliminate this issue. One thing we did notice however was that the number of rollbacks were greatly reduced. 
Here is the workaround that Oracle is suggesting: Create pinned destinations and assign it to a distributed queue. This will keep the transactions local and hence eliminate the duplicate transactions and rollback. We tried it and it eliminated the dups issue. However I discovered another bug during my testing. Our cluster messaging mode is "Unicast" and message forwarding from zero consumer queues to queues with consumers fails. We have four/five nodes in the cluster and two consumer threads. I observed that the zero consumer queues always forward to one queue in the cluster that has consumers. The forwarding stalls when I bring down the node that has consumers. Again, we were able to reproduce this issue at will and Oracle has acknowledged that it is a bug. They've reported that Unicast fails without any warning whereas Multicast fails with a warning in the log. We have observed this message forwarding stalling even with UDQs.
I have another case open for an issue where our message bridges that transfer messages from TIBCO to WLS stalls after sometime. The status is shown as active but it is not doing anything. The server instance shows stuck threads trying to roll back a message. TIBCO logs indicate that it is receiving a request to rollback a transaction but it is not finding the transaction to rollback. The only way to recover from this condition is to restart the cluster. I am fairly confident that he root case for this issue is again the XA transaction issue. I changed our UDQ to pinned destination in one environment and we are no longer seeing dups or bridge stalling there. Hopefully Oracle can resolve the message forwarding issue.Thanks again….

Resource Allocation Issue in Weblogic messaging bridges

Hi,
We are using
Weblogic version à WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 WebLogic Temporary Patch for CR250915 04/18/2006 22:21:33
Java JDK version à 1.4.2_11
Oracle version à 9.2.08
Solaris version à Solaris 5.8
The weblogic application is deployed on Unix Solaris.
We have configured 8 message bridges within weblogic between the 8 Topics in weblogic (source JMS destination) and 8 topics in the External EMS server (Target JMS destination) .
The properties set for the message bridges are
1] AsyncEnabled ="true"
2] DurabilityEnabled ="true"
3] QualityOfService="Exactly-once"TransactionTimeout="10"
4] TransactionTimeout="10"
The source and target JMS destinations are bridge using the resource adapter of jms-xa-adp (connector module)
The properties for the Source JMS Destination are
1] ConnectionFactory = weblogic.jms.client.JMSXAConnectionFactory
The properties for the Target JMS Destination are
1] InitialContextFactory = com.tibco.tibjms.naming.TibjmsInitialContextFactory
2] ConnectionFactory = XATopicConnectionFactory
The EMS client version library is EMS version client library à 4.2.0
The message Bridge Thread Pool Size is à 12
When the weblogic is started, all the bridges comes up properly and are forwarding message to the target, however after some time (1 to 2 days) we observe some that some of the bridges are going down and we get see following error in the weblogic logs
####<May 26, 2010 12:00:56 AM GMT> <Warning> <Connector> <ngun015> <zlw1rdbs12-a> <ExecuteThread: '6' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-190032> << Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
####<May 26, 2010 12:00:56 AM GMT> <Info> <MessagingBridge> <ngun015> <zlw1rdbs12-a> <ExecuteThread: '6' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200042> <Bridge RefDataCompanyBridge failed to connect to the source destination and will try again in 60 seconds. (javax.resource.ResourceException: Failed to start the connection)>
Can you please help us resolve the above issue?
Thanks,
Mohanraj

There seems to be couple of known issues with WLS 8.1 and Tibco EMS.. Check with support whether your issue is related to any of the below:
Message bridge will stop responding and WLS has to be restarted to overcome this.
There is a known bug on WLS 8.1. Bug 8062571 is for the issue.
Should the connection be interrupted by a problem on the Tibco side, the messaging bridge never tries to reconnect. the problem can be that Tibco EMS is restarted for some reason or that the maximum number of messages that Tibco EMS can handle is reached.
Unpublished bug8066979 is available for WebLogic Server 8.1 SP6 and later
Unpublished bug8172940 is available for WebLogic Server 9.2 MP2 and later
Note you can get more info about bridge problems by following the below steps:
To debug the bridge you can enable debugging for the messaging bridge using either of the followings methods:
* Add the following lines to your WebLogic start script (before the weblogic.Server line):
-Dweblogic.debug.DebugMessagingBridgeStartup=true
-Dweblogic.debug.DebugMessagingBridgeRuntime=true
* Add the following statements to the ServerDebug entry in your configuration file (config.xml) for the server that the messaging bridge is running on:
DebugMessagingBridgeStartup="true"
DebugMessagingBridgeRuntime="true"
Once debugging is enabled for the messaging bridge, the debugging messages are sent to the server log by default. However, if you want them to appear in the Administration Console, add “DumpToConsole” to the statements show above. For example:
-Dweblogic.debug.DebugMessagingBridgeStartupDumpToConsole=true
Edited by: atheek1 on May 30, 2010 5:19 AM

Weblogic 6.1sp1 - Weblogic 6.1sp1 in different domain messaging bridge configuration

I'm trying to configure messaging bridge to send messages from WLS
          6.1sp1 to WLS 6.1sp1 in another domain and seems it doesn't work. I'm
          using following configuration, any idea?
          <MessagingBridge Name="BatchBridge"
          SourceDestination="BatchBridgeDestination" Started="true"
          TargetDestination="BatchBridgeSource" Targets="myserver"/>
          <BridgeDestination
          AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          Name="BatchBridgeSource"
          Properties="ConnectionURL=t3://localhost:7001;DestinationJNDIName=ngfs.batch.Queue;ConnectionFactoryJNDIName=jms.connection.BridgeConnectionFactoryXA"
          UserName="system" UserPassword="something"/>
          <BridgeDestination
          AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          Name="BatchBridgeDestination"
          Properties="ConnectionURL=t3://ngfsdev:8001;DestinationJNDIName=ngfs.batch.Test;ConnectionFactoryJNDIName=jms.connection.BridgeConnectionFactoryXA"
          UserName="system" UserPassword="something"/>


Are the two servers having the same name?
          Try not to use the same name for different WebLogic servers.
          Also It is not recommended that different JMS servers or
          different JMS stores use the same name, even if they
          are on different WebLogic servers.
          Try it.
          Dongbo
          Vyacheslav wrote:
          >
          > I tryed what you adviced to me and it finally started to work on one
          > server. When both ConnectionURL point to t3://localhost:7001 it is
          > working. That is a progress already.
          > But when I'm pointing it to remote server it gives me exception. What
          > coud be the reason?
          > Configuration now looks like following:
          >
          > <MessagingBridge Name="BatchBridge"
          > SourceDestination="BatchBridgeSource" Started="true"
          > TargetDestination="BatchBridgeDestination"
          > Targets="myserver"/>
          >
          > <BridgeDestination
          > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          > Name="BatchBridgeSource"
          > Properties="ConnectionURL=t3://localhost:7001;DestinationJNDI=ngfs.batch
          > .Queue;ConnectionFactoryJNDI=jms.connection.BridgeConnectionFactoryXA"
          > UserName="system" UserPassword="something"/>
          >
          > <BridgeDestination
          > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          > Name="BatchBridgeDestination"
          > Properties="ConnectionURL=t3://ngfsdev:8001;DestinationJNDI=ngfs.batch.Test;ConnectionFactoryJNDI=jms.connection.BridgeConnectionFactoryXA"
          > UserName="system" UserPassword="something"/>
          >
          > I don't understand why it cannot connect.
          >
          > I have created factory jms.connection.BridgeConnectionFactoryXA on
          > remote server.
          > I have created queue ngfs.batch.Test on remote server.
          > What is wrong?
          >
          > Server output:
          >
          > configured = jms.connection.BridgeConnectionFactoryXA ra's =
          > jms.connection.Brid
          > geConnectionFactoryXA
          > Lookup: cfJNDI = jms.connection.BridgeConnectionFactoryXA
          > Username = system password = <cut>
          > configured = jms.connection.BridgeConnectionFactoryXA ra's =
          > jms.connection.Brid
          > geConnectionFactoryXA
          > Lookup: cfJNDI = jms.connection.BridgeConnectionFactoryXA
          > Username = system password = <cut>
          > weblogic.jms.common.JMSException: Connection not found
          > at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManag
          > er.java:121)
          > at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.jav
          > a:503)
          > at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.ja
          > va:272)
          > at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:26
          > 1)
          > at weblogic.jms.client.JMSXAConnection.createXAQueueSession(JMSXAConnect
          > ion.java:67)
          > at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:2
          > 00)
          > at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnect
          > ion(JMSManagedConnectionFactory.java:200)
          > at weblogic.connector.common.internal.ConnectionPool.makeResources(Conne
          > ctionPool.java:808)
          > at weblogic.connector.common.internal.ConnectionPool.getConnection(Conne
          > ctionPool.java:1441)
          > at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
          > n(ConnectionPoolManager.java:154)
          > at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
          > ection(ConnectionManagerImpl.java:20)
          > at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMS
          > BaseConnectionFactory.java:157)
          > at weblogic.jms.bridge.internal.MessagingBridge.getConnections(Messaging
          > Bridge.java:543)
          > at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
          > java:677)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > <Jul 23, 2002 4:52:37 PM EDT> <Error> <Connector> <Error granting
          > connection req
          > uest.>
          >
          > "Dongbo Xiao" <[email protected]> wrote in message news:<[email protected]>...
          > > Having looked at your configuration again, I found an interesting thing,
          > > which may have caused the problem. Your bridge is configured to
          > > transfer messages from ngfs.batch.Test to ngfs.batch.Queue, while you
          > > expect to see it working in the reverse direction.
          > >
          > > Dongbo
          > >
          > > > > "Vyacheslav" <[email protected]> wrote in message
          > > > > news:[email protected]...
          > > > > > I'm trying to configure messaging bridge to send messages from WLS
          > > > > > 6.1sp1 to WLS 6.1sp1 in another domain and seems it doesn't work. I'm
          > > > > > using following configuration, any idea?
          > > > > >
          > > > > > <MessagingBridge Name="BatchBridge"
          > > > > > SourceDestination="BatchBridgeDestination" Started="true"
          > > > > > TargetDestination="BatchBridgeSource" Targets="myserver"/>
          > > > > >
          > > > > > <BridgeDestination
          > > > > > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          > > > > > Name="BatchBridgeSource"
          > > > > >
          > > > >
          > > Properties="ConnectionURL=t3://localhost:7001;DestinationJNDIName=ngfs.batch
          > > > >
          > > .Queue;ConnectionFactoryJNDIName=jms.connection.BridgeConnectionFactoryXA"
          > > > > > UserName="system" UserPassword="something"/>
          > > > > >
          > > > > > <BridgeDestination
          > > > > > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
          > > > > > Name="BatchBridgeDestination"
          > > > > >
          > > > >
          > > Properties="ConnectionURL=t3://ngfsdev:8001;DestinationJNDIName=ngfs.batch.T
          > > > > est;ConnectionFactoryJNDIName=jms.connection.BridgeConnectionFactoryXA"
          > > > > > UserName="system" UserPassword="something"/>

Different error messages for Weblogic-Apache bridge

We are running WLS 5.1 sp5 with Apache as Webserver.
I want to know how could I display more user freindly error messages when
weblogic is down and apache is working. Currently we get the default
Weblogic-Apache down page.
Thanks,
Rakesh

We used this but it did not work. Now the default does not show up but it is
not able to find the url that we specify which is reachable if I directly
use in the brower.
"Vinod Mehra" <[email protected]> wrote in message
news:[email protected]..
Checkout the plugin param "ErrorPage" in our documentation.
--Vinod.
Rakesh Gupta wrote:
We are running WLS 5.1 sp5 with Apache as Webserver.
I want to know how could I display more user freindly error messages
when
weblogic is down and apache is working. Currently we get the default
Weblogic-Apache down page.
Thanks,
Rakesh

Weblogic Messaging Bridge stops working

Hi, we are having a Weblogic Integration Domain (WLI 8.1). This domain has several JMS distibuted destinations and Messaging Bridges. In Production environment, the Messaging bridge stops then and there and lot of messages get piled up in the queues. The following exception is found in logs. Can someone help with the suggestion on this please .. It is quite urgent for us ..
####<Sep 26, 2011 11:34:34 AM EEST> <Warning> <MessagingBridge> <servername.com> <ccpeIntMServer1> <ExecuteThread: '4' for queue: '
weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-200026> <Bridge "MessagingBridge1" encountered some problems in one of its adapters or underl
ying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.common
.LostServerException: java.net.SocketException: Broken pipe.)>
####<Sep 26, 2011 11:34:34 AM EEST> <Info> <MessagingBridge> <servername.com> <ccpeIntMServer1> <ExecuteThread: '22' for queue: 'we
blogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200020> <Bridge "MessagingBridge1" is stopped.>
####<Sep 26, 2011 11:34:34 AM EEST> <Warning> <MessagingBridge> <servername.com> <ccpeIntMServer1> <ExecuteThread: '1' for queue: '
weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-200026> <Bridge "JMSMessagingBridge1" encountered some problems in one of its adapters or under
lying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.common.LostServerException: java.net.SocketException: Broken pipe.)>
####<Sep 26, 2011 11:34:34 AM EEST> <Info> <MessagingBridge> <servername.com> <ccpeIntMServer1> <ExecuteThread: '20' for queue: 'we
blogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200020> <Bridge "JMSMessagingBridge1" is stopped.>

This is a very generic description of your issue, I think you should open a support case to help you troubleshoot.

Weblogic Messaging Bridge Question

          I am using the Weblogic Messaging Bridge and I have a question regarding Transactions.
          I am using the bridge to integrate MQ Series with Weblogic JMS.
          If I want to send messages over the the bridge and have it wrapped in a transaction
          do I wrap my code where I send the message across on the Queue within a User Transaction
          or do I wrap it in a Global Transaction?


Anuj,
          In your situation, if I remember correctly, use a JTA transaction to post
          the message to WL queue. Make sure that the bridge is configured with XA
          connection factory to move the message to MQ. The bridge will start an
          internal transaction and synchronously move messages to MQ and then it's
          upto your adapter code to dequue the message from MQ within transaction.
          On the receiving side, the adapter would put the message in MQ
          (transationally if you prefer), the bridge would move the message to WL
          destination within a transaction (assuming it is configured correctly). You
          could then use a MDB with container transaction to dequeue the message and
          invoke your business logic.
          Feel free to send me an email if you have further questions. You can also
          contact Helen. I am on the road, so I would not have access to my emails
          until I get back to the hotel.
          Once you are ready to move to 7.0 we could come back and see what hop can we
          remove.
          Hope this helps.
          .raja
          "Anuj Mehta" <[email protected]> wrote in message
          news:[email protected]...
          >
          > I am using the Weblogic Messaging Bridge and I have a question regarding
          Transactions.
          >
          > I am using the bridge to integrate MQ Series with Weblogic JMS.
          > If I want to send messages over the the bridge and have it wrapped in a
          transaction
          > do I wrap my code where I send the message across on the Queue within a
          User Transaction
          > or do I wrap it in a Global Transaction?
          >
          >

How to Montior Messaging Bridge weblogic 10.1?

Similar Messages

Maybe you are looking for