aspose file tools*
The moose likes Websphere and the fly likes Wepsphere 6.0 JNDI issue Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Wepsphere 6.0 JNDI issue" Watch "Wepsphere 6.0 JNDI issue" New topic
Author

Wepsphere 6.0 JNDI issue

Vedavalli Radhika
Greenhorn

Joined: Feb 20, 2007
Posts: 7
I am running WAS 6.0 from a AIX box. I have some message-driven enterprise bean in my application which needs an activation specification JNDI name.As i have checked "set default bindings", it has automatically generated the JNDI name as eis/GGG by looking up the specific ejb xml.
My application fails to start when I try to start from Applications > Enterprise Applications > Check my application name and click start.

When I check with the logs it shows the following message

[2/20/07 10:07:50:118 GMT+00:00] 00000039 RALifeCycleMa E J2CA0052E: The lookup of the ActivationSpec with JNDI Name eis/GFSAGG failed due to exception javax.naming.NameNotFoundException: Context: MyNodeNode01Cell/nodes/MyNodeNode01/servers/server1, name: eis/GFSAGG: First component in name GFSAGG not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info(WsnOptimizedNamingImpl.java:969)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:1435)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4045)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1776)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1737)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1444)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1324)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
....................................................................
....................................................................


Caused by: javax.naming.NameNotFoundException: Context: MyNodeNode01Cell/nodes/MyNodeNode01/servers/server1, name: eis/GFSAGG: First component in name GFSAGG not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0]
at com.ibm.ws.naming.jndicos.CNContextImpl.processNotFoundException(CNContextImpl.java:4394)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1784)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1737)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1444)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1324)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at com.ibm.ejs.j2c.RALifeCycleManagerImpl.activateEndpoint(RALifeCycleManagerImpl.java:1248)
... 54 more

Also I don't see any UTC to work with?? Where should I exactly look for starting my UTC??

Can anyone help??

I also referred to the topic http://www.coderanch.com/t/317047/EJB-JEE/java/WebSphere-jndi .But could not derive much help.

Thanks,
Radhika.
Hanumanth Kanthi
Ranch Hand

Joined: May 27, 2004
Posts: 74
I am confused!!

It seems your ejb-jar.xml saying "eis/GGG" but trace is complaining about not finding "eis/GFSAGG".

What are we missing here???

Most likely a wrong configuration of your activation spec.

Run dumpNameSpace.bat from your WAS_HOME/bin folder and see if it lists your interested JNDI name correctly......if yes but in a different name pattern then make appropriate corrections to match the pattern in your configuration and then give it a try......

What version of WebSphere you are running? You might wanted to apply latest fixpacks to get to the latest level.

If you are running in RAD then you should be able to launch UTC from test server context menu...... you can also try <a href="http://<hostName rel="nofollow">:9080/UTC" target="_blank">http://<hostName>:9080/UTC

Cheers,
H. Kanthi
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Wepsphere 6.0 JNDI issue