Any update ???
For the 10,000th time. JNDI configration is not a subject for this forum.
That includes looking up JMS objects in JNDI.
Now if you show me the problem is that the JMS objects are not being bound
into JNDI then I'll tell you to read the FAQ.
Would you suggest which FAQ we should read?
If you have a look at http://localhost:8080/jmx-console/ you will find an MBean called 'JNDI View' which has a list method you can invoke to show you what is bound to JNDI.
This should be checked first to see if the expected item is bound, anyone that posts a question with a 'javax.naming.NameNotFoundException' has obviously not checked this.
If an item you expect to be bound can not be found this is most likely to be caused by a deployment problem when the item you expect to be bound was deployed.
There should be an error in the log to say what happened during deployment, this is the place to start when trying to track down the answer.
The FAQ's either at the start of this forum or in the WIKI will contain information on comman deployment failures for JBoss MQ.
To give you a head start - The most common cause of this problem is that the user configuring JBoss has screwed up the persistence configuration for JMS.