I changed my session to transacted=true (and the printed debug stated this was the case). However, it worked the same as the transacted=false case.
According to what I've read and experienced with WebLogic JMS, transacted=true means to use JMS internal transactions (thus use commit()/rollback() on the session) and transacted=false to either not use transactions at all (for external clients) or join the current JTA transaction (for j2ee container-based clients or clients using UserTransactions). I am also familiar with J2EE 1.3 making it a requirement for all JMS transactions to be JTA-based within the container. That meant, with WebLogic, that all connection factories looked up through a resource-ref refused to do anything but honor a JTS transaction. I'm somewhat new to JBoss and am trying to get these more sophisticated scenarios tested,. I've boiled this down to a very simple test case and it fails the most basic publish/rollback case. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3857411#3857411 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857411 ------------------------------------------------------- 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://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
