wood burning stoves 2.0*
The moose likes EJB and other Java EE Technologies and the fly likes JMS and Websphere Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "JMS and Websphere" Watch "JMS and Websphere" New topic
Author

JMS and Websphere

Bjarne Soegaard
Greenhorn

Joined: Oct 15, 2002
Posts: 3
I get a strange Exception when looking up a QueueConnectionFactory from an EJB in Websphere.
I have added the factory to Websphere namespace using the administration console (web).
Also put it in the deployment descriptor.
What have I done wrong???
W NMSV0605E: A Reference object looked up from the context "domainRoots/UnspecifiedDomainName/legacyRoot" with the name "MyQueueConnectionFactory" was sent to the JNDI Naming Manager and an exception resulted.
Reference data follows:
Reference Factory Class Name: progress.message.jclient.AdministeredObjectFactory
Reference Factory Class Location URLs: <null>
Reference Class Name: progress.message.jclient.QueueConnectionFactory
Type: brokerURL
Content: localhost
Type: connectID
Content: ""
Type: defaultUserName
Content:
Type: defaultPassword
Content:
Type: clientID
Content: ""
Type: versionID
Content: 3.5.1
Type: randomizeBrokers
Content: false
Type: loadBalancing
Content: false
Exception data follows:
java.lang.ExceptionInInitializerError: java.lang.ClassCastException: progress.message.zclient.prBundle
at progress.message.zclient.prAccessor.getResource(Unknown Source)
at progress.message.zclient.prAccessor.getString(Unknown Source)
at progress.message.zclient.SessionConfig.<clinit>(Unknown Source)
at progress.message.jclient.BrokerName.BX_(Unknown Source)
at progress.message.jclient.BrokerName.<init>(Unknown Source)
at progress.message.jclient.QueueConnectionFactory.<init>(Unknown Source)
at progress.message.jclient.AdministeredObjectFactory.vJ_(Unknown Source)
at progress.message.jclient.AdministeredObjectFactory.getObjectInstance(Unknown Source)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:782)
at com.ibm.ejs.ns.jndi.CNContextImpl.processResolveResults(CNContextImpl.java:1599)
at com.ibm.ejs.ns.jndi.CNContextImpl.doLookup(CNContextImpl.java:1475)
at com.ibm.ejs.ns.jndi.CNContextImpl.lookup(CNContextImpl.java:1129)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:128)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:193)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
at com.ibm.ws.naming.urlbase.UrlContextHelper.isReference(UrlContextHelper.java:119)
at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:248)
at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1185)
at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1162)
at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1214)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:193)
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
at com.ibm.ws.naming.urlbase.UrlContextHelper.isReference(UrlContextHelper.java:119)
at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:240)
at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1185)
at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1162)
at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1214)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at dk.bdata.basis.server.MessageSenderServerSide.createConnection(MessageSenderServerSide.java:73)
at dk.bdata.basis.server.MessageSenderServerSide.sendTextMessage(MessageSenderServerSide.java:109)
at dk.bdata.henvendelse.server.HenvendelseServerSide.findByID(HenvendelseServerSide.java:894)
at dk.bdata.henvendelse.server.HenvendelseSession.findByID(HenvendelseSession.java:103)
at dk.bdata.henvendelse.server.EJSRemoteStatelessHenvendelseSessionRemote.findByID(EJSRemoteStatelessHenvendelseSessionRemote.java:79)
at dk.bdata.henvendelse.server._EJSRemoteStatelessHenvendelseSessionRemote_Tie._invoke(_EJSRemoteStatelessHenvendelseSessionRemote_Tie.java:151)
at com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(ExtendedServerDelegate.java:515)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:2377)
at com.ibm.CORBA.iiop.OrbWorker.run(OrbWorker.java:186)
at com.ibm.ejs.oa.pool.ThreadPool$PooledWorker.run(ThreadPool.java:104)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:137)
Michael Zalewski
Ranch Hand

Joined: Apr 23, 2002
Posts: 168
Is it a message bean?
EJB 2.0 is not supported in WebSphere (not until Websphere 5.0)
Dave Coombes
Greenhorn

Joined: Nov 06, 2001
Posts: 19
Assuming you are using MQSeries as the JMS provider have you got the JMS jars (mq.jar, mqjms.jar, providerutil.jar) on the nodes classpath?
 
jQuery in Action, 2nd edition
 
subject: JMS and Websphere
 
Similar Threads
NameNotFoundException
Problem connecting to EJB using Remote Client
problem with DB2 connection in a stateful session bean and deployed by Websphere
jdbc/jdbc/WebSphere Commerce DB2 DataSource
WSAD 5.0 JMS Problem