On Wed, Jan 6, 2010 at 2:25 PM, Jen Andre <[email protected]> wrote: > > > I can't use the JMS API because of this bug: > http://old.nabble.com/-jira--Created:-(QPID-1875)-Can't-create-durable-queues-that-use-amq.topic-due-to-error-in-BindingURLParser.-td23726482.html. > I need to create a durable queue bound to a topic. If there some > workaround let me know, I am happy to use the JMS API otherwise.
This is fixed in the upcomming 0.6 release. I expect the release to be happening soon. > I was able to successfully build from trunk. I changed nothing in my test > program, but now I am no longer getting timeouts and I see the heartbeat > replies in the log messages coming from my client: > 2010-01-06 12:02:01,703 INFO [Dispatcher-Channel-1] > client.AMQSession$Dispatcher (AMQSession.java:2910) - Dispatcher-Channel-1 > started > 2010-01-06 12:04:00,829 DEBUG [IoReceiver - /192.168.10.128:5672] > util.Logger (Logger.java:54) - RECV: [conn:1035079] ch=0 > ConnectionHeartbeat() > 2010-01-06 12:04:00,829 DEBUG [IoReceiver - /192.168.10.128:5672] > util.Logger (Logger.java:54) - SEND: [conn:1035079] ch=0 > ConnectionHeartbeat() > 2010-01-06 12:04:00,829 DEBUG [IoReceiver - /192.168.10.128:5672] > util.Logger (Logger.java:54) - FLUSH: [conn:1035079] > > > Something odd is happening -- I will try to narrow it down, since I want to > use the 0.5 version if at all possible. The 0.5 release was was taken from rev 779632, while the proper support for java client to echo heartbeats was added in rev 782633 So that explains why you didn't see it when you tried with the 0.5 release. Could you test it out with the most recent RC for the 0.6 release? We should be releasing that pretty soon. > > Rajith Attapattu wrote: >> >> On Tue, Jan 5, 2010 at 4:48 PM, Jen Andre <[email protected]> wrote: >>> >>> Yes, I am using both the c++ broker and the java library from 0.5. >>> >>> Setting the idle_timeout in the AMQP url doesn't seem affect anything. >>> I will try grabbing the latest from trunk as suggested by another >>> user. >>> >>> I'm not sure which API I'm supposed to be using. I tried both the >>> code in org.apache.qpid.client.* and org.apache.qpid.transport.* and >>> I get the same behavior. >> >> You are supposed to use the JMS API. >> The classes you are using right now are in the implementation layer >> and are subject to change without any notice btw versions. >> >> >>> Here some sample code. Maybe you can tell me what I'm doing wrong >> >> I cut paste your code and added an exception listener to the >> connection and I didn't see any timeouts. >> >> If I did a kill -STOP <broker-pid> then I saw a the client dropping >> the connection after 120 secs. >> >> >> > > -- > View this message in context: > http://n2.nabble.com/timeouts-tp4256406p4262712.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]
