-
1. Re: Possible issues with netty bridge?
clebert.suconic Jun 22, 2010 5:55 PM (in response to dhawes)There's an issue with paging when receiving messages over the bridge that I'm aware of.
https://jira.jboss.org/browse/HORNETQ-382
Besides this, I have seen a few issues on the Bridge fixed on past releases. Are you using the latest release? (you didn't state what version you're using now)
-
2. Re: Possible issues with netty bridge?
clebert.suconic Jun 22, 2010 5:56 PM (in response to clebert.suconic)382 is being fixed now. There's a fix committed that jeff will confirm tomorrow if that's fixing the issue or not.
-
3. Re: Possible issues with netty bridge?
dhawes Jun 22, 2010 6:05 PM (in response to clebert.suconic)We are using 2.1.0 Final.
-
4. Re: Possible issues with netty bridge?
dhawes Jul 8, 2010 4:39 PM (in response to dhawes)I have noticed a third issue.
Sometimes messages can be enqueued (MessageCount increases), but they are never sent to the target. When then happens the ConsumerCount is 0. A restart of the source causes everything to work properly (though I have not determined if the messages in the queue before the restart ever make it to the target).
I am wondering if these logs are related (hostnames and ips changed):
source 2010-07-07 23:39:10,569 ERROR [org.hornetq.core.client.impl.ClientSessionImpl] (Thread-23 (group:HornetQ-client-global-threads-236948990)) Failed to handle failover
HornetQException[errorCode=3 message=Timed out waiting for response when sending packet 32]
at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:277)
at org.hornetq.core.client.impl.ClientSessionImpl.handleFailover(ClientSessionImpl.java:874)
at org.hornetq.core.client.impl.FailoverManagerImpl.reconnectSessions(FailoverManagerImpl.java:814)
at org.hornetq.core.client.impl.FailoverManagerImpl.failoverOrReconnect(FailoverManagerImpl.java:715)
at org.hornetq.core.client.impl.FailoverManagerImpl.handleConnectionFailure(FailoverManagerImpl.java:577)
at org.hornetq.core.client.impl.FailoverManagerImpl.access$600(FailoverManagerImpl.java:70)
at org.hornetq.core.client.impl.FailoverManagerImpl$DelegatingFailureListener.connectionFailed(FailoverManagerImpl.java:1140)
at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.callFailureListeners(RemotingConnectionImpl.java:482)
at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.fail(RemotingConnectionImpl.java:254)
at org.hornetq.core.client.impl.FailoverManagerImpl$PingRunnable$1.run(FailoverManagerImpl.java:1198)
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)
source 2010-07-07 23:39:10,569 WARN [org.hornetq.core.protocol.core.impl.RemotingConnectionImpl] (Thread-15 (group:HornetQ-client-global-threads-236948990)) Connection failure has been detected: Did not receive data from server for org.hornetq.core.remoting.impl.netty.NettyConnection@25e6ed81[local= /source:60262, remote=/target:5445] [code=3]This is with HornetQ 2.1.0. We are upgrading to 2.1.1 in the near future. Do any of the fixes for 2.1.1 apply here?