Timed out waiting for response when sending packet

[philiplee]

Hi,

I'm getting the error below (repeatably) when testing with a heavy load. Both sender and receiver are in the same JVM. Any idea what's going on here?

The only reference I could find was this:

http://community.jboss.org/thread/19004

Thanks,

    Phil.

HornetQ GA2.0

JBoss 4.2.3GA

JRE6

Fedora12

2010-01-18 11:57:42,957 [3357173][35051][][] WARN  [org.hornetq.core.client.impl.ClientSessionImpl] Timed out waiting for response when sending packet 54
HornetQException[errorCode=3 message=Timed out waiting for response when sending packet 54]
        at org.hornetq.core.remoting.impl.ChannelImpl.sendBlocking(ChannelImpl.java:270)
        at org.hornetq.core.client.impl.ClientSessionImpl.prepare(ClientSessionImpl.java:1253)
        at org.hornetq.ra.HornetQRAXAResource.prepare(HornetQRAXAResource.java:120)
        at org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper.prepare(JcaXAResourceWrapper.java:93)
        at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelPrepare(XAResourceRecord.java:264)
        at com.arjuna.ats.arjuna.coordinator.BasicAction.doPrepare(BasicAction.java:2871)
        at com.arjuna.ats.arjuna.coordinator.BasicAction.doPrepare(BasicAction.java:2828)
        at com.arjuna.ats.arjuna.coordinator.BasicAction.prepare(BasicAction.java:2382)
        at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1783)
        at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:88)
        at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1389)
        at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135)
        at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87)
        at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:140)
        at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1028)
        at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:732)
        at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:701)
        at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140)

        ...

[timfox]

Can you take a look at this first?

http://community.jboss.org/wiki/Howtoreportabugissue

[philiplee]

Could this be a deadlock caused by the producer being flow controlled?

I'm using the configuration below with <max-size-bytes> deliberately set low (but larger than individual messages) to prove that flow control is working.

      <address-setting match="queue.TestQueue">
          <max-size-bytes>1000</max-size-bytes>
          <address-full-policy>DROP</address-full-policy>
      </address-setting>

- Phil.

[philiplee]

Will do, our messages crossed in the ether.

    Phil.