I was trying to set up a foreign server for JMS. Both servers are
WLS 9.2. One acting as the jms 'client' for topic publisher and
subscriber and an MDB as well, one as the JMS provider. The foreign
server was configured, foreign server, connection factory, etc. The
trust certs were imported, the EJB refs were added. It appears that
the connection was made. But I receive an exception when
publishing: javax.naming.NameNotFoundException.

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.newNameNotF oundException(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(Basi cNamingNode.java:
206)
at weblogic.jndi.internal.BasicNamingNode.lookup(Basi cNamingNode.java:
214)
at weblogic.jndi.internal.BasicNamingNode.lookup(Basi cNamingNode.java:
214)
at weblogic.jndi.internal.BasicNamingNode.lookup(Basi cNamingNode.java:
214)
at
weblogic.jndi.internal.WLEventContextImpl.lookup(W LEventContextImpl.java:
269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLCont extImpl.java:
362)
at
weblogic.jms.frontend.FEConnection.createDestinati on(FEConnection.java:
841)