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
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:
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.