HornetQ 2.3.0.Final uses JBoss Logging 3.1.0.GA (as you can see here). Unfortunately I don't believe there is any way to resolve this problem since the logging libraries conflict and I don't believe there is any way to isolate the classloader of a JCA RA. This is one of the reasons that we dropped support for JBoss AS 4.x and 5.x. However, you have a few different options if you can't move to a newer release of JBoss AS or Wildfly:
- Use a JMS bridge.
- Use an older version of the HornetQ JCA RA that doesn't use the newer version of JBoss Logging.
Thanks for the suggestions!