Thank you for our answers. jaikiran were absolutely right - the bean used Container managed transaction. I added a:
@TransactionManagement( value=TransactionManagementType.BEAN) annotation and now it works as a charm, concurrently processing and sending messages. The "normal" use case of the JMS-based system wouldn't be handling of massive amounts of messages, I'm just using the framework to import and process large amounts of legacy data, but I'll make sure to optimize the connection management. The while-loop is actually just a JDBC resultset iteration. As I wrote, using JMS for this particular purpose isn't strictly necessary - but a convenient way to stress-test the JMS and validate the business logic with large amounts of data. Well, now I'm starting to rant away. Thanks again for your answers! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3950592#3950592 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3950592 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
