Its taken me a while to get back to this test and try your recommendations. I
agree that the test code was not conserving resources the way it was written,
but I did not give thought to the fact that the session and publisher was being
created in a transaction and the publish was created in another transaction. I
have re-arranged to java code within the bean and now derive the expected
results; the JMS publish now gets rolled back with the JDBC/TX rollback.
| ejbCreate() {
| //just lookup TopicConnectionFactory and Topic
|
| business method() {
| //cFactory.createConnection()
| //connection.createSession()
| //session.createPublisher()
| //session.createMessage()
| //publisher.publish(msg)
| //call entity bean which sets rollbackOnly
| //close publisherm session, and connection
|
The setting of Shared versus Unshared in the resource-ref had no noticeable
impact on the transaction behavior. Although your comments there may have been
targeted towards conserving resources.
Thanks for the sanity check.
jim
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876379#3876379
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876379
-------------------------------------------------------
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
