On Thu, Feb 11, 2010 at 6:26 PM, Jen Andre <[email protected]> wrote: > > Thanks! I pulled the version from trunk, and indeed disabling qpid.heartbeat > did indeed fix it.
Thanks, great to hear that ! > I also wrote a simple java TCP client that connects to a server (in my case, > just netcat -l) and prints messages it gets and the current timestamp. I > ran it on the "bad server", then sent it some messages periodically. if I > setSoTimeout() on the socket for 120000 ms, I get the > "SocketTimeoutException: read timed out", even though the last message was > received 13 seconds ago. If I don't set the timeout, the program runs fine > forever. > > So: something strange is happening on this VM, possibly. I really appreciate you trying out this experiment ! It seems there is a possible bug either in the VM or the JVM impl. > > > -- > View this message in context: > http://n2.nabble.com/Connection-read-timed-out-tp4544370p4558127.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/ --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
