I have an application that I'm porting from Websphere 5.0 to JBoss 3.2.3 and one of the requirements is for rolled back messages to be redelivered "forever", until the transaction can be commited. Sounds like a bad idea, but the application is designed to work this way (and it works fine). The problem is that when the message is rolled back, jboss tries to redeliver it instantly and this causes 100% cpu load when it's rolled back multiple times. WebsphereMQ seems to wait for some time before trying to redeliver it, and that would be preferable in jboss as well.
Is there some setting for this or do I have to resolve to something like Thread.sleep()? I tried to increase the ReconnectIntervalSec in the invoker-proxy-binding for message driven beans in standardjboss.xml, but that didn't help. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3836232#3836232 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3836232 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
