Questions of qpid-route usage

Hi all, I am really confused about this tool. Hope some kind soul can help to explain the mechanism to me. If we want to add a route between 2 brokers, we can use qpid-route route add ip:port ip:port exchange_type routingkey. Which means: A--B A is a fake client and B will be the server. B

Re: Questions of qpid-route usage

Hi Kyrie, not sure if I understand your thoughts properly, but in normal A--B federation (without -s option), B broker behaves as a fake client and subscribes to A. When -s is used, A initiates the connection to B and requests it to connect to itself. The main reason for this push-like option

Re: SSL in proton-j

Rafael, Here is JIRA issue: https://issues.apache.org/jira/browse/PROTON-523 Thanks, Piotr On Fri, Feb 21, 2014 at 8:15 PM, Rafael Schloming r...@alum.mit.edu wrote: I don't believe there is currently any way to do so, although you could use the Transport interface without SSL and use your

Re: Proton interop for java and python

Rafael, I pulled the latest from git.apache.org. The stack trace looks like NPE is thrown during processing incoming message. I will check my python code whether a container uuid or name is set and let you know (is there default id?). Thanks, Piotr On Fri, Feb 21, 2014 at 8:07 PM, Rafael

RE: Questions of qpid-route usage

Hi Pavel Moravec, Thanks for explaining to me. I am trying to understand you. So the answers for my questions are: If we want to add a route between 2 brokers, we can use qpid-route route add ip:port ip:port exchange_type routingkey. Which means: A--B A is a fake client and B will be

Re: Proton interop for java and python

Rafael, After adding container name in python the code do not throw NPE anymore. Thanks for the hint, Piotr On Mon, Feb 24, 2014 at 10:36 AM, Piotr Kliczewski piotr.kliczew...@gmail.com wrote: Rafael, I pulled the latest from git.apache.org. The stack trace looks like NPE is thrown during

Novice questions regarding dispatch routers and brokers +++

Hello list, we are setting up an AMQP messaging infrastructure using Qpid (currently using proton and the dispatch router, not the broker). This is the basic set-up: * We have a server side, with a public, known IP-address and port. * We have X number of clients going on/off the net at

Re: JMS AMQP 1.0 SocketException for rapid session/producer open and close

I'm not overly familiar with the capabilities of the ServiceBus implementation... I recollect there were (at some time) some restrictions about the number of sessions supported by a connection, or the number of links on a session. There's obviously nothing too useful in the logs there... I'm just

RE: JMS AMQP 1.0 SocketException for rapid session/producer open and close

there... I'm just wondering if rapid closing and opening of sessions is leading the client to open one session before the last session has been fully closed on the server side, and that perhaps this is not something that ServiceBus is happy with... I think you are right and I should ask SB

NPE in Receiver$1.remoteDetached() with AMQP 1.0 and Service Bus

Hi, I am testing QPID Java JMS client 0.26 against Microsoft Service Bus. I run queue consumer in one process, consumes messages. In another process I run publisher, publisher produces 1 small messages. Approximately at the time producer finishes its work, I get NPE in consumer. The

Re: NPE in Receiver$1.remoteDetached() with AMQP 1.0 and Service Bus

Hi Jan, are you sure you are using version 0.26 of the client? Looking at your stack trace I can see SessionEndpoint.detachLinks() calling SessionEndpoint.detach() from line 192 of SessionEndpoint. This seems to be an instance of this defect: https://issues.apache.org/jira/browse/QPID-5206 for

RE: NPE in Receiver$1.remoteDetached() with AMQP 1.0 and Service Bus

You are right, this was 0.24, with 0.26 the problem is solved. I am sorry for bothering you, Jan -Original Message- From: Rob Godfrey [mailto:rob.j.godf...@gmail.com] Sent: Monday, February 24, 2014 4:56 PM To: users@qpid.apache.org Subject: Re: NPE in Receiver$1.remoteDetached()

JMS AMQP 1.0 - can the receiver.receive(timeout) return null even when timeout not expired?

Hi, JMS 0.26 with AMQP 1.0 and Service Bus. I have concurrent producer and receiver. The receiver.receive(7) returns null after ~17 seconds(the timeout did not expired). The javadoc says that null should be returned when timeout expires or message consumer is concurrently closed. I do not

Re: Novice questions regarding dispatch routers and brokers +++

On 02/24/2014 12:51 PM, Tor Rune Skoglund wrote: Hello list, we are setting up an AMQP messaging infrastructure using Qpid (currently using proton and the dispatch router, not the broker). This is the basic set-up: * We have a server side, with a public, known IP-address and port. * We have X

Re: JMS AMQP 1.0 - can the receiver.receive(timeout) return null even when timeout not expired?

Hi Jan, I think the easiest thing to help diagnose what is going on is to run with logging turned on in the client... The client uses java logging and you can turn it on by setting the Java system property java.util.logging.config.file to point to a file that looks something like this:

Re: Questions of qpid-route usage

On 02/24/2014 10:24 AM, Gao, Jie (Kyrie, HPIT-DS-CDC) wrote: Hi Pavel Moravec, Thanks for explaining to me. I am trying to understand you. So the answers for my questions are: If we want to add a route between 2 brokers, we can use qpid-route route add ip:port ip:port exchange_type

Qpid Dispatch 0.2 beta-1

A number of important features and fixes have gone into Dispatch Router since the initial release. I have created a beta release for Dispatch 0.2 for folks to test. The binary distribution can be found here: http://people.apache.org/~tross/qpid-dispatch-0.2beta1/ The following