I don't believe there is currently any way to do so, although you could use
the Transport interface without SSL and use your own SSLEngine to provide
encryption.
The SSL stuff on the Java side is slated for a bit of a cleanup as soon as
I have some time for it. If you file a JIRA for this capabil
What version are you using? I recall seeing the same issue on trunk,
however I thought I had fixed it and I didn't think it had made it into a
release. (I could be wrong.)
In any case you can probably work around the problem by supplying an
explicit name when you construct the messenger, e.g. Mess
Should have guessed it was ServiceBus from your previous issue... I'm not
ruling out some sort of client issue... but as above the error you're
getting would point to the server side disconnecting for some reason...
whether that reason is a server side error or a client error is a little
hard to kn
Hello,
I am sending message from java to python. Python code uses sasl authentication.
During processing response from python code I see following exception.
Can you tell me how to set the container-id in python?
Piotr
Exception in thread "main"
org.apache.qpid.proton.engine.TransportException:
Its Microsoft Service Bus with SSL :-)
If it works against Java QPID broker, it might be problem on the server side.
Thank you for testing. I will check the logs but I am afraid I will not find
anything useful.
Kind regards, Jan
> -Original Message-
> From: Rob Godfrey [mailto:rob.j.g
On 21 February 2014 10:58, Rob Godfrey wrote:
> Hi Jan,
>
> can you confirm which broker you are testing against here?
>
> I ran the code above on trunk against the Java Broker and didn't
> immediately see an issue (though I wasn't using SSL and you appear to be,
> so I shall try that presently)
Hi Jan,
can you confirm which broker you are testing against here?
I ran the code above on trunk against the Java Broker and didn't
immediately see an issue (though I wasn't using SSL and you appear to be,
so I shall try that presently)
Thanks,
Rob
On 21 February 2014 10:35, Jan Bares wrote:
Hi,
The code bellow throws SocketException with QPID 0.26 AMQP 1.0. It works fine
with AMQP 0-10 client. When I add sleeps of 100ms before and after the close()
calls, it works. Seems like the close() method returns too early when
background threads are still not finished. The code is minimal t
