Thanks for the pointer. Looking at the test suite code come with the jboss-3.2.2 source, most of the test is looking up ConnectionFactory through localhost rather than through remote server. They didn't help in my case. Further look at the code of org.jboss.mq.server.JMSDestinationManager seems like that even client code lookup connection and queue successfully, when create QueueReciever, the JMSDestinationManager is looking for the local queue instead of remote queue from "destinations" map.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838732#3838732 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3838732 ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
