I have noticed a couple of issues that seem to arise when using a netty bridge.
The first is that sometimes messages are never sent across the bridge. Other messages can still be enqueued and will be sent over the bridge when this happens, but the "stuck" messages just sit there (the jmx-console count never goes to 0). These messages will remain in this state until the source JBoss is restarted (a restart on the target JBoss does nothing), at which point they will be sent across the bridge.
The second issue that I see is that the source queue sometimes hangs until it is restarted. When this happens I cannot view anything about the queue through the jmx-console (the webpage simply hangs on load). Messages can still be enqueued, but they are never sent across the bridge. A restart of the source JBoss is necessary to resume sending the enqueued messages.
I noticed this issue:
http://community.jboss.org/thread/153084 (JMS Bridge stops retrying even with unlimited retry configured)
and have set both the jnp.timeout and jnp.sotimeout on a whim, but have still noticed this occuring.
I occasionally see the following in the logs, but I am not sure if it is related:
2010-06-18 09:44:13,557 WARN [org.jboss.resource.connectionmanager.TxConnectionManager] (Thread-49) Connection error occured: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@56d94a5f[state=NORMAL mc=org.hornetq.ra.HornetQRAManagedConnection@539c5c48 handles=0 lastUse=1276868340599 permit=false trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@38808450 context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@7d6ebd2a xaResource=org.hornetq.ra.HornetQRAXAResource@53a1cf84 txSync=null]
javax.jms.JMSException: HornetQException[errorCode=2 message=Channel disconnected]
Has anyone seem similar issues with netty bridges?