The name it is referencing / trying to lookup contains the name of the
JMS server on the "server" machine (GFAIMT_JmsServer). So it must be
connecting, finding the correct topic, and looking for the server that
contains that topic? But the JNDI name it is actually looking up
looks like something internal to WLS's implementation:
"weblogic.jms.backend.GFAIMT_JmsServer"
Anyone have a similiar issue?
The root cause in the exception stack trace is listed as:
Caused by: javax.naming.NameNotFoundException: Unable to resolve
'weblogic.jms.backend.GFAIMT_JmsServer'. Resolved
'weblogic.jms.backend'; remaining name 'GFAIMT_JmsServer'
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:
1139)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:
252)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:
171)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:
206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:
214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:
214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:
214)
at
weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:
269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:
362)
at
weblogic.jms.frontend.FEConnection.createDestination(FEConnection.java:
841)