Jakub, We don't support a Java Qpid API. The supported API for java is JMS.
Regards, Rajith On Tue, Jan 5, 2010 at 3:29 PM, JAkub Scholz <[email protected]> wrote: > Hi, > > I had a similar problem with the C++ broker and Java client from release 0.5 > (with the Qpid API, JMS API didn't suffered with this problem). I tried to > download the latest source from trunk in SVN repository and compile the > library myself and it solved the problem for me. > > Regards > JAkub Scholz > >> -----Original Message----- >> From: Jen Andre [mailto:[email protected]] >> Sent: Tuesday, January 05, 2010 6:48 PM >> To: [email protected] >> Subject: timeouts >> >> >> Hello, >> >> I have a Java client listener that subscribes to a topic and waits for >> messages. I'm noticing after 120 seconds of idle time (no messages >> received) the connections time out (here's what I see in syslog >> messages for >> qpidd) >> >> qpidd[3472]: 2010-01-01 16:46:20 error Connection timed out: closing >> >> This is consistent with the debug messages I'm seeing on the client >> side: >> >> IoReceiver - /192.168.10.128:5672 2010-01-05 12:32:10,126 WARN >> [apache.qpid.transport.ClientDelegate] Ignoring the idle timeout 0 set >> by >> the connection, using the brokers max value 120 >> >> and >> >> >> IoReceiver - /192.168.10.128:5672 2010-01-05 12:38:57,898 DEBUG >> [apache.qpid.transport.Connection] RECV: [conn:9ced8e] ch=0 >> ConnectionHeartbeat() >> IoReceiver - /192.168.10.128:5672 2010-01-05 12:40:57,899 DEBUG >> [apache.qpid.transport.Connection] RECV: [conn:9ced8e] ch=0 >> ConnectionHeartbeat() >> IoReceiver - /192.168.10.128:5672 2010-01-05 12:40:58,618 DEBUG >> [apache.qpid.transport.Connection] connection closed: conn:9ced8e >> >> >> I'm a bit confused on how timeouts and heartbeats are supposed to work. >> Does the client force the disconnect, or the server, or both, if the >> heartbeats are not received in a specific period of time? Do both >> peers >> send heartbeats? (this seems to imply it does. >> http://qpid.apache.org/configure-broker-and-client-heartbeating.html). >> >> I do notice that while I see a lot of RECV: heartbeat debug messages on >> the >> client side, I don't see any SEND: messages that indicates it's sending >> them >> to server. If the client is supposed to send them to the server >> periodically to ensure the connection stays alive, how can I ensure >> this is >> happening? (setting system property amqj.heartbeat.delay seems to have >> no >> effect). >> >> Thanks! >> Jen >> >> >> >> >> >> -- >> View this message in context: http://n2.nabble.com/timeouts- >> tp4256406p4256406.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] > > > --------------------------------------------------------------------- > 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]
