Sorry about that. I thought I attached it. I'll try again here.
Michael Tarullo
Contractor (Engility Corp)
Software Engineer
FAA WJH Technical Center
(609)485-5294
-Original Message-
From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain
Sent: Wednesday, September 14
So I've set my breakpoint in the wrong function of the wrong class?
Michael Tarullo
Contractor (Engility Corp)
Software Engineer
FAA WJH Technical Center
(609)485-5294
-Original Message-
From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain
Sent: Tuesday, September 13,
I have been assigned to track down a problem that requires debugging of the
message broker.
For this particular situation we are running version 5.5.1 of ActiveMQ.
I downloaded the source code for version 5.5.1 of ActiveMQ and imported it into
an Eclipse project I created for this purpose. I t
esn't support, something is really wrong.
Are all the brokers running the same version of ActiveMQ?
On Thu, Sep 1, 2016 at 12:52 PM, Michael.CTR.Tarullo [via ActiveMQ] <
ml-node+s2283324n4716079...@n4.nabble.com> wrote:
> I am not certain about this but I think the version mismatc
old messages. So, if the consumer then proceeds
to send an acknowledgement for the message, the broker won't be able to match
the message.
On Thu, Sep 1, 2016 at 11:13 AM, Michael.CTR.Tarullo [via ActiveMQ] <
ml-node+s2283324n4716062...@n4.nabble.com> wrote:
> Thanks Matt.
Thanks Matt. And yes I was aware of the behavior of CLIENT_ACK, although when
I started this research I was not. Before this I was under the impression that
it was a single message ack.
Michael Tarullo
Contractor (Engility Corp)
Software Engineer
FAA WJH Technical Center
(609)485-5294
-O
Thank you Tim.
Michael Tarullo
Contractor (Engility Corp)
Software Engineer
FAA WJH Technical Center
(609)485-5294
-Original Message-
From: tbai...@gmail.com [mailto:tbai...@gmail.com] On Behalf Of Tim Bain
Sent: Thursday, September 01, 2016 8:47 AM
To: ActiveMQ Users
Subject: Re: Need He
We had a rather unique situation some time ago where our message broker log was
recording the JMSException for an Invalid acknowledgement.
We traced it to the fact that the consumer of the message was using a more
recent version of ActiveMQ than our message broker was running (i.e. message
brok
Thanks Tim. I think I have resolved it. You are correct that it is a network
problem. We believe it is related to firewall issues on the two remote VM's
acting as the JMS clients.
Just so you know our network admins did confirm the existence of the firewalls
on the VM's and I also installed
I am trying to connect an ActiveMQ client to the ActiveMQ message broker.
I am running my client and the message broker on separate Linux VM's. The
message broker is started and I can access it with the ActiveMQ web console. I
can also ping the message broker VM from the client VM successfully
10 matches
Mail list logo