As much as I would like his help, and believe me, I do want Adrian's help, I think WE developers have a legitimate point.
Perhaps the debug code is showing an error. Then we are rightfully point it out. My question is EXTREMELY legitimate. I am asking, is that exception part of the closing logic, or is it an error? I think that if it was truly an expected exception, it would be handled properly, with a debug stating that exception was expected. THAT makes more sense to me. I did read that post. It states that us developers are laughable because we don't understand the severity levels in the log4j output. Now, I don't want to brag, I am sure the JBoss folks are higher caliber developers than I am. But seriously, spitting out exception messages would be alarming to anybody. If I am architechting a business solution on JBoss JMS, first I build a proof of concept. If THAT point fails, which this exception seems to indicate, then I need to find an alternative. I don't want an alternative though ;) I want JBoss to work properly. I am simply asking, IS THIS THE EXPECTED behaviour? Thank you again. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876821#3876821 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876821 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
