8 Replies Latest reply on Oct 1, 2012 10:56 AM by peter craddock

    How can I update as 7.1.1 to use the latest hornetq build ?

    peter craddock Novice

      I have tried adding the jars from the build into the hornetq module and altering the module.xml but I get an error on startup

        • 1. Re: How can I update as 7.1.1 to use the latest hornetq build ?
          Andy Taylor Master

          Im not sure you will be able to, there are integration changes between the versions.

           

          what error are you getting?

          • 2. Re: How can I update as 7.1.1 to use the latest hornetq build ?
            peter craddock Novice

            During our tests we get a JMS exception

             

            1. javax.naming.NamingException: Failed to lookup [Root exception is java.io.NotSerializableException: org.hornetq.api.core.client.loadbalance.RoundRobinConnectionLoadBalancingPolicy]

            at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:36)

            at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:101)

            at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:76)

            at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:77)

             

            So to fix this we are trying to use the latest in the app server but this fails to start with

             

            14:44:29,635 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.messaging.default: org.jboss.msc.service.StartException in service jboss.messaging.default: Failed to start service

            at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33]

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33]

            at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33]

            Caused by: java.lang.NoSuchMethodError: org.hornetq.core.config.Configuration.setLogDelegateFactoryClassName(Ljava/lang/String;)V

            at org.jboss.as.messaging.HornetQService.start(HornetQService.java:100)

            at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

            at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

            ... 3 more

            • 3. Re: How can I update as 7.1.1 to use the latest hornetq build ?
              Justin Bertram Master

              You won't be able to use the latest versions of HornetQ in JBoss AS 7.1.1 because the messaging subsystem it contains will be out of date.  Try a AS7 nightly build.

              • 6. Re: How can I update as 7.1.1 to use the latest hornetq build ?
                Andy Taylor Master

                thats built for 7.2 so it definately won't work, you could try building the AS7 branch https://github.com/hornetq/hornetq/tree/Branch_2_2_AS7, the fix should be in there

                • 7. Re: How can I update as 7.1.1 to use the latest hornetq build ?
                  peter craddock Novice

                  Tried it with the hornet module from the latest nightly build and I get this error

                   

                  15:38:01,866 WARN  [org.jboss.modules] (MSC service thread 1-1) Failed to define class org.jboss.as.messaging.jms.AS7Rec

                  overyRegistry in Module "org.jboss.as.messaging:main" from local module loader @6513cf0 (roots: D:\dev\as7\modules): jav

                  a.lang.LinkageError: Failed to link org/jboss/as/messaging/jms/AS7RecoveryRegistry (Module "org.jboss.as.messaging:main"

                  from local module loader @6513cf0 (roots: D:\dev\as7\modules))

                          at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:396)

                          at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243)

                          at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73)

                          at org.jboss.modules.Module.loadModuleClass(Module.java:517)

                          at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)

                          at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)

                          at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)

                          at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)

                          at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)

                          at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)

                          at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)

                          at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) [rt.jar:1.6.0_14]

                          at org.jboss.as.messaging.jms.PooledConnectionFactoryService.createService(PooledConnectionFactoryService.java:2

                  45) [jboss-as-messaging-7.1.1.Final.jar:7.1.1.Final]

                          at org.jboss.as.messaging.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:180) [jbo

                  ss-as-messaging-7.1.1.Final.jar:7.1.1.Final]

                          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-ms

                  c-1.0.2.GA.jar:1.0.2.GA]

                          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.G

                  A.jar:1.0.2.GA]

                          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_14]

                   

                  I'll try my own build once my check out has complete

                  • 8. Re: How can I update as 7.1.1 to use the latest hornetq build ?
                    peter craddock Novice

                    what goal should I use to build this ? I currently have an error running the package goal

                     

                    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.3:test (default-test) on project horn

                    etq-commons: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.12.3:test failed: Plugin or

                    g.apache.maven.plugins:maven-surefire-plugin:2.12.3 or one of its dependencies could not be resolved: Could not find art

                    ifact org.apache.maven.reporting:maven-reporting-api:jar:2.0.9 in jboss.release (https://repository.jboss.org/nexus/cont

                    ent/groups/public) -> [Help 1]