How to configure Message bridge

Kenny Yang

unread,

Jun 20, 2002, 11:19:22 AM6/20/02

to

Hi,
I am trying to setup a JMS Message Bridge for prove of concept purpose in Weblogic
7.0. Here is my configurations from config.xml:

<JMSBridgeDestination
AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
ConnectionFactoryJNDIName="weblogic.jms.testConnectionFactory"
ConnectionURL="t3://localhost:7001"
DestinationJNDIName="examples.queue2" Name="LocalBridge"
UserName="kyang" UserPassword="{3DES}2LeceOSYOaRuCvrFshnBZg=="/>
ConnectionFactoryJNDIName="weblogic.jms.ClientConnectionFactory"
ConnectionURL="t3://localhost:7001"
DestinationJNDIName="examples.queue1"
Name="MQWeblogicDestination" UserName="kyang"/>

..
<JMSConnectionFactory DefaultDeliveryMode="Persistent"
DefaultTimeToDeliver="200" DefaultTimeToLive="1000"
JNDIName="weblogic.jms.ClientConnectionFactory"
LoadBalancingEnabled="false" MessagesMaximum="100"
Name="ClientConnectionFactory" OverrunPolicy="KeepNew"
ServerAffinityEnabled="false" Targets="examplesServer"/>
<JMSConnectionFactory DefaultDeliveryMode="Non-Persistent"
DefaultTimeToDeliver="200" DefaultTimeToLive="1000"
FlowControlEnabled="false"
JNDIName="weblogic.jms.testConnectionFactory"
Name="testConnectionFactory" OverrunPolicy="KeepNew" Targets="examplesServer"/>

...

<MessagingBridge Name="MyMessaging Bridge" Selector="*"
SourceDestination="LocalBridge"
TargetDestination="MQWeblogicDestination" Targets="examplesServer"/>
################################

I used a test client get InitialContext with url:"t3://localhost:7001" and send
the message to "examples.queue2" which is "MyJMSQueue".

From the monitor screen I found the message was put on "MyJMSQueue" but the message
was nerver delieveried to the "examples.queue1".
From the log, I got following message:
<Jun 20, 2002 10:05:53 AM CDT> <Info> <MessagingBridge> <200012> <Bridge "MyMess
aging Bridge" suceesfully found the two adapters configured for it.>

Do you have any suggestions?

Thanks a lot!

Dongbo Xiao

unread,

Jun 20, 2002, 1:26:11 PM6/20/02

to

The second JMSBridgeDestination has a UserName with an
empty UserPassword. There is a bug in 7.0 that causes the
bridge failed to start. The bug has been fixed in the
next release. For now, you'll have to set UserPassword
attribute if you set UserName attribute.

Looks like you are setting up a bridge between two WLS 7.0
queues and your bridge is using "Exactly-once" quality of
service (which is the default). Please be aware that there
are some special configuration requirements for the bridge to
work in this kind of cases. If you are just doing a trial of
the new feature, I suggest you use "Atmost-once" or "Duplicate-okay"
quality of service. If you do need "Exactly-once", please check the
configuration requirements at:

http://edocs.bea.com/wls/docs70/adminguide/msgbridge.html#1063962

Hope this helps,

Dongbo

Kenny Yang

unread,

Jun 20, 2002, 2:40:38 PM6/20/02

to

Mr.Xiao,
Thanks! Things are getting better after I made changes according to your suggestion.
Now the status is showing: Forwarding Messages. But I still have following exceptions
from the logging window:

where can I get the context:"comp/env/wls-connector-resref"?

Dongbo Xiao

unread,

Jun 20, 2002, 3:44:47 PM6/20/02

to

Don't worry about the log messages about
"comp/env/wls-connector-resref".
It is not a problem for the Messaging Bridge feature.
The real problem is that you have an invalid selector for the
MessagingBridge. A bridge selector has the same syntax as a JMS message
selector. As you can see from the JMS specification, a message selector
syntax is based on a subset of the SQL92 conditional expression syntax.

I would suggest you try the bridge feature without any selection first
and add the selector later.

Dongbo