2nd createTopicConnection to a diffferent host/server hangs

Question

From a client (running on jre 1.5) using wlclient.jar and wljmsclient.jar (from v9.0 GA release), I can connect successfully to a jms server on host 1 (running wl 8.1 sp4) and receive messages.
          When I try to connect to a 2nd topic on another host/server (also running wl 8.1 sp4) , my client hangs for several minutes while calling createTopicConnection.
          If I reverse the order that I connect to the servers, it is still the 2nd connection that fails.
          It eventually throws an exception:
          weblogic.jms.common.JMSException: Error finding dispatcher
               at weblogic.jms.frontend.FEConnectionFactory.connectionCreateInternal(FEConnectionFactory.java:423)
               at weblogic.jms.frontend.FEConnectionFactory.connectionCreateRequest(FEConnectionFactory.java:386)
               at weblogic.jms.frontend.FEConnectionFactory_WLSkel.invoke(Unknown Source)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
               at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
               at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
               at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
               at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
          Caused by: weblogic.jms.dispatcher.DispatcherException: can not add a disconnected JMS Dispatcher espeed2
               at weblogic.jms.dispatcher.DispatcherManager.dispatcherAdd(DispatcherManager.java:132)
               at weblogic.jms.dispatcher.DispatcherManager.dispatcherAdd(DispatcherManager.java:103)
               at weblogic.jms.dispatcher.DispatcherManager.addDispatcherReference(DispatcherManager.java:197)
               at weblogic.jms.frontend.FEConnectionFactory.connectionCreateInternal(FEConnectionFactory.java:418)
          Any ideas how we can subscribe to 2 different topics on 2 different servers ?

Answer 1

Is the problem that these jms servers although uniquely           > named in all other respects are defined in the same wl
          > domain ?
          No. This is OK and quite common. (I should have been more clear in my original response.)
          Given that everything works when you use the full weblogic.jar. The best I can think of is try out the latest service-pack for 8.1, and make sure that you are using the newly released version of 9.0 rather than the beta.
          Also, I just noticed you are using the 9.0 thin client. You might be running into known problems with 9.0 thin client interoperability with older versions. These problems are slated to be fixed in the next incremental release (I'm not sure when this is due out, a few months?). I recommend filing a case with customer support.
          Tom