Messaging Bridge on WLS 6.1 sp3
Hi
I'm having a problem setting up a messaging bridge on WLS6.1 (sp3)
The source destination (MQseries -> bridge) uses com.ibm.mq.jms.MQXAQueueConnectionFactory.
I use a startup class to create JNDI entries for the MQ queue and qmanager.
The target (bridge -> JMS queue) uses weblogic.jms.client.JMSXAConnectionFactory.
Both source and target destinations use the eis.jms.WLSConnectionFactoryJNDIXA
adapter JNDI name.
When I start the server, I get these 2 messages in the log:
Warning> <Connector> << Weblogic Messaging Bridge Adapter (Local TX) > Connection
Pool has been initialized with no connections.>
<Info> <Connector> << Weblogic Messaging Bridge Adapter (Local TX) > Connection
Pool initial
ization has completed successfully.>
followed by :
<Info> <MessagingBridge> <Bridge "MQJMSMessaging Bridge" suceesfully found the
two adapters configured for it.>
And when I try to monitor the messaging bridge runtime from the console, it shows
"Found two adapters and about to make connections" but nothing happens after that.
Any message sent to the MQ queue is not picked up.
I'm not sure if I'm doing something wrong.
Any help would be greatly appreciated.
Vic
Hi Victor,
First of all, are you running any batches? You need to get the latest bridge
batch for 6.1sp3 from BEA Customer Support.
Second, I noticed that you are using XA. I don't know which MQ release you
are using, but there was a limitaion in the previous MQSeries releases that the queue
manager has to be collcated with the client (which is the bridg ein our case) in order for XA
to work. You may want to check that out.
If the problem persists after you take care of these two issues,
you could turn on the bridge debug to see what is wrong.
You probably need to take a look at the bridge FAQ (where you can
find out how to turn on the debug) at
http://e-docs.bea.com/wls/docs61/faq/msgbridge.html
Another useful doc is the white paper on dev2dev for using foreign JMS in WLS.
http://dev2dev.bea.com/resourcelibrary/whitepapers/jmsproviders.jsp
Thanks,
Dongbo
Victor wrote:
> Hi
> I'm having a problem setting up a messaging bridge on WLS6.1 (sp3)
>
> The source destination (MQseries -> bridge) uses com.ibm.mq.jms.MQXAQueueConnectionFactory.
> I use a startup class to create JNDI entries for the MQ queue and qmanager.
>
> The target (bridge -> JMS queue) uses weblogic.jms.client.JMSXAConnectionFactory.
>
> Both source and target destinations use the eis.jms.WLSConnectionFactoryJNDIXA
> adapter JNDI name.
>
> When I start the server, I get these 2 messages in the log:
>
> Warning> <Connector> << Weblogic Messaging Bridge Adapter (Local TX) > Connection
> Pool has been initialized with no connections.>
> <Info> <Connector> << Weblogic Messaging Bridge Adapter (Local TX) > Connection
> Pool initial
> ization has completed successfully.>
>
> followed by :
> <Info> <MessagingBridge> <Bridge "MQJMSMessaging Bridge" suceesfully found the
> two adapters configured for it.>
>
> And when I try to monitor the messaging bridge runtime from the console, it shows
> "Found two adapters and about to make connections" but nothing happens after that.
>
> Any message sent to the MQ queue is not picked up.
>
> I'm not sure if I'm doing something wrong.
> Any help would be greatly appreciated.
>
> Vic
Similar Messages
-
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
>> >
-
Hi there,
i try to install wls61 sp3 for evaluating the messaging bridge and i could not find
the connectors (jms-xa-adp.rar, jms-notran-adp.rar, jms-notan-adp51.jar)
the documentation says they sould be in WL_HOME\server\lib, but there are not there
Where can i find them ?
Thanks
Bye
Sven
1) Ok, i took theese files, but to deploy a connector to a managed server, i have
to but the jmsadapte.jar-file from the *.rar-file to the classpath of the managed
server
2) Starting a managed server with this configuration i get the following error:
<Jul 11, 2002 4:38:51 PM CEST> <Info> <Connector> <Unable to determine Resource Principal
for Container Managed Security Context.>
<Jul 11, 2002 4:38:52 PM CEST> <Warning> <Connector> << Weblogic Messaging Bridge
Adapter (XA) > ResourceAllocationException of javax.resource.ResourceException: ConnectionFactory:
jms.connection.BridgeConnectionFactoryXA not found on createManagedConnection.>
<Jul 11, 2002 4:38:52 PM CEST> <Error> <Connector> << Weblogic Messaging Bridge Adapter
(XA) > Error making initial connections for pool. Reason: CreateManagedConnection
Error: ConnectionFactory: jms.connection.BridgeConnectionFactoryXA not found>
<Jul 11, 2002 4:38:52 PM CEST> <Warning> <Connector> << Weblogic Messaging Bridge
Adapter (XA) > Connection Pool has been initialized with no connections.>
So what am i doing wrong ??
Thanks
Bye
Sven
"Dongbo Xiao" <[email protected]> wrote:
>After all, the adapters for the Messaging Bridge are missing
>in the 6.1SP3 package. There is a temporary patch for this on
>the way. Meanwhile, you can download the adapters from
>ftp://edownload:[email protected]/pub/downloads/MessagingBridge61.zip
>
>Alternatively you can copy the adapters from WL_HOME\server\lib
>in the 7.0 package into 6.1SP3 installation WL_HOME\lib. If one
>side of your bridge is WebLogic Server 5.x, you need
>jms51-interop.jar file as well, which is in the same directory as the
>adapters.
>
>Dongbo
>
>"Sven Roesner" <[email protected]> wrote in message
>news:[email protected]...
>>
>> Hi there,
>> i try to install wls61 sp3 for evaluating the messaging bridge and i could
>not find
>> the connectors (jms-xa-adp.rar, jms-notran-adp.rar, jms-notan-adp51.jar)
>> the documentation says they sould be in WL_HOME\server\lib, but there
>are
>not there
>> ?!
>> Where can i find them ?
>> Thanks
>> Bye
>> Sven
>
>
-
Using Messaging Bridge with Distributed Destinations
I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
* WLS Server1:
* JMS Server1:
* inbound queue
* outbound queue
* JMS Server2:
* inbound queue
* outbound queue
* WLS Server 2:
* JMS Server3:
* inbound queue
* outbound queue
A distributed destination is configured for the inbound and outbound queues.
Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
Any suggestions?
Hi Rob,
Consumers on distributed destinations are always pinned
to a single physical destination on creation. Only
producers can round-robin each message. When a
distributed destination is used as a source destination,
you will need to configure a bridge per distributed
destination. Alternatively, you can enable
forwarding between the physical queues, which automatically
forwards messages from physical queues with
no consumers to physical queues that have consumers
(but the extra hop impacts performance). For more information,
consult the JMS documentation.
Tom
Rob McArthur wrote:
> I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
> * WLS Server1:
> * JMS Server1:
> * inbound queue
> * outbound queue
> * JMS Server2:
> * inbound queue
> * outbound queue
> * WLS Server 2:
> * JMS Server3:
> * inbound queue
> * outbound queue
>
> A distributed destination is configured for the inbound and outbound queues.
>
> Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
>
> Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
>
> Any suggestions?
>
>
-
Message Bridge - from Topic to Queue
Hi all,
Can I set up a message bridge in Weblogic 8.1 sp3 to "redirect" message from a topic to a queue? i.e. The source is set to Topic while the target is to queue consumed by a MDB located in the same instance as the queue.
I tried to configure but I couldn't get any subscriber to subscribe the said topic. Would it be a configuration problem or would the proposed bridge work?
Thanks,
VincentSure, there's no reason why the bridge can't go from a topic to a queue, or from a queue to a topic. I don't know what specific problem you were having, but you can do this.
-
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 PMPerhaps 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 -
Keep-alive message bridge connection
Hi,
I have setup messaging bridge between WLS 10.3.0.0 and a JBoss Messaging queque, after about 4 hours of inactivity in a queue bridge was disconneted, is there any way to configure keep-alive connection in WLS bridge ?
Thanks,
LukaszYou can try to set the IdleTimeMaximum setting on your bridge configuration to a very large number. It specifies the maximum amount of time, in seconds, that a messaging bridge instance remains idle.
In “asynchronous” mode, this is the longest amount of time a messaging bridge instance stays idle before it checks the sanity of its connection to the source. In “synchronous” mode, this is the amount of time the messaging bridge can block on a receive call if no transaction is involved.
-Dongbo -
WLS 8.1 SP5 Message bridge doesn't refresh connection after idle time out
Hi,
I am seeing in the log after enabling the debug flags that message bridge intermittently stops refreshing the connection without logging further info and causing a production failure.Bridge is forwarding the message from WLS 8.1..5 DQ to the remote MQ 6.0 queue.
Below is the snippet which doesn't come in the log which suggests that bridge stops refreshing the connection.
<BEA-200027> <Bridge "CASLDNSenderBridge" works in asynchronous mode and has not received messages for the predefined maximum idle time. The connections to the adapters will be interrupted and reestablished.>
The above message does appear everytime but intermittently it stops and the messages put after this leading to the exceptions.The bridge has been configured in asynchronous mode and the idle time out is configured as 60 secs.
Can somebody please let me know if there is any known issue with 8.1 SP5 where message bridge stops refreshing connection intermittently or how to debug this further.I would normally suggest raising the issue with support, but I recall hearing that 8.1 is nearing the end of its support cycle, so I'm not sure that's an option for you. Other options:
- try upgrading to a newer SP, or better yet, a new version of WebLogic
- try changing to synchronous forwarding
- examine thread dumps from when the bridge appears to be stalled
- post the exception that bridge is throwing when it tries to connect
- try patching MQ (the problem could be on the MQ side, and perhaps an older version of the bridge may not be fully capable of handling all of MQs minor quirks)
- write a program to (A) detect inactivity on the src destination, and (B) somehow restart the bridge and/or all of WL when this occurs
Tom -
JMS Message Bridge - WLS to MQ
Hi,
Subsequent to my last posts on Foreign JMS Server setup (where I had to receive a msg from a remote MQ Queue), now I have a requirement to post messages to an remote MQ Queue for a diff application.
As a POC, I configured the JMS Message Bridge with bridge source as my local JMS queue and bridge destination as the Remote MQ Queue and it works fine as expected !!
just have couple of questions on that -
1. For a long time, I was struggling with this error on server startup
<BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
Then I realized from the server log that the actual reason was authentication failure in MQ Queue Manager :
JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager '' with connection mode 'Client' and host name '77.40.190.130'. Please check if the supplied username and password are correct on the QueueManager you are connecting to AND
JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
Since this MQ setup is managed by someone else, when they pass on the .binding file after creating queuemanager, queue, etc, Should I also ask them for the username and password for the QM?? I am not sure if this is a part of the .binding file.
2. Some doubts around the QOS. As I understood, I am using the No-Transaction Adapter. This means I can use QOS as either "Atmost once" or "Duplicate OK". The latter seems to be ok so that I dont lost messages in any case. But I am yet to find out if the other application is ok to handle duplicates.
But is there a restriction/limitation to use "Exactly Once" ?? I noticed that there is also an XA-Transaction Adapter in WLS. Is it not possible to use that with MQ?
Thanks in advance.
best regards,
MuraliIn your binding file QCF or XAQCF definition , you will see a Channel field since you are using a client mode to connect to the queue manager. This channel is called a Server Connection Channel [ SVRCONN]. At the queue manager side of things, when this SVRCONN is defined, MQ Admin teams tend to define an attribute called MCAUSER. In this setup the userid used for authorisation at queue manager is the following in the below precedence:
1. If MCAUSER is defined in the channel, that will be the user id and it overrides any security context sent from client application. This user id should have sufficient permissions to connect to queue manager , get , put. The MQ admin teams on certain platforms will be able to get the exact permission that is missed from the queue manager error logs when a 2035 security exception occurs.
2. If no MCAUSER is defined then the userid passed in the createConnection JMS call will be the user context used.
I am not exactly sure of the behaviour when no MCAUSER and no user id in createConnection calls, but i think it takes the user of the MQ Listener process which starts the SVRCONN channel instance when a client initiates the connection.
So for your situation, it will be worth start checking with how the MQ side configuration is. This issue tends to be a very common issue with client applns connecting to qmgr. -
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]
-
JMS Messaging Bridge Problems with WLS 8.1 sp2
Thank you in advance for your help.
I am trying to configure a JSM Messaging Bridge to connect an MQ Q to a Weblogic
Q. I have this working wonderfully in an environment without clustering but once
I try to deploy to a cluster, I am having two major problems.
1) When the managed servers are restarted, the messaging bridges immediately complain
about not being able to find the resource adaptor. After I manually un-target
the messaging bridge from the cluster and re-target them, they find the resource
adaptor but cannot connect to the source... which leads to my next problem.
2) The messaging bridges cannot connect to the source destination whether it is
an MQ Q or a Weblogic JMS Q does not matter. Here are the log entries that I
see relative:
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Got Notification:weblogic.management.AttributeAddNotification:
Deployments from <null> to [Caching Stub]Proxy for eBusDev02:Location=secaServer01,Name=seca_OES_ADV_REPLY
Messaging Bridge,Type=MessagingBridgeConfig - weblogic.management.AttributeAddNotification[source=eBusDev02:Location=secaServer01,Name=secaServer01,Type=ServerConfig].>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! creating bridge seca_OES_ADV_REPLY Messaging
Bridge.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
is deployed as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Initializging bridge seca_OES_ADV_REPLY Messaging
Bridge as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
source configurations are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = file:/e:/private/JNDI/eBusDev02
DestinationType = Queue
DestinationJNDIName = jms.oes.MQ-ADV-REPLYQ
InitialContextFactory = com.sun.jndi.fscontext.RefFSContextFactory
ConnectionFactoryJNDIName = jms.oes.MQ-QCF
.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
target configurations are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = t3://30.135.10.63:8103,30.135.10.63:8104
DestinationType = Queue
DestinationJNDIName = jms/oes/ADV-REPLYQ
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = jms/oes/QCF
.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
is successfully initialized.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
has been successfully initialized as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Activating bridge seca_OES_ADV_REPLY Messaging
Bridge.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
has been successfully activated..>
####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200033>
<Bridge "seca_OES_ADV_REPLY Messaging Bridge" is obtaining connections to the
two adapters.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
Getting source connection.>
####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200042>
<Bridge seca_OES_ADV_REPLY Messaging Bridge failed to connect to the source destination
and will try again in 15 seconds. (java.lang.NullPointerException)>
I know the queues are up and I am pretty sure my MQ client configuration is correct.
Is there anyway to get more information about the NullPointerException or the
error being encountered?
Given that you have ruled out message backlogs, my first suspicion is that the leak has something to do with connection allocation. Does JMS stats reveal an application generated connection leak? Check to see if the current number of connections/sessions stays steady.
If this doesn't help, you can use a third party tool like OptimizeIt to get periodic snap-shots of memory usage and identify the leaked object (or create a reproducer and have customer support do it). A possible work-around is to modify your app to pool JMS connections/sessions for re-use - greatly reducing the number of connections created per day.
Tom -
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 Tom,
Message Bridge is configured to transfer messages from AQ to DQ.
When the Message Bridge is deployed on Admin Server & Cluster, it works successfully. But, a closer look reveals that it’s the instance deployed on the Admin Server (and not the ones on the cluster) which is doing the job of looking up AQ & DQ and transferring messages from AQ to DQ. Monitoring Message Bridge instances on the cluster shows "WARN: failed to look up the source adapter." The corrective action for this is "Check if the adapter is deployed or the JNDI name in the source JMSBridgeDestination instance is correct.". But the adapter is correctly deployed and the JNDI name of the AQ is correctly bound, else the Message Bridge wouldn't have shown "Forwarding messages." for Admin Server's Message Bridge instances. The same set of configuration (MB destinations and MB) is shared by the Message Bridge instances on Admin Server & Cluster. So, the question of incorrect configuration of the JMS destinations i.e. AQ & DQ doesn't arise.
Can you point out where the problem could be ? ?:|
Cheers
DipsPatch for this problem should be added to the front of your WLS instance's CLASSPATH prior to any weblogic classes. This issue is resolved in WLS 8.1 SP3 and this is the recommended path to resolution, the patch should be used only if one can't upgrade to SP3.
CR126671
Setup a cluster configuration on 8.1SP1 with at least on managed server in the cluster. Deploy the bridge adapter jms-xa-adp.rar to the cluster. Configure a bridge and target it to the cluster.Bridge never receives Add
Notification for the adapter. However, if you retarget the adapter to the individual servers in the cluster it works fine.
Dips -
Dump produced after install WLS 8.1 SP3
Hi there,
I am sending you the DUMP file generated a lot of times after we had just installed the SP 3. I am not sending the MDUMP file because its size is larger then 180Mb. The same code that generated this error worked fine when we were using the SP 2. It has never occured a DUMP while we were using the SP 2.
My server configuration:
before the SP3 installation:
- WLS 8.1 SP2
- BEA WebLogic JRockit(TM) 1.4.2_04 JVM (build ari-29212-20040415-1348-win-ia32)
- SQL Server 2000
- DB JDBC Driver weblogic.jdbc.sqlserver.SQLServerDriver
after the SP3 installation:
- WLS 8.1 SP3
- BEA WebLogic JRockit(TM) 1.4.2_04 JVM (build ari-31788-20040616-1132-win-ia32)
- SQL Server 2000
- DB JDBC Driver weblogic.jdbc.sqlserver.SQLServerDriver
Piece of code where the error occured:
public void executeData(String sql) throws DAOException {
if (Util.isEmpty(sql)){
return;
Connection con = null;
Statement st = null;
try {
con = getConnection();
st = con.createStatement();
if (logger.isDebugEnabled())
logger.debug("Antes do execute do sql no DAO " + sql); // the sql variable has lots of "update" statements (more then 100)
int rs = st.executeUpdate(sql); // THE ERROR OCCURES HERE
st.close();
} catch (SQLException sqe) {
logger.error(sqe.toString(), sqe);
throw new DAOException(sqe);
} catch (Exception ex) {
logger.error("Erro inesperado na aplicação do sql no banco", ex);
throw new DAOException(ex);
} finally {
cleanup(con, st);
Thanks
===== BEGIN DUMP =============================================================
JRockit dump produced after 0 days, 02:49:43 on Thu Sep 09 10:05:17 2004
Additional information is available in:
D:\bea\user_projects\Mercador_PROD\jrockit.3332.dump
D:\bea\user_projects\Mercador_PROD\jrockit.3332.mdmp
Please send the file(s), information about your system
setup and the program you were running to [email protected]. Thank you.
Error Message: Stack overflow
Version : BEA WebLogic JRockit(TM) 1.4.2_04 JVM ari-31788-20040616-1132-win-ia32
Threads / GC : Native Threads, GC strategy: parallel
: mmHeap->data = 0x10020000, mmHeap->top = 0x54C20000
: mmStartCompaction = 0x303C0000, mmEndCompaction = 0x359B0000
Number CPUs : 2
Tot Phys Mem : 2683813888
OS version : Microsoft Windows 2000 Service Pack 4 (Build 2195)
State : JVM is running
Command Line : -Djava.class.path=D:\bea\jrockit81sp3_142_04\lib\tools.jar;D:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;D:\bea\WEBLOG~1\server\lib\weblogic.jar;D:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;D:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;D:\bea\jrockit81sp3_142_04\jre\lib\rt.jar;D:\bea\WEBLOG~1\server\lib\webservices.jar;D:\bea\weblogic81\server\lib\JSQLConnect.jar; -Xgc:parallel -XXfullsystemgc -Xmanagement -Xms1100m -Xmx1100m -Dweblogic.Name=Mercador -Dweblogic.management.username= -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=D:\bea\WEBLOG~1\server\lib\weblogic.policy -Dsun.java.command=weblogic.Server
Environment : JAVA_HOME=D:\bea\jrockit81sp3_142_04, java.home=D:\bea\jrockit81sp3_142_04\jre, java.class.path=D:\bea\jrockit81sp3_142_04\lib\tools.jar;D:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;D:\bea\WEBLOG~1\server\lib\weblogic.jar;D:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;D:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;D:\bea\jrockit81sp3_142_04\jre\lib\rt.jar;D:\bea\WEBLOG~1\server\lib\webservices.jar;D:\bea\weblogic81\server\lib\JSQLConnect.jar;, java.library.path=D:\bea\jrockit81sp3_142_04\jre\bin;.;C:\WINNT\system32;C:\WINNT;D:\bea\jrockit81sp3_142_04\jre\bin;D:\bea\WEBLOG~1\server\bin;D:\bea\jrockit81sp3_142_04\jre\bin;D:\bea\jrockit81sp3_142_04\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;D:\bea\WEBLOG~1\server\bin\oci920_8
C Heap : Good; no memory allocations have failed
Registers:
Converted EIP: 004ef5dd
EAX = 00000000 EBX = 5be2a26c
ECX = 5be0fc40 EDX = 5e2c103d
ESI = 5be0fc40 EDI = 1e45ad90
EIP = 004ef5dd ESP = 5e2c1000
EBP = 5be2a1e0 EFL = 00010202
CS = 001b DS = 0023 ES = 0023
SS = 0023 FS = 0038 GS = 0000
Stack:
5e2c1000 :5be2a26c 00000000 00000000 00000000 00000000 5be2a1e0
5e2c1018 :0056ae00 0055f017 5be0fc40 5be2a1e0 5e2c1038 5be2a2dc
5e2c1030 :5be0fc40 55f70707 5be2a26c 54c99368 5be2a2dc 00000000
5e2c1048 :5be0fc40 5be2a1e0 5be2a26c 1e45ae08 1e45ae0d 55f70758
5e2c1060 :54c2d910 1e45ad90 5be0fc40 22f30898 55f70b00 00000058
5e2c1078 :00000022 6e000aa3 00000053 1e45ad90 22f307f0 00000010
5e2c1090 :1e45ad90 000df4ab 6e0001d3 1e45ad68 5be2a1e0 6e0004f4
5e2c10a8 :000df49b 000df49a 1e45ad68 22f30820 6e0005cc 1e45aea0
5e2c10c0 :000df493 22f307b8 1e45ad68 6e001e1f 22f30770 5be2a1e0
5e2c10d8 :000df492 1e45aea0 000df448 1e45ad90 6e001225 00000007
5e2c10f0 :22f303a8 1e45ad68 5be2a1e0 22f303a8 22f303a8 22f303a8
5e2c1108 :00000001 22f30320 000df447 22f30340 1e45ad68 5be2a1e0
5e2c1120 :6e001710 22f302e8 22f302e8 22f302e8 22f302e8 22f302e8
5e2c1138 :22f302e8 22f2f108 1e45ad68 22f2f0b0 6e0017f2 22f2f0b0
5e2c1150 :22f2f0b0 22f2f0b0 22f2f0b0 22f2f0b0 22f2f0b0 22f2e388
5e2c1168 :1e45ad68 22f2e330 6e0017f2 22f2e330 22f2e330 22f2e330
5e2c1180 :22f2e330 22f2e330 22f2e330 22f2d4a0 1e45ad68 22f2d448
5e2c1198 :6e0017f2 22f2d448 22f2d448 22f2d448 22f2d448 22f2d448
5e2c11b0 :22f2d448 22f2c938 1e45ad68 22f2c8e0 6e0017f2 22f2c8e0
5e2c11c8 :22f2c8e0 22f2c8e0 22f2c8e0 22f2c8e0 22f2c8e0 000df0a3
5e2c11e0 :1e45ad68 22f2be38 6e0017f2 22f2be38 22f2be38 22f2be38
5e2c11f8 :22f2be38 22f2be38 22f2be38 000df094 1e45ad68 22f2bc80
5e2c1210 :6e0017f2 22f2bc80 22f2bc80 22f2bc80 22f2bc80 22f2bc80
5e2c1228 :22f2bc80 22f2b708 1e45ad68 22f2b6b0 6e0017f2 22f2b6b0
5e2c1240 :22f2b6b0 22f2b6b0 22f2b6b0 22f2b6b0 22f2b6b0 000defc6
5e2c1258 :1e45ad68 22f2ac50 6e0017f2 22f2ac50 22f2ac50 22f2ac50
5e2c1270 :22f2ac50 22f2ac50 22f2ac50 000defb7 1e45ad68 22f2aa98
5e2c1288 :6e0017f2 22f2aa98 22f2aa98 22f2aa98 22f2aa98 22f2aa98
5e2c12a0 :22f2aa98 22f2a510 1e45ad68 22f2a4b8 6e0017f2 22f2a4b8
5e2c12b8 :22f2a4b8 22f2a4b8 22f2a4b8 22f2a4b8 22f2a4b8 000deee8
5e2c12d0 :1e45ad68 22f29a68 6e0017f2 22f29a68 22f29a68 22f29a68
5e2c12e8 :22f29a68 22f29a68 22f29a68 000deed9 1e45ad68 22f298b0
5e2c1300 :6e0017f2 22f298b0 22f298b0 22f298b0 22f298b0 22f298b0
5e2c1318 :22f298b0 22f29340 1e45ad68 22f292e8 6e0017f2 22f292e8
5e2c1330 :22f292e8 22f292e8 22f292e8 22f292e8 22f292e8 000dee0d
5e2c1348 :1e45ad68 22f28898 6e0017f2 22f28898 22f28898 22f28898
5e2c1360 :22f28898 22f28898 22f28898 000dedfe 1e45ad68 22f286c0
5e2c1378 :6e0017f2 22f286c0 22f286c0 22f286c0 22f286c0 22f286c0
5e2c1390 :22f286c0 22f28150 1e45ad68 22f280f8 6e0017f2 22f280f8
5e2c13a8 :22f280f8 22f280f8 22f280f8 22f280f8 22f280f8 22f27938
5e2c13c0 :1e45ad68 22f278e0 6e0017f2 22f278e0 22f278e0 22f278e0
5e2c13d8 :22f278e0 22f278e0 22f278e0 000debeb 1e45ad68 22f25ba0
5e2c13f0 :6e0017f2 22f25ba0 22f25ba0 22f25ba0 22f25ba0 22f25ba0
5e2c1408 :22f25ba0 22f256b0 1e45ad68 22f25658 6e0017f2 22f25658
5e2c1420 :22f25658 22f25658 22f25658 22f25658 22f25658 000deb54
5e2c1438 :1e45ad68 22f24c70 6e0017f2 22f24c70 22f24c70 22f24c70
5e2c1450 :22f24c70 22f24c70 22f24c70 22f24788 1e45ad68 22f24730
5e2c1468 :6e0017f2 22f24730 22f24730 22f24730 22f24730 22f24730
5e2c1480 :22f24730 22f23ba0 1e45ad68 22f23b48 6e0017f2 22f23b48
5e2c1498 :22f23b48 22f23b48 22f23b48 22f23b48 22f23b48 22f22620
5e2c14b0 :1e45ad68 22f225c8 6e0017f2 22f225c8 22f225c8 22f225c8
5e2c14c8 :22f225c8 22f225c8 22f225c8 22f20f58 1e45ad68 22f20f00
5e2c14e0 :6e0017f2 22f20f00 22f20f00 22f20f00 22f20f00 22f20f00
5e2c14f8 :22f20f00 22f201c0 1e45ad68 22f20168 6e0017f2 22f20168
5e2c1510 :22f20168 22f20168 22f20168 22f20168 22f20168 22f1ef58
5e2c1528 :1e45ad68 22f1ef00 6e0017f2 22f1ef00 22f1ef00 22f1ef00
5e2c1540 :22f1ef00 22f1ef00 22f1ef00 22f1e1c0 1e45ad68 22f1e168
5e2c1558 :6e0017f2 22f1e168 22f1e168 22f1e168 22f1e168 22f1e168
5e2c1570 :22f1e168 22f1cf58 1e45ad68 22f1cf00 6e0017f2 22f1cf00
5e2c1588 :22f1cf00 22f1cf00 22f1cf00 22f1cf00 22f1cf00 22f1c1c0
5e2c15a0 :1e45ad68 22f1c168 6e0017f2 22f1c168 22f1c168 22f1c168
5e2c15b8 :22f1c168 22f1c168 22f1c168 22f1af58 1e45ad68 22f1af00
5e2c15d0 :6e0017f2 22f1af00 22f1af00 22f1af00 22f1af00 22f1af00
5e2c15e8 :22f1af00 22f1a1c0 1e45ad68 22f1a168 6e0017f2 22f1a168
5e2c1600 :22f1a168 22f1a168 22f1a168 22f1a168 22f1a168 22f18f58
5e2c1618 :1e45ad68 22f18f00 6e0017f2 22f18f00 22f18f00 22f18f00
5e2c1630 :22f18f00 22f18f00 22f18f00 22f181c0 1e45ad68 22f18168
5e2c1648 :6e0017f2 22f18168 22f18168 22f18168 22f18168 22f18168
5e2c1660 :22f18168 22f16f58 1e45ad68 22f16f00 6e0017f2 22f16f00
5e2c1678 :22f16f00 22f16f00 22f16f00 22f16f00 22f16f00 22f161c0
5e2c1690 :1e45ad68 22f16168 6e0017f2 22f16168 22f16168 22f16168
5e2c16a8 :22f16168 22f16168 22f16168 22f14f58 1e45ad68 22f14f00
5e2c16c0 :6e0017f2 22f14f00 22f14f00 22f14f00 22f14f00 22f14f00
5e2c16d8 :22f14f00 22f141c0 1e45ad68 22f14168 6e0017f2 22f14168
5e2c16f0 :22f14168 22f14168 22f14168 22f14168 22f14168 22f132a8
5e2c1708 :1e45ad68 22f13250 6e0017f2 22f13250 22f13250 22f13250
5e2c1720 :22f13250 22f13250 22f13250 22f12718 1e45ad68 22f126c0
5e2c1738 :6e0017f2 22f126c0 22f126c0 22f126c0 22f126c0 22f126c0
5e2c1750 :22f126c0 000ddc2e 1e45ad68 22f11b70 6e0017f2 22f11b70
5e2c1768 :22f11b70 22f11b70 22f11b70 22f11b70 22f11b70 000ddc1f
5e2c1780 :1e45ad68 22f119b8 6e0017f2 22f119b8 22f119b8 22f119b8
5e2c1798 :22f119b8 22f119b8 22f119b8 22f11428 1e45ad68 22f113d0
5e2c17b0 :6e0017f2 22f113d0 22f113d0 22f113d0 22f113d0 22f113d0
5e2c17c8 :22f113d0 000ddb41 1e45ad68 22f10898 6e0017f2 22f10898
5e2c17e0 :22f10898 22f10898 22f10898 22f10898 22f10898 000ddb32
5e2c17f8 :1e45ad68 22f106c0 6e0017f2 22f106c0 22f106c0 22f106c0
Code:
004ef4dd :44890000 548b1424 78a11424 8b005ada c0851004 80c71b74
004ef4f5 :000000c0 00000000 00c4808b c0850000 ff500774 58210015
004ef50d :75f68500 6a046a2e cd946801 4c8d0058 396a2424 83d3ff51
004ef525 :f88314c4 8d077339 52182454 706805eb e80058cd 00019e33
004ef53d :8b04c483 8b0c2444 5bb2400d 81348900 63980d8b 3b40005b
004ef555 :244489c1 248c0f0c 5effffff c4835b5d ccccc348 cccccccc
004ef56d :8bcccccc 5b63980d 85c03300 8b167ec9 5bb24015 348b5600
004ef585 :c13b4082 000006c7 f27c0000 ccccc35e cccccccc cccccccc
004ef59d :a1cccccc 005bb244 0f75c085 0b9d7eb8 4ecde800 44a30008
004ef5b5 :8b005bb2 4f71e8c8 ff250008 997fffff 63983df7 c28b005b
004ef5cd :83ccccc3 4c8b18ec 84a11c24 53005bb2 8b575655 db330c79
004ef5e5 :89ffff83 8910245c 751c2444 b244a12d c33b005b 7eb80f75
004ef5fd :e8000b9d 00084e7b 5bb244a3 e8c88b00 00084f1f ffffff25
004ef615 :3df7997f 005b6398 7c89fa8b 40a11824 8b005bb2 758bb82c
004ef62d :89f68500 8924246c 74142474 009b8d34 8b000000 24548916
004ef645 :24548b20 24448b24 244c8b14 b10ff020 0fc63b0a 0000ce84
004ef65d :00758b00 7489f685 d7751424 5bb240a1 244c8b00 75c98510
004ef675 :55006a3f b23c15ff 4c8b005b 158b2424 005bb284 3b08c483
004ef68d :ff850fd1 85000000 0e850fc0 8b000001 bb2c2454 00000001
004ef6a5 :10245c89 ff0c42c7 e9ffffff ffffff6e 6398158b 3b47005b
004ef6bd :33027cfa b80c8bff 8b003983 7518244c 3bff8b15 471374f9
004ef6d5 :027cfa3b 348bff33 003e83b8 f93bed74 01bb3e75 53000000
Loaded modules:
(* denotes the module causing the exception)
0x77f80000-0x77ffcfff C:\WINNT\system32\ntdll.dll
0x7c570000-0x7c627fff C:\WINNT\system32\KERNEL32.dll
0x7c2d0000-0x7c331fff C:\WINNT\system32\ADVAPI32.dll
0x77d30000-0x77da0fff C:\WINNT\system32\RPCRT4.DLL
0x78000000-0x78044fff C:\WINNT\system32\MSVCRT.dll
0x00410000-0x0060efff* D:\bea\jrockit81sp3_142_04\jre\bin\jrockit\jvm.dll
0x77570000-0x7759ffff C:\WINNT\system32\WINMM.dll
0x77e10000-0x77e74fff C:\WINNT\system32\USER32.DLL
0x77f40000-0x77f7dfff C:\WINNT\system32\GDI32.DLL
0x782f0000-0x78537fff C:\WINNT\system32\SHELL32.dll
0x70a70000-0x70ad4fff C:\WINNT\system32\SHLWAPI.DLL
0x71710000-0x71793fff C:\WINNT\system32\COMCTL32.DLL
0x75030000-0x75043fff C:\WINNT\system32\WS2_32.dll
0x75020000-0x75027fff C:\WINNT\system32\WS2HELP.DLL
0x7c340000-0x7c395fff D:\bea\jrockit81sp3_142_04\jre\bin\MSVCR71.dll
0x10000000-0x10018fff D:\bea\jrockit81sp3_142_04\jre\bin\java.dll
0x00b30000-0x00b3dfff D:\bea\jrockit81sp3_142_04\jre\bin\verify.dll
0x74fd0000-0x74fedfff C:\WINNT\system32\msafd.dll
0x75010000-0x75016fff C:\WINNT\System32\wshtcpip.dll
0x692e0000-0x69306fff C:\WINNT\system32\pdh.dll
0x76b30000-0x76b6dfff C:\WINNT\system32\comdlg32.dll
0x77a50000-0x77b3efff C:\WINNT\system32\ole32.dll
0x779b0000-0x77a4afff C:\WINNT\system32\OLEAUT32.dll
0x69280000-0x69288fff C:\WINNT\system32\perfos.dll
0x782c0000-0x782cbfff C:\WINNT\System32\rnr20.dll
0x77980000-0x779a3fff C:\WINNT\system32\DNSAPI.DLL
0x75050000-0x75057fff C:\WINNT\system32\WSOCK32.DLL
0x77340000-0x77352fff C:\WINNT\system32\iphlpapi.dll
0x77520000-0x77524fff C:\WINNT\system32\ICMP.DLL
0x77320000-0x77336fff C:\WINNT\system32\MPRAPI.DLL
0x75150000-0x7515efff C:\WINNT\system32\SAMLIB.DLL
0x75170000-0x751befff C:\WINNT\system32\NETAPI32.DLL
0x59810000-0x5981efff C:\WINNT\system32\SECUR32.DLL
0x751c0000-0x751c5fff C:\WINNT\system32\NETRAP.DLL
0x77950000-0x77979fff C:\WINNT\system32\WLDAP32.DLL
0x773b0000-0x773defff C:\WINNT\system32\ACTIVEDS.DLL
0x77380000-0x773a2fff C:\WINNT\system32\ADSLDPC.DLL
0x77830000-0x7783dfff C:\WINNT\system32\RTUTILS.DLL
0x77880000-0x7790dfff C:\WINNT\system32\SETUPAPI.DLL
0x7c0f0000-0x7c150fff C:\WINNT\system32\USERENV.DLL
0x774e0000-0x77512fff C:\WINNT\system32\RASAPI32.DLL
0x774c0000-0x774d0fff C:\WINNT\system32\RASMAN.DLL
0x77530000-0x77551fff C:\WINNT\system32\TAPI32.DLL
0x77360000-0x77378fff C:\WINNT\system32\DHCPCSVC.DLL
0x777e0000-0x777e7fff C:\WINNT\System32\winrnr.dll
0x777f0000-0x777f4fff C:\WINNT\system32\rasadhlp.dll
0x621c0000-0x621c5fff D:\bea\jrockit81sp3_142_04\jre\bin\ioser12.dll
0x06640000-0x06644fff D:\bea\weblogic81\server\bin\wlntio.dll
0x6cd60000-0x6ce20fff D:\bea\jrockit81sp3_142_04\jre\bin\dbghelp.dll
0x77820000-0x77826fff C:\WINNT\system32\VERSION.dll
0x759b0000-0x759b5fff C:\WINNT\system32\LZ32.DLL
0x690a0000-0x690aafff C:\WINNT\system32\psapi.dll
Java Thread ID = 0x00000880, lastJavaFrame = 0x5E2C103C, Name = ExecuteThread: '4' for queue: 'weblogic.kernel.Default'
Thread Stack Trace:
at _mmAllocateThreadLocalAreaMemory+13()@0x004EF5DD
at jrockit/vm/MemSystem.getMoreTLAMemory(Native Method)@0x55F706C0
at jrockit/vm/MemSystem.getMoreTLAMemoryWrapper(Native Method)@0x55F70758
at jrockit/vm/MemSystem.allocArray2(Native Method)@0x55F70B00
at weblogic/jdbc/base/BaseSQLScanner$BaseSQLScannerIDOrKeywordState.processChar(Optimized Method)@0x6E000AA3
at weblogic/jdbc/base/BaseSQLScanner.getNextToken(Optimized Method)@0x6E0001D3
at weblogic/jdbc/base/BaseSQLParser.matchWhiteSpaceOrComment(Optimized Method)@0x6E0004F4
at weblogic/jdbc/base/BaseSQLParser.matchWhiteSpaceOrComment(Optimized Method)@0x6E0005CC
at weblogic/jdbc/base/BaseSQLParser.parseParenthesizedExpression(Optimized Method)@0x6E001E1F
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E001710
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents(Optimized Method)@0x6E0017F2
at weblogic/jdbc/base/BThe dump is caused by a stackoverflow condition. For some reason JRockit is not able to throw the StackOverFlowError (this can be really tricky in a JVM when there is no stack left).
The cause seems to be that weblogic/jdbc/base/BaseSQLParser.parseUnknownStatementComponents calls itself recursively quite a few times. I don't anything about that code so I couldn't tell you why there are are so many recursive calls. Maybe there is something in your SQL statement that causes the driver to do this?
The reason this happens after the SP3 installation can be a couple of things: 1) code in the driver has changed 2) code in WLS has changed 3) changes in JRockit may cause the stackoverflow to happen in a "bad" place which we cannot handle.
You can try increasing the stack size with the -Xss parameter. I think the default is 64kB, so try the double or more.
Maybe you should contact support for the db driver and ask them why the recursive calls happen.
Regards,
/Staffan -
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….
Maybe you are looking for
-
ITunes wont open on laptop (running windows 7)
It was working earlier but it seems a update for either windows or apple has been automatically downloaded and as a consequence when i click on iTunes it doesnt open and does nothing? I have uninstalled and reinstalled the most up to date version bu
-
Two action in Universal Worklist
Hi Experts, Whenever I test any of the process by initiating it and then I check that action in the universal worklist then it show two action means if I have generated Action1 from the process1. then in the Universal Worklist I found the list as
-
Software Update persistent Error
Hi, Please help. I am currently on BB 10 OS version 10.1.0.273, I want to upgrade to version 10.2.1.537. I tried updating my BB Z10 software on the web and using USB in the BB link , every time i get to 25%-26% i get an error saying "An error has occ
-
2 versions of .jar, need to launch correct version
Currently, our users are using a shortcut in Windows95/NT to launch a jar file. Now they will have two versions of the jar file, version_a.jar and version_b.jar. Now there will also need to be an ini file (or properties file) that will have four line
-
"Donnée insuffisante pour image"
Bonjour, Quand j'essaie d'ouvrir un fichier pdf sur le réseau, il m'apparait ce message d'erreur. Par contre, le fichier s'affiche sans message d'erreur quand je diminue le zoom... Dans le cas contraire, le message d'erreur survient et aussi quand j'