This content has been marked as final. Show 1 reply
Deleting and recreating the foreign server produced something of a useful result (the connectionfactory and destination now appear in the jndi tree). However I am now left with the following errors
weblogic.jndi.factories.java.ReadOnlyContextWrapper cannot be cast to javax.jms.Queue
LMBConnector.java connect 68 jmsconnect.LMBConnector
LMBConnector.java conn 47 jmsconnect.LMBConnector
LMBGradesHandler.java pushToLMB 32 lmbwebservice.LMBGradesHandler
LMBGradeResource.java doPost 39 lmbwebservice.LMBGradeResource
NativeMethodAccessorImpl.java invoke0 -2 sun.reflect.NativeMethodAccessorImpl
NativeMethodAccessorImpl.java invoke 39 sun.reflect.NativeMethodAccessorImpl
DelegatingMethodAccessorImpl.java invoke 25 sun.reflect.DelegatingMethodAccessorImpl
Method.java invoke 597 java.lang.reflect.Method
and from the server
There was an error while making the initial connection to the JMS resource named jms/LMBQCF from within an EJB or a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [JMSPool:169818]The JMS connection pool named "jms/LMBQCF" has a configured connection factory JNDI name of "jms/LMBQCF". However, an object that is not a javax.jms.ConnectionFactory is bound to that JNDI name. The object bound to that JNDI name has type "weblogic.jndi.remote.DirContextWrapper_1034_WLStub".
I`m not really sure how to work around this as it appears to be the weblogic wrappers that are giving me grief.