-
Bug
-
Resolution: Done
-
Major
-
EAP_EWP 5.3.0.ER1
-
None
-
Not Required
-
NEW
When java:/JmsXA configured on EAP 5 is trying to connect to HornetQ on EAP 6 then following warning is logged on EAP 5:
16:10:46,414 WARN [HornetQPacketHandler] Client with version 123 and address /127.0.0.1:49554 is not compatible with server version 2.2.24.GA (HQ_2_2_24_EAP_JBPAPP-10876, 122). Please ensure all clients and servers are upgraded to the same version for them to interoperate properly 16:10:46,414 ERROR [HornetQPacketHandler] 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) at org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handlePacket(HornetQPacketHandler.java:84) at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:528) at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:551) at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:512) at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:521) at org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:73) at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:100) at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:372) at org.jboss.netty.channel.StaticChannelPipeline$StaticChannelHandlerContext.sendUpstream(StaticChannelPipeline.java:534) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:287) at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.decode(HornetQFrameDecoder2.java:169) at org.hornetq.core.remoting.impl.netty.HornetQFrameDecoder2.messageReceived(HornetQFrameDecoder2.java:134) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:372) at org.jboss.netty.channel.StaticChannelPipeline$StaticChannelHandlerContext.sendUpstream(StaticChannelPipeline.java:534) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302) at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:321) at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:299) at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:372) at org.jboss.netty.channel.StaticChannelPipeline.sendUpstream(StaticChannelPipeline.java:367) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261) at org.jboss.netty.channel.socket.oio.OioWorker.run(OioWorker.java:100) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) at org.jboss.netty.util.VirtualExecutorService$ChildExecutorRunnable.run(VirtualExecutorService.java:181) 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:662) 16:10:46,414 WARN [HornetQPacketHandler] Client is not being consistent on the request versioning. It just sent a version id=122 while it informed 123 previously 16:10:46,423 WARN [HornetQPacketHandler] Client is not being consistent on the request versioning. It just sent a version id=122 while it informed 123 previously
It does not harm functionality and for this reason it should not appear in the log. ERROR and WARN messages are carefully watched by users/customers.
- is incorporated by
-
JBPAPP-11073 Upgrade HornetQ to 2.2.28.Final
- Resolved
- is related to
-
JBPAPP-11203 Interoperability EAP 5 <-> EAP6 - Client is not being consistent on the request versioning. It just sent a version id=122 while it informed 123 previously
- Closed