I'm seeing the same error, anyone out there know of other solutions?
Try org.jboss.as.integration.hornetq.recovery.AS5RecoveryRegistry. I know this class comes with JBoss EAP, but I do not believe it is in the community version of JBoss AS. You will notice that the branch name says "EAP_GA_BUILD2" which indicates it is for JBoss EAP. If you deploy EAP builds into the community AS you will get weird stuff like this because EAP and the community bits have diverged.
It is potentially harmful not to have this configured because it means you won't have automated recovery for any XA transactions involving a HornetQ resource.
At the end of the day, you should plan on moving to a more recent version of JBoss AS (like version 7) since we're likely to phase out support for older versions of JBoss AS.
For the EAP that file comes from the EAP Branch I think.
Thanks Justin, using the class you mentioned seems to resolve the error. I'd love to use the latest JBoss, but have had too many issues getting our apps working under it - third party stuff - i'll save that for another thread.
Can you clarify your statement. Can a JBoss 5,1 Community Edition server be upgraded from hornetq 2.2.5.GA to 2.2.14.Final?
* You state on one hand that the class can be found within a EAP branch -- but then state it will have issues if deployed to a Community Edition server. That tells me we are toast on this front until we update to JBoss 7 -- right?
* There is no equivalent setting in 2.2.5.GA hornetq-jboss-mbeans.xml. Does that mean we don't have automatic XA recovery in 2.2.5.GA as well and will be no worse if we did the same with 2.2.14.Final?
I just had this issue myself with JBoss AS 5.1.0.GA, the community version. I think what Justin proposed is to change:
<bean name="AS5RecoveryRegistry" class="org.hornetq.jms.server.recovery.AS5RecoveryRegistry">
<bean name="AS5RecoveryRegistry" class="org.jboss.as.integration.hornetq.recovery.AS5RecoveryRegistry">
BTW, changing to org.jboss.as.integration.hornetq.recovery.AS5RecoveryRegistry didn't resolve the issue for me.