If you turn protocol logging on for the JMS client (see:
http://mail-archives.apache.org/mod_mbox/qpid-users/201402.mbox/%3CCACsaS94QyZbYrScWNtChgk=gn3ojdzgsl5sk5rrnvoj9izj...@mail.gmail.com%3E
for an explanation of how to do that) what do you see? ... it should show
the mechanisms the MQ light ser
Hello,
I'm attempting to connect to MQLight with the Qpid JMS API for AMQP 1.0.
The code (in *Scala*):
/val host = "localhost"
val port = 5672
val user = "guest"
val pass = "guest"
val isSSL = false
val clientId = "test-client"
val connectionFactory = new Connection
Sorry, after a little investigation discovered that qpidd crashed due to assert
abort in qpid-proton library, function pn_full_settle. Currently I am using
proton 0.7, will now upgrade to latest (0.8rc4 == almost final) version and see
whether it will help.
Best regards,
24.10.2014 16:36, Michael
Hallo,
qpidd dies at some point with the following message:
[Protocol] error Error on attach: Node not found:
eead7253-4466-44d8-927a-af151f2f2184_receiver-xxx
[System] warning CLOSING [qpid.127.0.0.1:5672-127.0.0.1:54665] unsent data
(probably due to client disconnect)
Is this a qpidd b
Hi Alan,
we are using the C++ client and local transactions.
The client starts a transactional session with one C++ Qpid Broker, then
sends some messages on an exchange topic and afterwards commits them (or
calls rollback).
Andreas
Am 23.10.2014 um 16:41 schrieb Alan Conway:
On Thu, 2014
