Hi Robbie,
yes we are using the logs from the Qpid client API. We need them currently
the most of the time if something is wrong in the data we received from the
broker. Then we send the log files as evidence to the provider of the
service we are connecting to with our client application.
Is
Hi Erik,
We will likely look at beginning a 0.3.0 release fairly soon, e.g in
the next week or so.
Robbie
On 8 June 2015 at 07:25, Erik Aschenbrenner easch...@icubic.de wrote:
Hi Robbie,
yes we are using the logs from the Qpid client API. We need them currently
the most of the time if
Dear Qpid users,
the old Qpid client API used the loggers FRM and RAW. These were
replaced by the loggers org.apache.qpid.jms.provider.amqp.FRAMES and
org.apache.qpid.jms.provider.amqp.BYTES. The byte logger only logs sent
data. Why doesn't it log the received data also? This would be interesting
Hi Erik,
I think the most likely answer is that none of us really use that
logger and so haven't noticed the disparity :)
I just pushed a change to use the BYTES logger for the incoming data
as well for consistency with the outgoing data handling in that class,
as the trace message that was
On 4 June 2015 at 10:28, Robbie Gemmell robbie.gemm...@gmail.com wrote:
On 4 June 2015 at 08:01, Erik Aschenbrenner easch...@icubic.de wrote:
Ok thanks,
I created my connection URI by using the new options now.
First of all, I had to find out, that the URI option for the client ID has
to be
Dear Qpid users,
here is another difference I noticed between the old and the new client API:
The correlation ID of a received message which can be obtained via (JMS)
Message.getJMSCorrelationID() now has the prefix ID:. So I had to change
my code because my application uses this ID to map
On 06/03/2015 09:45 AM, Erik Aschenbrenner wrote:
Dear Qpid-Users,
I just tried to use the new proton based Qpid JMS 0.2.0 client.
I removed the jars of the old client (Qpid JMS 0.32) and added the jars of
the new client to my project.
When I try to start my application I'm getting this
