[asterisk]

I now have migrated from JBoss messaging to HornetQ 2.0.0 GA and can confirm that this fixes my problem. So the problem mentioned in this thread is caused by the bug in JBoss messaging.

The question now is whether this bug already has a ticket and whether it will be fixed in the 5.x JBoss series. Does anybody know that?

Thanks a lot!

[jaikiran]

Kay Hannay wrote:

The question now is whether this bug already has a ticket

I couldn't find any.

Kay Hannay wrote:

whether it will be fixed in the 5.x JBoss series. Does anybody know that?

There won't be any more 5.x community version releases. So no it won't be fixed for JBoss AS5 community editions. You'll have to use the JBoss AS6 latest (6.0.0.M5 version at the moment) version. JBoss AS6 by default ships with HornetQ.

[waterzhang]

Hi,has it been solved in jboss-messaging1.4x?I also have troubled this problem in our company's project when upgrade from jboss4 to jboss5.