It may be obvious but if you can, write a little code that iterates over the naming enumeration of your initial context, and print out what content it has, if any. This might give you a better idea of which naming service you are actaully connected to.
You could compare this with the JNDIView list you get from the JMX console - if the two differ then you are not connecting to the JNDI tree you thought you were connecting to. This doesn't solve your problem, of course, but it might make things a bit clearer. If you can iterate to the adapter but can't look it up directly this would probably mean a spelling mistake in the JNDI name, for example. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880620#3880620 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880620 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
