Trouble Installing HornetQ (2.3.0 Final) into JBoss 5.1

[andyjc]

Hi All,

Simple question, I hope.

I'm trying to follow the installation instructions here and runnning into trouble with the step of running ./build.sh from the config/jboss-as-5 directory.  The issue is that the child script ../../bin/build.sh doesn't seem to exist.  Is there a step I'm missing here?

Thanks,

Andy

[ataylor]

2.3.0.final is developed for AS7, you should upgrade your AS

[redboul]

Hi All,

I am trying to  set up a Jboss 5.1 sending messages via JCA to a standalone HornetQ 2.3.0 (with the user-guide) but encountering many problmes:

• class not found error (HornetQException for instance which are not in hornetq-jms-client.jar nor hornetq-core-client.jar nor hornetq-ra.jar but in hornetq-commons.jar which is not said to be added to Jboss lib)
• adding HornetQException class into hornetq-core-client.jar result in missing BasicLogger class
• adding jboss-mc.jar into hornetq-ra.rar folder solved the later but added a java.lang.NoSuchMethodError: org.jboss.logging.Logger.getMessageLogger(Ljava/lang/Class;Ljava/lang/String;)Ljava/lang/Object; since jboss 5.1 logger are different from the one used in HornetQ

I was hoping that the rar classloader would only use the class from the rar folder but it seems it does not...

I finally successfuly installed the  Resource Adapter using Hornetq 2.2.14.Final jars version but I am encoutering some issues that may be fixed with 2.3.0.Finale.

With Andy's post, should I understand that HornetQ 2.3.0.Final does not work with Jboss 5.1 (even in standalone)?

Thanks

[clebert.suconic]

you will need to add the jboss logger used on jboss7 / wildfly on the jar lib as well

[redboul]

Hi Clebert,

Thanks for your answer.

I already did add the jboss logging jar (in the rar foler or in the lib folder) but jboss is still using the  jboss5 one since class names/packages are the same but with different signatures.

Do you mean remove the jboss logging of jboss 5 and replace it with the ones of jboss7? If so, I will encouter the same issues on jboss deployment instead of hornetq deployment.

Regards,