2010/1/6 Jen Andre <[email protected]>: > > > 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.
If you are wanting a durable queue bound to a topic then all you need do is define your topic in JNDI topic.JNDIName=TopicName Then create a durable subscription: session.createDurableSubscriber(topic,name) The topic is the value retrieved from JNDI and name is a unique identifier for your subscription. There should be no need to define a custom URL in the JNDI property file. Cheers Martin > 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. > > > 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] > > -- Martin Ritchie --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
