On 01/12/17 21:56, tomt wrote:
I have successfully managed to create a durable queue with a binding to an
exchange through QpidJMS when I connect directly to the broker using the
Session.createDurableConsumer() API. This is great progress for us. It
appears that queue is going to live forever,
Proton will raise a proton::error, which just inherits
std::runtime_exception. The e.what() message should include the "name:
descripition" from the AMQP condition that was received on the wire.
If you are closing a connection at your end and want to send a message to
the other end you can call co
By the way.
Does anybody have an idea how could we encode any information fromn the
Exception thrown?
I mean, correct Exception cast to some type from which we could print it's
input?
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
--
1) "ANONYMOUS" results in the same error as "EXTERNAL".
2) Yes, no message wasn't even tried to be sent, since connection was never
granted.
3) Regarding correct username and password.
>From what I figured out,
*username *is equivalent to *ServiceBusQueuePolicyName*
*password * is equivalent to
On 04/12/17 16:11, igor wrote:
No,
I'm not trying to use SSL client-certificate based authentication.
As far as I figured out, Azure SB uses SAS authentification.
Simply attached "Authentification" header with SAS token (generated from
policyName, keyValy and entity) as it's value to the message
No,
I'm not trying to use SSL client-certificate based authentication.
As far as I figured out, Azure SB uses SAS authentification.
Simply attached "Authentification" header with SAS token (generated from
policyName, keyValy and entity) as it's value to the messages sent to the
Queue, performed a
On 4 December 2017 at 14:55, igor wrote:
> Hej, thanks for reply.
>
> Yes, I've tried to set idle_timeout to "0", or not to set it atall.
> Nothing actually happens, the same error msg. is received.
>
> And Yes, host name is correct. I was successfuly using the same hostname for
> message sending
Ok,
Regarding SASL authentication.
I looked through example programs from the Qpid Proton tutorial page and
those which are supplied after the qpid proton build process.
There where examples (e.g. service_bus) with no SSL encryption stuff.
I mean there are simply given policy/key/namespace/enti
Hej, thanks for reply.
Yes, I've tried to set idle_timeout to "0", or not to set it atall.
Nothing actually happens, the same error msg. is received.
And Yes, host name is correct. I was successfuly using the same hostname for
message sending via Postman or Boost.Asio. But this time I needed AMQ
On 4 December 2017 at 14:24, Gordon Sim wrote:
> On 04/12/17 14:15, Alan Conway wrote:
>>
>> Have you tried turning the timeout off completely by setting it to 0?
>
>
> Might be worth a try, certainly.
>
>> If
>> the connection is idle, and the Azure side is not sending keepalives
>> (which
>> see
On 04/12/17 14:15, Alan Conway wrote:
Have you tried turning the timeout off completely by setting it to 0?
Might be worth a try, certainly.
If
the connection is idle, and the Azure side is not sending keepalives (which
seems to be the case) then you should have idle-timeout turned off
comple
Have you tried turning the timeout off completely by setting it to 0? If
the connection is idle, and the Azure side is not sending keepalives (which
seems to be the case) then you should have idle-timeout turned off
completely on the proton side, otherwise it will time out eventually no
matter how
12 matches
Mail list logo
