I'm already working on it, but there is a reason why the existing JMS session is used. The problem with starting a new JMS session is, in case the message is already there when you open the listener, it will be delivered immediately. The thread that opened the listener may not have committed yet, so its changes are not visible from the thread where the message is delivered. When you use the same session, JMS will not deliver another message until the current one has been acknowledged.
This model proved problematic when I tried to implement timers, because the thread that delivers the alarm is not managed by JMS and results in similar misbehavior. I'm changing things to rely on database locking rather than JMS ordered delivery. I will also cover the message events case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923641#3923641 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923641 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
