Dear All, I am finding when I set up a Queue much like the example at...
http://trailblazer.demo.jboss.com/EJB3Trail/serviceobjects/mdb/ ...JBoss instantiates several (I'm guessing around 5) consumers that all hungrily grab whatever appears on the Queue in a concurrent fashion. Also, if any of the message processing fails, they retry several (I'm guessing around 10) times before assigning the message to the DLQ. My question is: how can I control this behaviour? My requirement is for a sequential, single-threaded point-to-point, so all I want is one consumer that processes each message just once. If the message fails to consume then so be it: as long as it reached the consumer I'm happy. I have tried setting the ActivationConfigProperties maxSessions to 1, DLQMaxResent to 1, and transacted to false, as listed at... http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigJMSMessageListener ...but they all seem to have little effect? You help is most appreciated, Richard. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3932715#3932715 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3932715 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
