MQSeries.net :: View topic

brand3111 · Posted: Fri May 19, 2006 2:01 am Post subject:

i've used an ibm tutorial to setup a bridge from mq to weblogic jms provider and vice versa. this works fine using jmsadmin to define mq jndi objects on the filesystem and using weblogic console for weblogic jndi objects.

this all works fine when both providers reside on the same machine. however, when they're on separate machines things get complicated. since i used the local file system to store mq jndi objects, they are no longer accessible since weblogic now is on a different machine. given this, the source destination of the bridge cannot find the jndi objects through a connection url that points to the local file system.

here's what i've tried in attempt to work around it (to no avail). i placed(and configured) jmsadmin on the weblogic server, including all applicable jars. i define local objects on this server. one in particular, the qcf, contains a hostname which points to the mq server. this way, the objects are now local for the source destination configuration to see via weblogic console.

trouble is, when i change the source destination to point to the new jndi objects which are now local, i receive a resource exception. here it is:

####<May 12, 2006 1:32:21 PM PDT> <Warning> <Connector> <ISGLWARNERJXP> <myserver> <ExecuteThread: '4' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-190032> << Weblogic Messaging Bridge Adapter (No TX)_eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
####<May 12, 2006 1:32:21 PM PDT> <Info> <MessagingBridge> <ISGLWARNERJXP> <myserver> <ExecuteThread: '4' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200042> <Bridge MQ-WLS81 failed to connect to the source destination and will try again in 20 seconds. (javax.resource.ResourceException: Failed to start the connection)>

and here's how i defined my qcf that's now local on the weblogic box:

def qcf(QCF) hostname(00.00.0.00) port(1414) channel(SYSTEM.DEF.SVRCONN) transport(CLIENT) qmanager(QM1)

where hostname is the ip of my mq machine and qmanager is the qmanager residing on the mq machine. what concerns me here is the channel. i'm not sure if this is required for a bridge and possibly it could be causing a problem. it's defined by default on the mq server, yet doesn't look like it's active.

i know this is done frequently otherwise the concept of the bridge would be pointless.

please could someone let me know if they've any experience with this and what the problem might be.

thanks,
brian