This content has been marked as final. Show 2 replies
From what you described, I have got the impression that you are running an application (say the scheduler) on WebLogic server to send messages to a 3rd party JMS provider. The exception tells me that your connection is established to the WebLogic JMS server while you are supposed to connect to the foreign provider. Are you using WebLogic foreign JMS server configuration to map the 3rd party resources into the WebLogic JNDI tree? If so can you post your foreign JMS server configuration for the connection factories and destinations?
Especially you need to check if the local jndi name of the connection factory in the Foreign JMS Server is the same as the jndi name of any of the regular connection factories including the default connection factories on the WebLogic servers.