Message Bridge error "Received message with no URI property"
I have created a message bridge between two weblogic JMS servers on different domains.
Message bridge has source and destinations.
I have tested each ques seperately with MDB deployed on each server.
When i am putting message on source que then i am getting this error "Received message with no URI property"
It would be grat help if some could tell me what might be going wrong.
Thanks
Akash
Hi,
This exception indicates a failure to establish a JNDI context for either the source or target destination host. Check if the the bridge's configured URLs for both are correct. I'm not 100% sure, but it is likely that no URL need be configured for destination's that are in the same cluster as the bridge.
For more information, I suggest looking at the Messaging Bridge FAQ, which contains some troubleshooting tips. You can find a link to it here:
http://dev2dev.bea.com/technologies/jms/index.jsp
Tom Barnes, BEA
Similar Messages
-
Message Bridge error:Connection Factory
Hi
I am trying to build a Message Bridge accross two domains which are using the same version of Weblogic Server(8.1).
I am running into this error..
<Warning> <Connector> <BEA-190032> << Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException of javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = , user name =) on createManagedConnection.>
Please could anybody help me with this.Hi,
This exception indicates a failure to establish a JNDI context for either the source or target destination host. Check if the the bridge's configured URLs for both are correct. I'm not 100% sure, but it is likely that no URL need be configured for destination's that are in the same cluster as the bridge.
For more information, I suggest looking at the Messaging Bridge FAQ, which contains some troubleshooting tips. You can find a link to it here:
http://dev2dev.bea.com/technologies/jms/index.jsp
Tom Barnes, BEA -
MQ 6 WLS 9.2 JMS Message Bridge Error
I tried to set up a JMS message bridge between MQ 9.2 and WLS 9.2 collocated on the same server following the BEA example:
1.Create local queue on MQ
2.Bind queue using JMSAdmin
3.Create JMS bridge betwen a source destination using JNDI name in #2 and a local WLS queue.
Here is the WLS config:
<messaging-bridge>
<name>MQ-WLSBridge</name>
<target>adminServer</target>
<source-destination>MQ-WLSSource</source-destination>
<target-destination>MQ-WLSTarget</target-destination>
<selector></selector>
<quality-of-service>Exactly-once</quality-of-service>
<qos-degradation-allowed>true</qos-degradation-allowed>
<durability-enabled>true</durability-enabled>
<idle-time-maximum>60</idle-time-maximum>
<async-enabled>true</async-enabled>
<started>true</started>
<preserve-msg-property>false</preserve-msg-property>
</messaging-bridge>
<jms-bridge-destination>
<name>MQ-WLSTarget</name>
<adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
<classpath></classpath>
<connection-factory-jndi-name>com.MetaSolv.Security.QueueConnectionFactory</connection-factory-jndi-name>
<connection-url>t3://localhost:7005</connection-url>
<destination-jndi-name>WLSMessageQueue</destination-jndi-name>
</jms-bridge-destination>
<jms-bridge-destination>
<name>MQ-WLSSource</name>
<adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
<classpath></classpath>
<connection-factory-jndi-name>QCF</connection-factory-jndi-name>
<initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
<connection-url>file:///usr/mqm/java/jndi</connection-url>
<destination-jndi-name>MQMessageQueus</destination-jndi-name>
</jms-bridge-destination>
I used a standalone JMS client and was able to connect to the MQ queue using the above JNDI name, factory so the MQ side was set up properly.
When I start up WLS, I saw that
<The messaging bridge "MQ-WLSBridge" has been successfully deployed.>
and the exception:
<MessagingBridge> <BEA-200042> <Bridge MQ-WLSBridge failed to connect to the source destination and will try again in 20 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: javax.resource.ResourceException: Failed to start the connection
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1458)
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1438)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:403)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:242)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1057)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:346)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:294)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:277)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:606)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:271)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMSBaseConnectionFactory.java:92)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:809)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1042)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
)>
There is no error in the MQ logs. What is the problem?
CSC S <> wrote:
> I tried to set up a JMS message bridge between MQ 9.2 and WLS 9.2
> collocated on the same server following the BEA example: 1.Create local
> queue on MQ 2.Bind queue using JMSAdmin
> 3.Create JMS bridge betwen a source destination using JNDI name in #2 and
> a local WLS queue.
>
> Here is the WLS config:
> <messaging-bridge>
> <name>MQ-WLSBridge</name>
> <target>adminServer</target>
> <source-destination>MQ-WLSSource</source-destination>
> <target-destination>MQ-WLSTarget</target-destination>
> <selector></selector>
> <quality-of-service>Exactly-once</quality-of-service>
> <qos-degradation-allowed>true</qos-degradation-allowed>
> <durability-enabled>true</durability-enabled>
> <idle-time-maximum>60</idle-time-maximum>
> <async-enabled>true</async-enabled>
> <started>true</started>
> <preserve-msg-property>false</preserve-msg-property>
> </messaging-bridge>
>
> <jms-bridge-destination>
> <name>MQ-WLSTarget</name>
>
<adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
> <classpath></classpath>
>
<connection-factory-jndi-name>com.MetaSolv.Security.QueueConnectionFactory</connection-factory-jndi-name>
> <connection-url>t3://localhost:7005</connection-url>
> <destination-jndi-name>WLSMessageQueue</destination-jndi-name>
> </jms-bridge-destination>
> <jms-bridge-destination>
> <name>MQ-WLSSource</name>
>
Hello,
First of all, your classpath doesn't seem to be correct. You need to add the
MQ jars in the bridge classpath. (DONT use the server classpath for
this!!!)
Secondly, enable debugging in Weblogic, which will give you some
information: -Dweblogic.Debug.DebugMessagingBridgeStartup=true -Dweblogic.Debug.DebugMessagingBridgeRuntime=true -Dweblogic.Debug.DebugMessagingBridgeRuntimeVerbose=true
IF you have more questions, pls reply also be mail.
Bart
Schelstraete Bart
[email protected]
http://www.schelstraete.org
http://www.linkedin.com/in/bschelst -
Hi,
I am getting this Warning for every 2 mins. i was using this for 4 yrs on HP-UX . few months back i moved this to Linux and working good. today i did reboot start getting this Warning
<Jan 12, 2010 6:29:53 PM GMT> <Warning> <MessagingBridge> <BEA-200026> <Bridge "TestInboundQueue" 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 javax.jms.IllegalStateException: MQJMS3033: QueueReceiver is closed.)>
Thanks
Subba
Edited by: Subba R Kancharla on Jan 12, 2010 4:33 PMHave you consulted the bridge troubleshooting guide in the bridge documentation?
Also check to see if there was a change to the MQ version and/or configuration...
Tom -
HI, I am new to this and trying to open this app but keep getting this message. Anyone help me define this and a fix if needed, thanks.
Try reinstalling the software.
-
PI 7.1 Error:- Receiver Adapter with File Content Conversion
Hi,
I am doing XML to Flat file scenario in PI 7.1.
I have done Recevier side below configuration:_
Recordset Structure - Contact,*
Contact.fieldNames Name,LastName
Contact.fieldFixedLengths 10,20
But still it is throwing error in Recevier Communication channel monitoring.
ERROR-
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
Do the needful.
Thanks,
Anshulyou never give the occurrence in the receiver recordset structure.
i.e it will never be,
a,*,b,*,c,1,d,1 etc but it would be just a,b,c,d
ex. /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion -
How to see "sent messages" mailbox within "received" messages mailbox into Mail app
I'm a brand new user of Ipad and when I'm using Mail I would like to be able to see all my mailboxes and my sent messages box and even the bin box within each others. I saw it on the Ipad of a friend, but on mine I've got a column called "all mailboxes" where I can see all my mailboxes and all my mail account and nothing more. if I click on one account then it offers me a new column with sent messages and bin. Can I change that? I havn't found how...
Thank you by advanceHi Decosensei,
Welcome to the Support Communities!
Congratulations on the purchase of your iPad!
In the Mail app on your iPad - you do have to click on the Account (ie. iCloud, Gmail, etc.) in order to see the Sent, Junk, Drafts and any subfolders you've created.
I've included the iPad User Guide and our main support page for the iPad to get you started.
manuals.info.apple.com/en_US/ipad_user_guide.pdf
Apple - Support - iPad
Enjoy!
- Judy -
Hi friends,
I've a strange problem. I've posted a problem on another newsgroup concerning remote lookup as you can see below.
I'm working on WLS8.1sp2. 2 clusters (front-end with webapps and back-end with ejbs with a firewall without nat between they). Message bridges deployed on back end.
When that problem during loockup(see below) occurs I noticed also this exception regarding message bridge:
####<Jun 6, 2005 6:26:38 PM CEST> <Warning> <MessagingBridge> for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-200026> <Bridge "Bridge1-SourceWLXQueueSend > TargetWLSQueueSend" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.common.LostServerException: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException.)>
####<Jun 6, 2005 6:26:38 PM CEST> <Error> <MessagingBridge> <ExecuteThread: '120' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <BEA1-009BCF7999A0A21B1158> <BEA-200015> <An error occurred in bridge "Bridge1-SourceWLXQueueSend > TargetWLSQueueSend" during the transfer of messages (javax.resource.ResourceException: Error receiving message).>
I'm working on weblogic server 81.sp2.
I've 2 clusters (front-end cluster with web apps and back-end cluster with ejbs) with 2 active server per cluster.
Randomically when I try to make a lookup on the back-end cluster with a servlet deployed in the front-end cluster I received the following error:
javax.naming.CommunicationException. Root exception is java.rmi.ConnectExceptio
n: Unable to get direct or routed connection to: '7425491688784079753S:cihpas04:
[7200,7200,-1,-1,7200,-1,-1,0,0]:cihpas03:7100,cihpas03:7300,cihpas03:7500,cihpa
s04:7200,cihpas04:7400,cihpas04:7600:cie:CIEServer2'
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.j
ava:108)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:244)
at weblogic.jndi.internal.ServerNamingNode_812_WLStub.lookup(Unknown Sou
rce)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:343)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:336)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at Cie.servlet.SSCE.CIE045_Ping_Servlet.service(CIE045_Ping_Servlet.java
:157)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Can you help me for both problems?tnx in advancegabriele.folchi,
did you ever resolved this issue ? -
Messaging Bridge with MQ using SSL
Hi everybody,
I'm using JMS messaging bridge to transfer messages from WLS 10.3.6 running on a Solaris machine to remote WebSphere MQ 7 running on an AIX machine. Weblogic reads the configuration of remote MQ from a text file, called .bindings, created using the MQ JMSAdmin tool. The file defines a connection factory with the IP address, port, queue and queue manager name and other important definitions of the remote MQ.
The thing is that the bridge starts pretty well and transfer messages normally, but I need to change the configuration to use SSL. To do it I just added the parameter SSLCIPHERSUITE(SSL_RSA_WITH_RC4_128_MD5) and thought it was enough to achieve the goal.
<May 12, 2014 3:05:45 PM BRT> <Debug> <MessagingBridgeRuntimeVerbose> <BEA-000000> <Exception:
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
Wondering the error could be relatedo to an SSL exception, I enabled the SSL debugging (-Dssl.debug=true) to the managed server, but there were no evidences of an SSL handshake of Weblogic and MQ, so there is no SSL communication between the peers.
Does anybody know if this kind of communication is feasible? What may I be missing here?
Tks!Hi everybody,
I'm using JMS messaging bridge to transfer messages from WLS 10.3.6 running on a Solaris machine to remote WebSphere MQ 7 running on an AIX machine. Weblogic reads the configuration of remote MQ from a text file, called .bindings, created using the MQ JMSAdmin tool. The file defines a connection factory with the IP address, port, queue and queue manager name and other important definitions of the remote MQ.
The thing is that the bridge starts pretty well and transfer messages normally, but I need to change the configuration to use SSL. To do it I just added the parameter SSLCIPHERSUITE(SSL_RSA_WITH_RC4_128_MD5) and thought it was enough to achieve the goal.
<May 12, 2014 3:05:45 PM BRT> <Debug> <MessagingBridgeRuntimeVerbose> <BEA-000000> <Exception:
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
Wondering the error could be relatedo to an SSL exception, I enabled the SSL debugging (-Dssl.debug=true) to the managed server, but there were no evidences of an SSL handshake of Weblogic and MQ, so there is no SSL communication between the peers.
Does anybody know if this kind of communication is feasible? What may I be missing here?
Tks! -
Message Bridge Destination points to old IP, after failover with HA pair
Hi
Weblogic Version in use is 7.0sp7
We have this Messaging Bridge configured, between two instances of Weblogic server (Each weblogic server exists on Different Weblogic domains)
Both the weblogic servers run on the same machine.
So we have configured the message bridge destination with localhost, instead of an IP or DNS name in it.. viz.
t3://localhost:8001
t3://localhost:8020 respectively
where 8001 and 8020 are the listen ports of the respective weblogic servers.
This machine is a HA pair, controlled by vcs cluster server.
Which means when we failover from one node to another of the HA pair, the transition(which also involves the IP change from node A to node B) should be ideally transparent to weblogic.
But when it comes to these messaging bridge destinations
The Messaging bridge resolves the localhost in the Message Bridge destination to the old node IP, after the failover is done using vcs cluster server.
To me it looks like weblogic is caching the IP details somewhere and probably reusing it, unaware of the fact that the IP of the machine has changed after the failover.
I tried configuring the message bridge destination with addresses like t3://<DNSname>:8001 and 8020 respectively. But stiil it tries to connect to the IP of the old node only.
I did come across this patch in Weblogic 7.0 sp5, which is pretty close to the issue that i am encountering..
CR126201 In a multiple-server domain, if a Managed Server was rebooted to use a different address or port
number, the JTA subsystem failed to update the address information. This would cause the
following exception when the changed server was rebooted:
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: t3://ip_address:port_number:
Destination unreachable;
nested exception is: java.net.ConnectException: Connection
refused; No available router to destination
Would really appreciate if someone can help with this issue.
Regards
AzadI'm not quite sure what the correct solution might be, but a possible work-around might be to hard-code the two addresses directly into the bridge URL. For example: t3://host:7010,host:7020. WebLogic will try each address in turn, starting from the first one until one succeeds or all fail.
Another solution might be to configure an "external listen address" on each server. This is the address that "reconnectable" external clients (such as EJBs or a bridge ) will use for reconnect in place of the server's actual listen address.
Tom -
ECATT with WDA Error logon message
When I record a WDA application for eCatt I always get an error when I do the playback. I run playback in Foreground and visible.
Recording works fine, no indication of a error.
The error message says "Error logon message".
We are on WebAS 7 ABAP SPS12Hello Frank,
my suggestion is not use eCatt for WDA until SAP will have fully released this functionality. There
are a number of limitations, which make it impossible to record any real world application. There's
a note describing the current limitations.
Best regards,
Thomas -
Message Bridge between WLS 6.1 sp3 and MQSeries 5.2
Hi,
I'm really struggling with getting the Message Bridge working with Weblogic 6.1
sp3 and MQSeries 5.2. Currently I have both installed on the same Windows 2000
machine. First I'll pose some questions that I have, then I discuss the error
I'm getting. Here are my questions:
1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml. Within the
ra.xml deployment descriptor there are config-properties for ConnectionURL, InitialContextFactory,
ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue is the source
jms destination bridge and my weblogic queue is the target jms destination bridge,
what values do I set for the listed config-properties? I can't seem to find any
documentation on what these values should be. Am I missing something? Do these
values even have to be set?
2. When I go to install a Weblogic instance to a different physical machine what
has to be installed in terms of MQSeries? So I'll have MQSeries on physical machineA
and Weblogic on a different physical machineB. I want machineA to forward all
messages placed on a MQSeries Queue to forward them to machineB where the weblogic
Queue resides. Does machineB also have to contain an MQSeries installation?
Or can I just grab the necessary libraries and jar files and place them on the
Weblogic machineB so they can be included?
3. Is it correct that if I distribute Weblogic onto one physical server and MQSeries
onto a different physical server that I cannot use Exactly-once quality of service?
Other notes:
1. I have the following patches installed for Weblogic 6.1 sp3:
CR081404_610sp3.jar
CR081511_61sp3.jar
2. Here is the commands I used to create my ConnectionFactory and Queue within
MQSeries:
def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
def q(MQTestQueue) qmanager(QM_jeff) queue(default)
Okay...here is my error:
<21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred in bridge
"Messaging Bridge" during transferring messages (java.lang.Exception: java.lang.
reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
javax.resource.ResourceException: Error creating consumer or receiving message
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
at $Proxy82.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
Has anyone see this error before? Here is part of my ra.xml file....I just put
these entries in to see what happens:
<config-property>
<config-property-name>ConnectionURL</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
</config-property>
<config-property>
<config-property-name>InitialContextFactory</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
</config-property>
<config-property>
<config-property-name>ConnectionFactoryJNDI</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>MQTestConnectionFactory</config-property-value>
</config-property>
<config-property>
<config-property-name>DestinationJNDI</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>MQTestQueue</config-property-value>
</config-property>
<config-property>
<config-property-name>DestinationType</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<config-property-name>AdapterType</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>XATransaction</config-property-value>
</config-property>
Here is a snip of my config.xml:
<MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
Name="Messaging Bridge" QualityOfService="Atmost-once"
SourceDestination="Source JMS Bridge Destination"
TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
<JMSBridgeDestination
AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
ConnectionFactoryJNDIName="MQTestConnectionFactory"
ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
Name="Source JMS Bridge Destination"/>
<JMSBridgeDestination
AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
ConnectionURL="t3://localhost:7001"
DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
InitialContextFactory="weblogic.jndi.WLInitialContextFactory" Name="Target
JMS Bridge Destination"/>
Any help would be greatly appreciated. Thank you in advance for your help.
Sincerely,
Jeff
I tried your suggestion and it worked!! The only thing is, it
makes the deployment of the resource adapter a little more
complicated. Now my customers are going to have to edit their
config.xml, instead of just dropping in the appropriate rar into
the applications directory. But one nice side affect of placing
the rar's in a different directory is it makes the Message
Bridge a little more stable. I was finding it to be very
unstable. One time I would startup my Application Server and
everything was fine, then I would shutdown. The next time I
started it up, I would get exceptions. I have yet to see that
behavior with this new configuration.
Thanks again for all of your help, it is greatly appreciated!!
Jeff
Dongbo Xiao <[email protected]> wrote:
>Looks like that somehow you have the adapter deployed
>multiple times, may not be intended. The cause is that
>everything in the application directory will be automatically
>deployed and all of them are added to the config.xml. During
>the next boot, those appear in the config.xml will be deployed and
>everything in the application directory too. As a result, the adapters
>are deployed twice. The complain about runtime mbean not found may
>mean the one that is overridden by the new one.
>
>The work around is not to put your adapters in the application
>directory, instead, put them in a different directory and point to
>the directory in your config.xml.
>
>Dongbo
>Jeff wrote:
>>
>> One more thing...
>> I noticed that the exception specified that it couldn't find
>> mydomain:Location=myserver,Name=jms-xa-
>> adp_Pool_1,ServerRuntime=myserver,Type=ConnectorConnectionPoolRun
>> time MBean, but what's interesting that if I run the following
>> java weblogic.Admin GET -type ConnectorConnectionPoolRuntime -
>> property ActiveConnectionsCurrentCount -url
>> http://localhost:7001 -username xxxx -password xxxx I get the
>> following output:
>>
>> {MBeanName="mydomain:Location=myserver,Name=jms-xa-
>> adp_Pool_3,ServerRuntime=myse
>> rver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCurren
>> tCount=0}}
>> {MBeanName="mydomain:Location=myserver,Name=jms-notran-
>> adp_Pool_2,ServerRuntime=
>> myserver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCu
>> rrentCount=0}}
>>
>> So from that...it looks like the MBean is there. Any ideas why it
>is not being
>> found?
>>
>> Thanks,
>>
>> Jeff
>>
>> "Jeff" <[email protected]> wrote:
>> >
>> >
>> >
>> >Thank you very much!!
>> >
>> >I tried your suggestions and created a general Queue Connection Factory
>> >within
>> >MQSeries. Then I setup my MQSeries JMS Bridge Destination to use
>the
>> >jms-notrans-adp.rar
>> >resource adapter. With this configuration, I can send messages to
>MQSeries
>> >and
>> >they get forwarded to Weblogic.
>> >
>> >But, if I create a XAQueueConnectionFactory within MQSeries I cannot
>> >get the bridge
>> >working at all. I realize that MQSeries has a bug with Transactions
>> >and remote
>> >servers, but I have MQSeries and Weblogic running on the same machine.
>> > I thought
>> >I could setup an XAConnectionFactory in MQSeries, set the MQSeries
>JMS
>> >Bridge
>> >Destination to use the jms-xa-adp.rar and specify Exactly-once QOS
>and
>> >it should
>> >work? I tried it and it didn't work. ( see attachment for weblogic.log
>> >showing
>> >exception ).
>> >
>> >Here is my config.xml:
>> > <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
>> > Name="Request Messaging Bridge" QOSDegradationAllowed="true"
>> > QualityOfService="Exactly-once"
>> > SourceDestination="Source JMS Bridge Destination"
>> > TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
>> > <JMSBridgeDestination
>> > ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
>> > ConnectionURL="t3://localhost:7001"
>> > DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
>Name="Target
>> >JMS Bridge Destination"/>
>> > <JMSBridgeDestination
>> > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
>> > ConnectionFactoryJNDIName="MQTestConnectionFactory"
>> > ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
>> > DestinationJNDIName="MQTestQueue"
>> > InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
>> >Name="Source
>> >JMS Bridge Destination"/>
>> >
>> >Again, thank you very much for your response. It helped me a great
>deal.
>> > Any
>> >thoughts on the above problem please foward them along.
>> >
>> >Oh...and to answer the question posed to me, yes the CR081511_61sp3.jar
>> >file is
>> >dated 8/13/2002
>> >
>> >
>> >Sincerely,
>> >
>> >Jeff
>> >
>> >Dongbo Xiao <[email protected]> wrote:
>> >>Please see my comments inline.
>> >>
>> >>
>> >>Jeff wrote:
>> >>>
>> >>> Hi,
>> >>> I'm really struggling with getting the Message Bridge working with
>> >>Weblogic 6.1
>> >>> sp3 and MQSeries 5.2. Currently I have both installed on the same
>> >>Windows 2000
>> >>> machine. First I'll pose some questions that I have, then I discuss
>> >>the error
>> >>> I'm getting. Here are my questions:
>> >>>
>> >>> 1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml.
>> >> Within the
>> >>> ra.xml deployment descriptor there are config-properties for ConnectionURL,
>> >>InitialContextFactory,
>> >>> ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue
>> >is
>> >>the source
>> >>> jms destination bridge and my weblogic queue is the target jms
>destination
>> >>bridge,
>> >>> what values do I set for the listed config-properties? I can't
>seem
>> >>to find any
>> >>> documentation on what these values should be. Am I missing something?
>> >> Do these
>> >>> values even have to be set?
>> >>>
>> >>
>> >>You DON'T have to do anything to the adapter deployment descriptor
>> >>files.
>> >>The values given there for the listed config-properties are just
>default
>> >>values.
>> >>The values configured in JMSBridgeDestination instances are the values
>> >>used to
>> >>override the default values in the dd file.
>> >>
>> >>> 2. When I go to install a Weblogic instance to a different physical
>> >>machine what
>> >>> has to be installed in terms of MQSeries? So I'll have MQSeries
>on
>> >>physical machineA
>> >>> and Weblogic on a different physical machineB. I want machineA
>to
>> >>forward all
>> >>> messages placed on a MQSeries Queue to forward them to machineB
>where
>> >>the weblogic
>> >>> Queue resides. Does machineB also have to contain an MQSeries
>installation?
>> >>> Or can I just grab the necessary libraries and jar files and place
>> >>them on the
>> >>> Weblogic machineB so they can be included?
>> >>>
>> >>
>> >>You don't have to install MQSeries on the machine that the WebLogic
>> >>server is running. You need the necessary libraries and jar files
>> >>though.
>> >>
>> >>> 3. Is it correct that if I distribute Weblogic onto one physical
>server
>> >>and MQSeries
>> >>> onto a different physical server that I cannot use Exactly-once
>quality
>> >>of service?
>> >>>
>> >>
>> >>That is correct and it is a MQSeries transaction limitation.
>> >>
>> >>> Other notes:
>> >>> 1. I have the following patches installed for Weblogic 6.1 sp3:
>> >>> CR081404_610sp3.jar
>> >>> CR081511_61sp3.jar
>> >>>
>> >>
>> >>What version of CR081511_61sp3.jar you have? You need the one dated
>> >on
>> >>8/13/2002.
>> >>
>> >>> 2. Here is the commands I used to create my ConnectionFactory
>and
>> >>Queue within
>> >>> MQSeries:
>> >>> def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
>> >>> def q(MQTestQueue) qmanager(QM_jeff) queue(default)
>> >>>
>> >>
>> >>The only possible error I see here is that you create a xaqcf while
>> >your
>> >>bridge
>> >>is configured to have "Atmost-once" QOS. The bridge adapter will
>create
>> >>XASession
>> >>if the connection factory is xa because it knows nothing about QOS
>of
>> >>the bridge.
>> >>As I said, there is a limitation in MQSeries transactions, which
>prevent
>> >>the
>> >>transaction to happen between remote servers. Although the bridge
>does
>> >>not
>> >>start the the transaction in your case, but MQSeries xa connection
>> >>factory may
>> >>throw error when it detects the other side is remote. Having said
>that,
>> >>I am not
>> >>completely sure this is the problem caused the bridge to fail. I
>suggest
>> >>you use
>> >>a non-xa connection factory on the MQSeries side and see if the problem
>> >>goes away.
>> >>
>> >>> Okay...here is my error:
>> >>>
>> >>> <21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred
>> >>in bridge
>> >>> "Messaging Bridge" during transferring messages (java.lang.Exception:
>> >>java.lang.
>> >>> reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
>> >>> javax.resource.ResourceException: Error creating consumer or receiving
>> >>message
>> >>> at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
>> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
>> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
>> >>> at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
>> >>> at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
>> >>> at java.lang.reflect.Method.invoke(Native Method)
>> >>> at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
>> >>> at $Proxy82.receive(Unknown Source)
>> >>> at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
>> >>> at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
>> >>> at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
>> >>>
>> >>
>> >>The latest patch CR081511_61sp3.jar (dated on 8/13/2002) will expose
>> >>more error
>> >>information.
>> >>
>> >>> Has anyone see this error before? Here is part of my ra.xml file....I
>> >>just put
>> >>> these entries in to see what happens:
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>ConnectionURL</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
>> >>> </config-property>
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>InitialContextFactory</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
>> >>> </config-property>
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>ConnectionFactoryJNDI</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property-value>MQTestConnectionFactory</config-property-value>
>> >>> </config-property>
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>DestinationJNDI</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property-value>MQTestQueue</config-property-value>
>> >>> </config-property>
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>DestinationType</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property-value></config-property-value>
>> >>> </config-property>
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>AdapterType</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property-value>XATransaction</config-property-value>
>> >>> </config-property>
>> >>>
>> >>
>> >>As I said earlier, you are not supposed to change the adapter dd
>file.
>> >>
>> >>
>> >>> Here is a snip of my config.xml:
>> >>>
>> >>> <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
>> >>> Name="Messaging Bridge" QualityOfService="Atmost-once"
>> >>> SourceDestination="Source JMS Bridge Destination"
>> >>> TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
>> >>> <JMSBridgeDestination
>> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
>> >>> ConnectionFactoryJNDIName="MQTestConnectionFactory"
>> >>> ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
>> >>> DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
>> >>> Name="Source JMS Bridge Destination"/>
>> >>>
>> >>> <JMSBridgeDestination
>> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
>> >>> ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
>> >>> ConnectionURL="t3://localhost:7001"
>> >>> DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
>> >>> InitialContextFactory="weblogic.jndi.WLInitialContextFactory"
>Name="Target
>> >>> JMS Bridge Destination"/>
>> >>>
>> >>
>> >>Your configuration of the bridge and bridge destinations look fine.
>> >
>> >>The last thing is that you have to put MQSeries stuff in your CLASSPATH
>> >>and PATH for starting the WebLogic server that the bridge is running
>> >>on.
>> >>
>> >>You can also turn on debug for more information.
>> >>-Dweblogic.Debug.DebugMessagingBridgeStartup=true
>> >>-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
>> >>
>> >>
>> >>Thanks,
>> >>Dongbo
>> >
-
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,
MohanrajThere seems to be couple of known issues with WLS 8.1 and Tibco EMS.. Check with support whether your issue is related to any of the below:
Message bridge will stop responding and WLS has to be restarted to overcome this.
There is a known bug on WLS 8.1. Bug 8062571 is for the issue.
Should the connection be interrupted by a problem on the Tibco side, the messaging bridge never tries to reconnect. the problem can be that Tibco EMS is restarted for some reason or that the maximum number of messages that Tibco EMS can handle is reached.
Unpublished bug8066979 is available for WebLogic Server 8.1 SP6 and later
Unpublished bug8172940 is available for WebLogic Server 9.2 MP2 and later
Note you can get more info about bridge problems by following the below steps:
To debug the bridge you can enable debugging for the messaging bridge using either of the followings methods:
* Add the following lines to your WebLogic start script (before the weblogic.Server line):
-Dweblogic.debug.DebugMessagingBridgeStartup=true
-Dweblogic.debug.DebugMessagingBridgeRuntime=true
* Add the following statements to the ServerDebug entry in your configuration file (config.xml) for the server that the messaging bridge is running on:
DebugMessagingBridgeStartup="true"
DebugMessagingBridgeRuntime="true"
Once debugging is enabled for the messaging bridge, the debugging messages are sent to the server log by default. However, if you want them to appear in the Administration Console, add “DumpToConsole” to the statements show above. For example:
-Dweblogic.debug.DebugMessagingBridgeStartupDumpToConsole=true
Edited by: atheek1 on May 30, 2010 5:19 AM -
Connecting 2 WLS 7 servers via the Messaging Bridge
Hi,
I am trying to use the messaging bridge to post messages received on a
source JMS queue running in one WLS instance to a destination queue running
on another target WLS instance. I have followed the instructions in the
admin guide and performed the following:
- defined in the source WLS instance 2 JMS bridge destinations - one for the
source queue and one for the target queue
- defined the bridge between the 2 destination, using the jms-xa-adp.rar
- deployed the jmx-xa-adp.rar adapter to the source WLS instance
- enabled the XA connection factory (had to define a new connection factory
to do this)
- made sure that both WLS instances have the system user configured with the
same password
When the source WLS instance starts up, the following is logged to the
console:
weblogic.jms.common.JMSException: Connection not found
at
weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java
:134)
at
weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:592)
at
weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:275)
at
weblogic.jms.client.JMSConnection.createSession(JMSConnection.java:368)
at
weblogic.jms.client.JMSXAConnection.createXAQueueSession(JMSXAConnection.jav
a:75)
at
weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:
257)
at
weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:215)
at
weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMS
ManagedConnectionFactory.java:1
at
weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPo
ol.java:1002)
at
weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPo
ol.java:1777)
at
weblogic.connector.common.internal.ConnectionPoolManager.getConnection(Conne
ctionPoolManager.java:190)
at
weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(
ConnectionManagerImpl.java:25)
at
weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseCon
nectionFactory.java:126)
at
weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.
java:753)
at
weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:91
9)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
and any messages sent to the source queue just sit there.
What might I be missing? Am I correct that the configuration of the bridge
and destinations takes place at the source WLS instance (as this is posting
the messages to the target WLS) - the documentation seems to me a bit
ambiguous in this regard.
Thanks,
Stanley.
I am afraid that you'll have to enable security interoperability for
the bridge to work across two domains. Making the password for
system user is not enough. You have to disable generated credential
for both domains. For details, please look at the following link:
http://edocs.bea.com/wls/docs70/adminguide/msgbridge.html#1078380
Please also note that this requirement has been removed in 8.1 release and
7.0SP3.
Thanks
Dongbo
Stanley Beamish wrote:
> "Dongbo Xiao" <[email protected]> wrote in message
> news:[email protected]...
> > I suspect that the two WebLogic servers have the same name.
> > There are some naming restrictions in the WLS configuration.
> > Please take a look at the following link.
> > http://e-docs.bea.com/wls/docs70/adminguide/msgbridge.html#1076982
> >
> > Dongbo
>
> OK, I've changed the name of one of the servers and I can get further. But
> now I get the following exception on the server that hosts the bridge,
> relating to permissions. Both servers use the same system password.
>
> Thanks,
> SB
>
> java.lang.SecurityException: Invalid Subject: principals=[system,
> Administrators, Operators, Monitors, Deployers]
> at
> weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager
> .java:993)
> at
> weblogic.security.service.RoleManager.getRoles(RoleManager.java:277)
> at
> weblogic.security.service.AuthorizationManager.isAccessAllowed(Authorization
> Manager.java:589)
> at weblogic.jms.JMSService.checkPermission(JMSService.java:1064)
> at weblogic.jms.JMSService.checkRecvPermission(JMSService.java:1076)
> at
> weblogic.jms.frontend.FESession.consumerCreate(FESession.java:944)
> at weblogic.jms.frontend.FESession.invoke(FESession.java:2252)
> at
> weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:602)
> at
> weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:275)
> at
> weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:1592)
> at
> weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:1452)
> at
> weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:1302)
> at
> weblogic.jms.adapter.JMSBaseConnection.setMessageListenerInternal(JMSBaseCon
> nection.java:931)
> at
> weblogic.jms.adapter.JMSBaseConnection.setMessageListener(JMSBaseConnection.
> java:885)
> at
> weblogic.jms.adapter.JMSConnectionHandle.setMessageListener(JMSConnectionHan
> dle.java:121)
> at java.lang.reflect.Method.invoke(Native Method)
> at
> weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrappe
> r.java:101)
> at $Proxy103.setMessageListener(Unknown Source)
> at
> weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge
> .java:862)
> at
> weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:94
> 2)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
>
> >
> > Stanley Beamish wrote:
> >
> > > Hi,
> > >
> > > I am trying to use the messaging bridge to post messages received on a
> > > source JMS queue running in one WLS instance to a destination queue
> running
> > > on another target WLS instance. I have followed the instructions in the
> > > admin guide and performed the following:
> > >
> > > - defined in the source WLS instance 2 JMS bridge destinations - one for
> the
> > > source queue and one for the target queue
> > > - defined the bridge between the 2 destination, using the jms-xa-adp.rar
> > > - deployed the jmx-xa-adp.rar adapter to the source WLS instance
> > > - enabled the XA connection factory (had to define a new connection
> factory
> > > to do this)
> > > - made sure that both WLS instances have the system user configured with
> the
> > > same password
> > >
> > > When the source WLS instance starts up, the following is logged to the
> > > console:
> > >
> > > weblogic.jms.common.JMSException: Connection not found
> > > at
> > >
> weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java
> > > :134)
> > > at
> > >
> weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:592)
> > > at
> > >
> weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:275)
> > > at
> > > weblogic.jms.client.JMSConnection.createSession(JMSConnection.java:368)
> > > at
> > >
> weblogic.jms.client.JMSXAConnection.createXAQueueSession(JMSXAConnection.jav
> > > a:75)
> > > at
> > >
> weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:
> > > 257)
> > > at
> > > weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:215)
> > > at
> > >
> weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMS
> > > ManagedConnectionFactory.java:1
> > > )
> > > at
> > >
> weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPo
> > > ol.java:1002)
> > > at
> > >
> weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPo
> > > ol.java:1777)
> > > at
> > >
> weblogic.connector.common.internal.ConnectionPoolManager.getConnection(Conne
> > > ctionPoolManager.java:190)
> > > at
> > >
> weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(
> > > ConnectionManagerImpl.java:25)
> > > at
> > >
> weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseCon
> > > nectionFactory.java:126)
> > > at
> > >
> weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.
> > > java:753)
> > > at
> > >
> weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:91
> > > 9)
> > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
> > >
> > > and any messages sent to the source queue just sit there.
> > >
> > > What might I be missing? Am I correct that the configuration of the
> bridge
> > > and destinations takes place at the source WLS instance (as this is
> posting
> > > the messages to the target WLS) - the documentation seems to me a bit
> > > ambiguous in this regard.
> > >
> > > Thanks,
> > > Stanley.
> >
[att1.html]
Maybe you are looking for
-
Hi, I understand that muse preview is a composite of various browsers, phones etc...is this correct and if so why would you do that if the result is going to just look hotchpotch - apologies if I'm wrong here? All I have at this stage is a simple sli
-
How do i get my macbook to stay connected to my wireless network . i have to constantly rejoin it when i go online. Wayne
-
Skipped Numbering for Materials
Hi, We currently have a situation wherein we noticed that material numbers are inconsistently numbered. Instead of sequential all throughout, some numbers are skipped. For example, we would have materials 300010, 300011, 300012, 300020, 300021 (see t
-
I have problem with wifi adapter in z97 mpower max ac the problem is the disappearance wifi from my computer I can't find wireless in network and sharing center and in device manage i tried network troubleshooting and he said plug an ethernet cable i
-
Passing dynamic cmdline arguments to app deployed by JWS offline
Hi, i want to deploy my java application through JWS for the benefit of autoupdating. my app, when started, needs a cmdline argument that the user supplies. It's a filename, so it can be anything. I cannot use the <argument> tag in JNLP file to speci