2 Replies Latest reply on Nov 26, 2009 6:45 PM by Ross Nicholson

    Latest Trunk - Issues

    Ross Nicholson Apprentice

      First of all, I know I'm using trunk which is not supposed to be stable. What I wanted to do was test the various fixes, but most importantly the paging for bridges.

      Unfortunately I did not get that far.

      First I get this error when sending a message:

      java.lang.IllegalArgumentException: n must be positive
       at java.util.Random.nextInt(Random.java:250)
       at org.hornetq.core.client.impl.RoundRobinConnectionLoadBalancingPolicy.select(RoundRobinConnectionLoadBalancingPolicy.java:42)
       at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:1087)
       at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:819)
       at org.hornetq.jms.client.HornetQConnection.authorize(HornetQConnection.java:544)
       at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:579)
       at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:114)
       at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:109)
       at com.paddypower.phase.common.internal.jms.JMSConnectionImpl.<init>(JMSConnectionImpl.java:39)
       at com.paddypower.phase.common.internal.jms.JMSConnectionSingleQueuePool.getConnection(JMSConnectionSingleQueuePool.java:175)
       at com.paddypower.phase.common.internal.jms.JMSConnectionMultiQueuePool.getConnection(JMSConnectionMultiQueuePool.java:126)
       at com.paddypower.phase.input.core.InputMessageSenderTask.sendMesage(InputMessageSenderTask.java:139)
       at com.paddypower.phase.input.core.InputMessageSenderTask.run(InputMessageSenderTask.java:102)
       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)
      


      Secondly I get the follow error when trying to activate an MDB:

      2009-11-25 18:10:29,405 ERROR [org.hornetq.ra.inflow.HornetQActivation] (WorkManager(2)-2) Unabler to start activation
      HornetQException[errorCode=2 message=Unable to connect to server using configuration org-hornetq-core-remoting-impl-invm-InVMConnectorFactory?serverid=0]
       at org.hornetq.core.client.impl.FailoverManagerImpl.createSession(FailoverManagerImpl.java:280)
       at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSessionInternal(ClientSessionFactoryImpl.java:1091)
       at org.hornetq.core.client.impl.ClientSessionFactoryImpl.createSession(ClientSessionFactoryImpl.java:819)
       at org.hornetq.ra.HornetQResourceAdapter.createSession(HornetQResourceAdapter.java:1293)
       at org.hornetq.ra.inflow.HornetQActivation.setupSession(HornetQActivation.java:317)
       at org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:264)
       at org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:473)
       at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
       at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
       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)
      


      Finally, I don't think the bridges are working. I don't get any log messages when when I shutdown one side of the bridge.

      I'm using AS5, trunk from this afternoon and the in-vm connector to send messages.

      Any idea what's a good time to checkout trunk or a nightly tag which might work?

      Cheers,

      Ross

        • 1. Re: Latest Trunk - Issues
          Andy Taylor Master

          This is probably a byproduct of a dodgy config in *-jms.xml. check the connector-ref is surrounded by elements as follows.

          <connection-factory name="ConnectionFactory">
           <connectors>
           <connector-ref connector-name="netty-connector"/>
           </connectors>
           <entries>
           <entry name="ConnectionFactory"/>
           <entry name="XAConnectionFactory"/>
           </entries>
           </connection-factory>


          and not

          <connection-factory name="ConnectionFactory">
           <connector-ref connector-name="netty-connector"/>
           <entries>
           <entry name="ConnectionFactory"/>
           <entry name="XAConnectionFactory"/>
           </entries>
           </connection-factory>
          


          There was a problem with the schema that didn't pick this up which is now fixed in trunk.

          • 2. Re: Latest Trunk - Issues
            Ross Nicholson Apprentice

            Great, thanks.

            I'll try this out tomorrow and see how I get on.