Incorrect behavior: transactional Sessions in EJB methods

SourceForge Submitter: swaldman .
If a QueueSession is created in a business method of an EJB
with the transacted argument of createQueueSession() set to
true, JBoss fails to send the message unless the user
explicitly calls commit() on the session.

This is incorrect – users should be forbidden from calling
commit() or rollback(), as jboss is responsible for
transaction management.

According to Sun (see e.g. JMS tutorial, http://java.sun.com/
products/jms/tutorial/1_3_1-fcs/doc/jmsj2ee.html#1029338)
the transacted argument should be ignored in an EJB
context. My beans usually set it to true, only to document
that message send is intended to be included in the method's
transaction. These JMS beans break in jboss.