Well, I found my own solution. First, I didn't have TRACE logging enabled correctly; all I was getting was DEBUG. In addition to adding the category tags for org.jboss.mq, etc. in the log4j.xml (as noted in the FAQ) I also had to comment out the Threshold tag in my file appender section (setting it to TRACE didn't work...I obviously don't really grok log4j.). Now I could see the exceptions.
During the topicConnection.close() method JBoss was trying to delete the temporary topics. But, trying to be a good citizen, I had already deleted them myself after each send/receive, and so it was throwing an exception because there were no destinations for it to delete. This seemed a little odd to me because, a) my deletes didn't fail so I would assume JBoss would recognize that they are gone, and b) the exceptions were completely hidden by the warnings -- they were only visible with trace logging on! Not sure how useful that is, but I guess the important part was that something was deleting the topics, so the warnings were just that. Anyway, I simply commented out my deletes, letting JBoss take care of it, and now all is well. No more warnings. Frankly, I suspect that I am misusing JMS here, anyway (using asynchronous messaging for a synchronous purpose) and so will be looking into switching this out for JMX remoting or straight RMI sometime in the future. Still, it works for now. Cheers! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866725#3866725 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866725 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
