I found the problem. The MDB described above can reply to messages whose replyTo field is set. To get the connection factory to create a connection to that replyTo destination, it does a new InitialContext() in the MDB. This worked in non-clustered environments, but as I pointed out, not in a JBoss clustered environment.
One of the MDB responds with that JNDI error because the InitialContext returned has no clue about the HAJNDI connection factory. To fix this, of course, you need to use the Context set in the MDB's setMessageDrivenContext() method. Question: shouldn't a new InitialContext() from an MDB return the same context as the one set on the MDB's setMessageDrivenContext() method? Thanks, Reggie View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884881#3884881 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884881 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
