Register / Login
Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
this forum made possible by our volunteer staff, including ...
Stephan van Hulst
Error: Unable to lookup JMS resources, JNDI lookup exception: null
posted 14 years ago
I have installed WebSphere Application Server 18.104.22.168 on Windows XP. I have also installed WebSphere MQ. Whenever I attempt to start my application server, this error shows up in my SystemOut log.
c85dfdf MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: <null>
[1/28/05 10:42:44:252 EST] c85dfdf MDBListenerIm W WMSG0019E: Unable to start MDB Listener DataImportMDB, JMSDestination queue/DataImportMDB : javax.naming.NameNotFoundException: QueueConnectionFactory. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound
And this error repeats for all of the MDBs that I have. I am VERY new to WebSphere, and would appreciate any assistance.
There’s no place like 127.0.0.1. But I'll always remember this tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
Boost this thread!
WAS 5 and Windows XP?
JMS ---- URGENT !!!!
Unable to lookup JMS resources NotFound in WAS
Message Listeners in WAS 5.0
Exception in JMS due to Configuration.