JMS Exception: Connection not found

Question

I get a Connection not found exception when creating a TopicSession to communicate with a remote server. Here's the situation. I have several MDBs listening to one jms topic on Weblogic 6.1. They work properly sending and receiving jms messages from the topic when run within one server.
However, I have a second Weblogic 6.1 server with the same named jms connection factory and topic as on the first machine with the MDBs deployed. I am trying to send jms messages from a stateless session bean within the first server to the second server's topic to trigger the MDBs deployed on that machine.
I create a connection using the InitialContext and get the topic but when I try and create the TopicSession, it breaks. Here's the code:
Properties myEnvironment = new Properties();
myEnvironment.setProperty(Context.INITIAL_CONTEXT_FACTORY, WEBLOGIC_ICF);
myEnvironment.setProperty(Context.PROVIDER_URL, "t3://<serverAddress>:7031");
Context myContext = new InitialContext(myEnvironment);
TopicConnectionFactory myTCFactory = (TopicConnectionFactory) myContext.lookup(CONNECTION_FACTORY);
Topic myTopic = (Topic) myContext.lookup(TOPIC_NAME);
TopicConnection myTopicConnection = myTCFactory.createTopicConnection();
// Connection is not null but breaks here:
TopicSession myTopicSession = myTopicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
And here is the error message that results.
weblogic.jms.common.JMSException: Connection not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:121)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:509)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:272)
at weblogic.jms.client.JMSConnection.sessionCreate(JMSConnection.java:268)
at weblogic.jms.client.JMSConnection.createTopicSession(JMSConnection.java:245)
at com.informore.scenariomanager.util.ScmEventJMSUtil.openTopicConnection(Unknown Source)
at com.informore.scenariomanager.components.topicdispatcher.ejb.TopicDispatcherEJB.sendTopicMessage(Unknown Source)
at com.informore.scenariomanager.components.topicdispatcher.ejb.TopicDispatcherEJB.handleMessagesPosted(Unknown Source)
at com.informore.scenariomanager.components.topicdispatcher.ejb.TopicDispatcherEJB.processJMSMessage(Unknown Source)
at com.informore.scenariomanager.components.topicdispatcher.ejb.TopicDispatcherEJB_44hyzr_ELOImpl.processJMSMessage(TopicDispatcherEJB_44hyzr_ELOImpl.java:200)
at com.informore.scenariomanager.components.topicdispatcher.ejb.TopicDispatcherMDB.onMessage(Unknown Source)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
I've tried using "org.omg.CORBA.ORBInitialHost" and "org.omg.CORBA.ORBInitialPort" to no avail. And, because I will potentially need MDBs running on the current and several other remote servers, I don't want to have to specify only one target machine. Any help or suggestions GREATLY appreciated!
Thanks.

Answer 1

Thanks !
I had the same problem on wls 7.0 and it solved it.
I tried to send a JMS from server to server and got :
weblogic.jms.common.JMSException: Connection not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:134)
The problem was that the two servers had the same name !
Ilan.