7 Replies Latest reply: Mar 28, 2014 10:25 AM by Justin Bertram RSS

hornetq-2.2.14.Final with jboss-5.1.0.GA?

Prasanna kumar Newbie

I need clarification for one thing.

I have jboss-5.1.0.GA and i want to upgrade my hornetq to hornetq-2.2.14.Final.

Is this possible to use hornetq-2.2.14.Final with jboss-5.1.0.GA?

or

Is this possible to use hornetq-2.2.5.Final with jboss-5.1.0.GA?

  • 1. Re: hornetq-2.2.14.Final with jboss-5.1.0.GA?
    spyhunter99 Novice

    Considering that you've also posted about another issue with 5.1.0GA, could you let me on the secret?

     

    I just downloaded and applied it to a clean 5.1.0GA and ran into this

    21:35:00,432 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/C:/jboss-5.1.0.GA/server/default-with-hornetq/deploy/hornetq.sar/ state=PreReal mode=Ma

    nual requiredState=Real

    org.jboss.deployers.spi.DeploymentException: Error deploying: vfsfile:/C:/jboss-5.1.0.GA/server/default-with-hornetq/deploy/hornetq.sar/hornetq-jboss-beans.xml

            at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)

            at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:136)

            at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125)

            at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.internalDeploy(AbstractRealDeployerWithInput.java:102)

            at org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:78)

            at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)

            at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)

            at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)

            at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)

            at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)

            at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)

            at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

            at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

            at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

            at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

            at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

            at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

            at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

            at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)

            at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)

            at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)

            at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)

            at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

            at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)

            at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

            at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)

            at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)

            at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

            at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)

            at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)

            at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)

            at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)

            at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)

            at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

            at org.jboss.Main.boot(Main.java:221)

            at org.jboss.Main$1.run(Main.java:556)

            at java.lang.Thread.run(Thread.java:662)

    Caused by: java.lang.IllegalArgumentException: Exception loading class for ScopeKey addition.

            at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:67)

            at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)

            ... 35 more

    Caused by: java.lang.ClassNotFoundException: org.hornetq.jms.server.recovery.AS5RecoveryRegistry from BaseClassLoader@1ebbdb4{VFSClassLoaderPolicy@1f37775{name=

    vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/hornetq.sar/ domain=ClassLoaderDomain@873723{name=DefaultDomain parentPolicy=BEFORE parent=org.jboss.bootstrap.

    NoAnnotationURLClassLoader@133796} roots=[MemoryContextHandler@19382021[path= context=vfsmemory://441bp1k-d7f405-h2v5i9ap-1-h2v5iupz-10 real=vfsmemory://441bp1k

    -d7f405-h2v5i9ap-1-h2v5iupz-10], FileHandler@7211747[path=hornetq.sar context=file:/C:/jboss-5.1.0.GA/server/default-with-hornetq/deploy/ real=file:/C:/jboss-5.1.0.GA/server

    /default-with-hornetq/deploy/hornetq.sar/]]  delegates=null exported=[] <IMPORT-ALL>NON_EMPTY}}

            at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:448)

            at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

            at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:63)

            ... 36 more

  • 2. Re: hornetq-2.2.14.Final with jboss-5.1.0.GA?
    srinivaas venkat Novice

    Hi, I do have the very same issue with Hornetq2.2.14 and Jboss 5.1.0 GA. Can i use 2.2.14 with Jboss 5.1.0 or should i upgrade to JBoss 6 or JBoss 7?

     

    Also what is the latest hornetq version that can be used with Jboss 5.1.0 GA. Pls help.

     

    Thanks

    Srinivaas

  • 3. Re: hornetq-2.2.14.Final with jboss-5.1.0.GA?
    Yong Hao Gao Master

    I'd suggest you use JBoss 7. HQ 2.2.14 may not work with 5.1.0 GA as other guys tried. It should work with later versions of JBoss 5 like 5.1.2. But I don't think it is available in community download anymore, only EAP.

    If you use JBoss 5.1.0.GA, I'm not sure which is the latest support version. HornetQ is more targeted at integration with JBoss AS7 (as well as being a standalone messaging server).

  • 4. Re: hornetq-2.2.14.Final with jboss-5.1.0.GA?
    srinivaas venkat Novice

    Thanks, JBoss AS 7.1 looks definitely better and can see the response messages from mdb routed to any of the available node in cluster. Thanks for the suggestion.

  • 5. Re: hornetq-2.2.14.Final with jboss-5.1.0.GA?
    Prasanna kumar Newbie

    Hi Yong,

    Thanks for the reply. I will use JBoss AS 7.1.

     

    Thanks,

    Prasanna

  • 6. Re: hornetq-2.2.14.Final with jboss-5.1.0.GA?
    Arul Mozhi Newbie

    From your reply its a bug in Hornetq2.2.14 and Jboss 5.1.0 GA.Is this a known issue ?.

  • 7. Re: hornetq-2.2.14.Final with jboss-5.1.0.GA?
    Justin Bertram Master

    The issue is more like JBoss AS 5.x is extremely old at this point and we don't have the time and manpower to support integration with JBoss AS 5, 6, 7, and WildFly (not to mention JBoss AS 4).