• Post Reply Bookmark Topic Watch Topic
  • New Topic

JMS Connection not found Exception in clustered environment  RSS feed

s pramod
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We have two servers(weblogic) lets say server A and server B both clustered set-up running application APP-A and APP-B.When we try to send a message from a session Bean on server A to a JMS Queue on server B we get the following exception:
Caused by: weblogic.jms.common.JMSException: Connection not found
at weblogic.jms.dispatcher.InvocableManager.invocableFind(InvocableManager.java:136)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:608)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsyncInternal(DispatcherImpl.java:128)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.java:180)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
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:144)
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)
at java.lang.Thread.startThreadFromVM(Unknown Source)

We were able to solve the problem by changing the admin server name of server B (previously both were named adminserver).Can anyone please throw some light on the solution? Because the site where i got this idea "http://forums.bea.com/bea/message.jspa?messageID=202174377" doesnt mention the reason why this problem is faced.

It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!