Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JNDI lookup, First component in name xx not found

 
Sammy Kanan
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've got a MDB which publishes to a TCF configured using embedded messaging. When my MDB attempts to publish, it appears to connect to the TCF but then things get a bit nasty I get the following exception.
[ExtraInfo - null]; nested exception is: javax.naming.NameNotFoundException: Con
text: sakana/nodes/sakana/servers/server1, name: jms/iaTradetoAltioDestination:
First component in name iaTradetoAltioDestination not found. [Root exception is
org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingCon
text/NotFound:1.0]
javax.naming.NameNotFoundException: Context: sakana/nodes/sakana/servers/server1
, name: jms/iaTradetoAltioDestination: First component in name iaTradetoAltioDes
tination not found. Root exception is org.omg.CosNaming.NamingContextPackage.No
tFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_in
fo(WsnOptimizedNamingImpl.java:968)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete
_info(WsnOptimizedNamingImplBase.java:1398)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(U
nknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java
:3491)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1
Any help is greatly appreciated
 
Sammy Kanan
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What a typo, using infinite wisdom the JNDI name was in fact wrong. Problem sorted.
 
Michael Morris
Ranch Hand
Posts: 3451
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to JavaRanch Sammy. Glad we could help.
 
gmansoor
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What was the problem? I am getting exact same error and couldn't figure out yet.
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In this situation, the name for the JNDI lookup was wrong.

There are a number of things that need to be configured for JMS messaging to work with the embedded WebShpere messaging engine. You really have to check and double-check the configuration of topics, queues and destinations.

I actually put together a little tutorial on WebSphere JMS configurations. It can help verify the steps needed to get JMS working:

configuring WebSphere JMS and MDB EJBs

Good luck.

-Cameron McKenzie
 
bradley winter
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Please DELETE this worthless thread! There's nothing of use in the thread. All it has done is waste my time - The DEAD link at the end was really helpful guys.
 
bradley winter
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I didn't mean to sound so ungrateful for the forum. But, when key words and phrases lead to threads that say nothing (or links are dead) it is very frustrating to people who are looking for real answers.
 
Paul Clapham
Sheriff
Posts: 21107
32
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Didn't you notice that the last post was made 5 years ago? It shouldn't be surprising to find that a link that old is dead. That's just a fact of life on the Web.

And I'm sure you didn't mean to suggest that we should continually review links posted by our members for validity, did you?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic