lto:a...@amlinv.com]
Sent: Friday, September 02, 2016 12:36 AM
To: users@activemq.apache.org
Subject: Re: Need Help With A JMS Exception
The broker and client negotiate the version of the OpenWire protocol when the
client connects. If the client sends a version of an ack that the broker
do
rsday, September 01, 2016 12:05 PM
> To: [hidden email] <http:///user/SendEmail.jtp?type=node&node=4716079&i=1>
> Subject: Re: Need Help With A JMS Exception
>
> A couple of thoughts on this front.
>
> First, how was the conclusion of different client versions made?
artnaseef [mailto:a...@amlinv.com]
Sent: Thursday, September 01, 2016 12:05 PM
To: users@activemq.apache.org
Subject: Re: Need Help With A JMS Exception
A couple of thoughts on this front.
First, how was the conclusion of different client versions made? I'm curious
because I can't t
062&i=0>]
> Sent: Thursday, September 01, 2016 10:58 AM
> To: [hidden email] <http:///user/SendEmail.jtp?type=node&node=4716062&i=1>
> Subject: Re: Need Help With A JMS Exception
>
> +1 Agree that debugging it is the only surefire way to understand what
> is goin
-Original Message-
From: Matt Pavlovich [mailto:mattr...@gmail.com]
Sent: Thursday, September 01, 2016 10:58 AM
To: users@activemq.apache.org
Subject: Re: Need Help With A JMS Exception
+1 Agree that debugging it is the only surefire way to understand what
is going on.
On a side note
+1 Agree that debugging it is the only surefire way to understand what
is going on.
On a side note-- CLIENT_ACKNOWLEDGE is kludgy of sorts. Be sure to
understand that it acknowledges the current message and _all_ previous
messages. It isn't an individual message acknowledgement as most people
Help With A JMS Exception
Since you have the 5.5.1 source code, I recommend you attach a debugger to the
broker process and set a breakpoint on the
TopicSubscription.acknowledge() method; the stack will tell you how you got
there. Setting breakpoints on the broker can lead to instability and may
Since you have the 5.5.1 source code, I recommend you attach a debugger to
the broker process and set a breakpoint on the
TopicSubscription.acknowledge() method; the stack will tell you how you got
there. Setting breakpoints on the broker can lead to instability and may
force you to restart it (pl
