"f2racer" wrote : BTW, after the exception occurs on the connect, it looks like it 
continues to process message as soon as a connection is freed...  In fact, it doesn't 
actually miss any of the messages even though the code creates an exception in the 
code that sends the messages...
  | 

Oops, I meant if I'm using ConnectionFactory (the JMSException), if I use QueueFactory 
the code stops at the NamingException.

<a 
href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3824980#3824980";>View 
the original post</a>

<a 
href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3824980>Reply 
to the post</a>


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to