• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

JNDI Lookup Exception

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I am trying to perform a JNDI lookup in order to obtain a reference to a J2C connection factory & keep getting the following exception:

Caught exception:Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object.

What I don't understand is that I'm able to obtain a reference to my activation spec & Destination objects without any issue. I'm calling into WebSphere 6.1 via an external app.

Any ideas as to why this is occuring?

Lookup code:


Main code:


Output:
Object returned: class com.stc.jms.client.STCQueue
Object returned: class com.ibm.ejs.j2c.ActivationSpecBindingInfo
Caught exception:Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object.


============================================================================
Name Space Dump
Provider URL: corbaloc:iiop:localhost:2810
Context factory: com.ibm.websphere.naming.WsnInitialContextFactory
Requested root context: cell
Starting context: (top)=LocalNode02Cell
Formatting rules: jndi
Time of dump: Mon Jun 11 09:57:46 EDT 2007
============================================================================

============================================================================
Beginning of Name Space Dump
============================================================================
1 (top)
2 (top)/nodes javax.naming.Context
3 (top)/nodes/LocalNode02 javax.naming.Context
4 (top)/nodes/LocalNode02/domain javax.naming.Context
4 Linked to context: LocalNode02Cell
5 (top)/nodes/LocalNode02/persistent javax.naming.Context
6 (top)/nodes/LocalNode02/servers javax.naming.Context
7 (top)/nodes/LocalNode02/servers/server1 javax.naming.Context
8 (top)/nodes/LocalNode02/servers/server1/jms javax.naming.Context
9 (top)/nodes/LocalNode02/servers/server1/jms/MyActivationSpecRef
9 com.ibm.ejs.j2c.ActivationSpecBindingInfo
10 (top)/nodes/LocalNode02/servers/server1/jms/MyConnectionFactoryRef
10 javax.jms.QueueConnectionFactory
11 (top)/nodes/LocalNode02/servers/server1/jms/MyDestinationRef
11 com.stc.jms.client.STCQueue

...
...

Cheers!
Sean.
 
Sean Norman
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
After examining the stack trace, here is the root of the issue:

com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.NoClassDefFoundError: Invalid Implementation Key, com.ibm.ws.transaction.NonRecovWSTxManager]
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(CNContextImpl.java:1947)
...
...
...

Looks like I'm missing "com.ibm.ws.transaction.NonRecovWSTxManager"
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic