The link below discusses (briefly) how to configure HornetQ to work with JBoss 4.X:
We are using JBoss 4.0.4.GA on OpenSuSE 10.2 with EJB2.1 (yes - that's all very dated now, I am only too aware of that, but please don't reply with unhelpful suggestions to upgrade. We are on the versions we are on).
The documentation states that HornetQ can be used in JBoss 4.X. No minimum value for X is specified. I mention this because there was one other post that said 4.2 was the minimum version. According to the documentation that is not the case.
There are two vital things that I expected to find in the documentation of how to get HornetQ working in JBoss4:
(1) I checked what the differences were between the default configuration and the default-with-hornetq configuration. There are of course new files in the default-with-hornetq folder, but the only file change is to login-config.xml. So when I start JBoss, how does it know to start using HornetQ as the JMS provider rather than JBossMQ?
(2) ith JBossMQ, I defined my destinations in deploy/jms/xxx-jms-service.xml files - how do I migrate those to HornetQ?
When starting the default-with-hornetq configuration, it is throwing a few errors on startup.
(1) 11:14:50,581 WARN [ServiceController] Problem starting service org.hornetq:service=HornetQJMSStarterService java.lang.NoSuchMethodError: org.apache.log4j.Logger.isTraceEnabled()
I replaced the log4j.jar in server/default-with-hornetq/lib with log4j-1.2.17.jar, but still get the same error.
(2) If I drop into deploy my mdb.jar, I get this error:
10:46:23,715 WARN [JMSContainerInvoker] JMS provider failure detected for Message1Bean
javax.naming.NameNotFoundException: XAConnectionFactory not bound
even though my jar file does not make any mention of XAConnectionFactory.
I have commented out keepAlive,reconnetInterval, and DLQHandler from conf/standardjboss.xml as instructed here:
I am therefore not too sure what it is about my jar that is causing this error.
(3) 2013-03-20 18:32:53,012 ERROR [STDERR] Mar 20, 2013 6:32:53 PM org.hornetq.core.logging.impl.JULLogDelegate warn
WARNING: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
I have been unable to install libaio, but it would appear from the error message that this will not be a fatal problem.
Any helpful answers gratefully appreciated.