3 Replies Latest reply on Jun 26, 2013 10:24 AM by Justin Bertram

    AS 7.2.0 not the same as EAP 6.1

    peter craddock Novice

      We raised a bug some time ago against 7.1 and this was finally fixed in EAP 6.1.

       

      Since I cant package and release 6.1 I used a build of 7.2 from http://olex.openlogic.com/packages/jboss/7.2.0.Final this still has our original bug in ithttps://issues.jboss.org/browse/JBEAP-4

       

      So how can I get a comunity version of Jboss that does contain my fix in it ?

       

      I have the source checked out so I guess I need to update the POM file to get the correct version of the remoting module out

        • 1. Re: AS 7.2.0 not the same as EAP 6.1
          Tomaz Cerar Master

          Hi,

           

          7.2.0.Final == EAP 6.1.0.Alpha

           

          your bug was fixed in EAP 6.1.0.CR1 which was released later.

           

          also fix for your problem is fixed in upstream, so you can use WildFly 8.0 alpha1 or alpha2 that both have this fix.

           

          Or if you need 7.x, then i would recommend you to checkout 7.2.0.Final tag from github and change version of version.org.jboss.remote-naming pom.xml to 1.0.6.Final.

          or apply this patch against it https://github.com/wildfly/wildfly/pull/4261/files

           

          --

          tomaz

          • 2. Re: AS 7.2.0 not the same as EAP 6.1
            peter craddock Novice

            I have checked out the source and altered the pom and this sorts out the reported problem thanks.

             

            I now get the following stack from the client when connecting to the topic any idea what is causing this

             

            15:06:50,274 DEBUG [client] Trying to connect at the main server using connector :TransportConfiguration(name=netty, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8030&host=10-2-32-7

            15:06:50,274 DEBUG [client] Remote destination: /10.2.32.7:8030

            15:06:50,535 DEBUG [client] Reconnection successfull

            15:06:50,670 DEBUG [client] Node d7490d1c-de68-11e2-b617-f30efc513c42 going up, connector = Pair[a=null, b=null], isLast=true csf created at

            serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=netty, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8030&host=10-2-32-7], discoveryGroupConfiguration=null]

            java.lang.Exception

                at org.hornetq.core.client.impl.ClientSessionFactoryImpl.<init>(ClientSessionFactoryImpl.java:197)

                at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:808)

                at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:583)

                at org.hornetq.jms.client.HornetQConnectionFactory.createTopicConnection(HornetQConnectionFactory.java:131)

                at org.hornetq.jms.client.HornetQConnectionFactory.createTopicConnection(HornetQConnectionFactory.java:126)

                at com.cedar.cp.util.common.JmsConnectionImpl$AbstractJmsTopic.<init>(JmsConnectionImpl.java:289)

                at com.cedar.cp.util.common.JmsConnectionImpl$JmsTopicSubscriber.<init>(JmsConnectionImpl.java:416)

                at com.cedar.cp.util.common.JmsConnectionImpl.<init>(JmsConnectionImpl.java:36)

                at com.cedar.cp.impl.base.CPConnectionImpl.getJmsConnection(CPConnectionImpl.java:426)

                at com.cedar.cp.impl.base.EntityEventWatcher.init(EntityEventWatcher.java:30)

                at com.cedar.cp.impl.base.EntityEventWatcher.access$200(EntityEventWatcher.java:10)

                at com.cedar.cp.impl.base.EntityEventWatcher$1.run(EntityEventWatcher.java:57)

            15:06:53,119 DEBUG [utils] using dummy address 5d:ffffff82:fffffff2:16:ffffffee:44

            15:06:53,120 DEBUG [client] NodeUp ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=netty, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8030&host=10-2-32-7], discoveryGroupConfiguration=null]::nodeID=d7490d1c-de68-11e2-b617-f30efc513c42, connectorPair=Pair[a=TransportConfiguration(name=a71d8c4f-de69-11e2-8a0e-5d82f216ee2c, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8030&host=10-2-32-7, b=null]

            java.lang.Exception: trace

                at org.hornetq.core.client.impl.ServerLocatorImpl.notifyNodeUp(ServerLocatorImpl.java:1509)

                at org.hornetq.core.client.impl.ClientSessionFactoryImpl$Channel0Handler$1.run(ClientSessionFactoryImpl.java:1611)

                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

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

            15:06:53,121 DEBUG [client] Topology@3f9872ad::NewMemeberAdd nodeId=d7490d1c-de68-11e2-b617-f30efc513c42 member = TopologyMember[name = default, connector=Pair[a=TransportConfiguration(name=a71d8c4f-de69-11e2-8a0e-5d82f216ee2c, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=8030&host=10-2-32-7, b=null]]

            • 3. Re: AS 7.2.0 not the same as EAP 6.1
              Justin Bertram Master

              This is just DEBUG logging.  There are no errors here.