"b.eckenfels" wrote :
https://jira.jboss.org/jira/browse/JBAS-6412
Adrian provided us with a Fix for 4.2.3 and this also applies to 4.0.5. Our first tests
shows, that the specific condition is solved (in both versions). We now let this run on
customer system and see if the problem is completely fixed, or if the messages get stuck
at other conditions as well.
In parallel we are testing JBM with the same fault injection method in order to determine
if it is really more reliable. We plan to switch to JBM only with 5.0 (and that will take
us a few more month to finish the migration and tests).
I will keep you updated, Clebert in case we see something similiar with JBM.
Thanks to the JBoss Developers who made that fix possible so quickly (once we found the
reason).
Gruss
Bernd
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204786#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...