[switchyard-issues] [JBoss JIRA] Created: (SWITCHYARD-460) Update camel-jms-binding to work with latest version of AS7 (jboss-as-7.1.0.Alpha1-SNAPSHOT)

Daniel Bevenius (JIRA) jira-events at lists.jboss.org
Thu Sep 15 06:42:26 EDT 2011


Update camel-jms-binding to work with latest version of AS7 (jboss-as-7.1.0.Alpha1-SNAPSHOT)
--------------------------------------------------------------------------------------------

                 Key: SWITCHYARD-460
                 URL: https://issues.jboss.org/browse/SWITCHYARD-460
             Project: SwitchYard
          Issue Type: Task
          Components: quickstarts
            Reporter: Daniel Bevenius
            Assignee: Daniel Bevenius


The HornetQ version has been updated to 2.2.7.Final and the client is incompatible with the server:
{noformat}
11:17:18,441 WARN  [org.hornetq.core.protocol.core.impl.HornetQPacketHandler] (Old I/O server worker (parentId: 588932657, [id: 0x231a6631, localhost/127.0.0.1:5445])) Client with version 120 and address /127.0.0.1:57856 is not compatible with server version 2.2.7.Final (HQ_2_2_6_FINAL_AS7, 121). Please ensure all clients and servers are upgraded to the same version for them to interoperate properly
11:17:18,460 ERROR [org.hornetq.core.protocol.core.impl.HornetQPacketHandler] (Old I/O server worker (parentId: 588932657, [id: 0x231a6631, localhost/127.0.0.1:5445])) Failed to create session : HornetQException[errorCode=108 message=Server and client versions incompatible]
        at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handleCreateSession(HornetQPacketHandler.java:151) [hornetq-core-2.2.7.Final.jar:]
        at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handlePacket(HornetQPacketHandler.java:84) [hornetq-core-2.2.7.Final.jar:]
        at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:474) [hornetq-core-2.2.7.Final.jar:]
        at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:496) [hornetq-core-2.2.7.Final.jar:]
        at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:457) [hornetq-core-2.2.6.Final.jar:]
        at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:458) [hornetq-core-2.2.7.Final.jar:]
        at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:73) [hornetq-core-2.2.7.Final.jar:]
        at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100) [netty-3.2.3.Final.jar:]
        at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:362) [netty-3.2.3.Final.jar:]
        at org.jboss.netty.channel.StaticChannelPipeline$StaticChannelHandlerContext.sendUpstream(StaticChannelPipeline.java:514) [netty-3.2.3.Final.jar:]
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:287) [netty-3.2.3.Final.jar:]
        at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.decode(HornetQFrameDecoder2.java:169) [hornetq-core-2.2.7.Final.jar:]
        at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:134) [hornetq-core-2.2.7.Final.jar:]
        at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) [netty-3.2.3.Final.jar:]
        at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:362) [netty-3.2.3.Final.jar:]
        at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:357) [netty-3.2.3.Final.jar:]
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) [netty-3.2.3.Final.jar:]
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) [netty-3.2.3.Final.jar:]
        at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:90) [netty-3.2.3.Final.jar:]
        at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.2.3.Final.jar:]
        at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) [netty-3.2.3.Final.jar:]
        at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:181) [netty-3.2.3.Final.jar:]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
        at java.lang.Thread.run(Thread.java:680) [:1.6.0_26]
{noformat}
Update the version of HornetQ to 2.2.7.Final in pom.xml and also upgrade Netty to 3.2.3.Final:
{noformat}
<properties>
    <switchyard.version>0.3.0-SNAPSHOT</switchyard.version>
    <hornetq.version>2.2.7.Final</hornetq.version>
    <netty.version>3.2.3.Final</netty.version>
  </properties>
{noformat}

The test code for this quickstart still extends SwitchYardTestCase and this should be changed to use the new style of testing.

Changes to the HornetQ API require code changes to the HornetQClient to get it to compile. I'm also seeing a strange error where I don't get an error message but nothing is happing on the server or client.

Update the Readme file and change the command for creating the jms queue.
{noformat}
create-jms-queue name=GreetingServiceQueue entries=GreetingServiceQueue durable=true
{noformat}
should be changed to 
{noformat}
 add-jms-queue --name=GreetingServiceQueue --entries=GreetingServiceQueue --durable=true
{noformat}


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the switchyard-issues mailing list