That feels to me like there might still be something wrong in your
configuration, and maybe it only works with those two older versions of
ActiveMQ and Paho because they don't include the code that would recognize
that something's not right. I'd like to see what if anything Martin can
tell us about
Not that I'm aware of; I don't remember seeing any such requirement in the
release notes (and I'd be surprised if there was one, since we typically
bundle all necessary JARs). What version were you upgrading from?
Can one of you please write a bug in JIRA for this?
Thanks,
Tim
On Mon, May 22, 20
I see the same exact error after upgrading to version 5.14.5 and JDK
1.8.0_131. This happens when I try to get XML version of Queues and Topics
in ActiveMQ Web Console. Looks like this is related to JSTL libs. Do I need
to add other jars during install ?
--
View this message in context:
http://
Messages will go to the DLQ because the redelivery count is > the
configured. The message will be redelivered because the client
rejected it...
Different than OpenWire messages, messages are redelivered through the
server, always.. on OpenWire the client will redeliver the message and
the client w
There are currently no plans to add that feature. However, feel free to open a
JIRA and (even better) send a PR to implement the functionality.
Justin
- Original Message -
From: "vishal3007"
To: users@activemq.apache.org
Sent: Monday, May 22, 2017 11:32:45 PM
Subject: Re: ActiveMQ Arte
Also I am connecting the client to the "ws://0.0.0.0:1883" port instead of
the "ws://0.0.0.0:61615" port.
But even like this, with activemq 5.14.3 I still have the same problem
"client disconnecting in one second".
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Connectio
So if I understand correctly, you downgraded your Paho version from 1.1.1
to 1.1.0 and left the ActiveMQ version and your client code unchanged, and
everything started working. Is that right?
On May 23, 2017 3:06 AM, "aragoubi" wrote:
> Now it's working for me too Tim, I think it was a problem o
Hi Tim!
Answers inlined
Tim Bain wrote
> Shenandoah is aimed at large JVMs (the page that link points to says 20GB
> or bigger), so I wouldn't just go trying it without understanding what its
> strengths and weaknesses are.
Partially disagree, that link was only a fast overview of what Shena
Now it's working for me too Tim, I think it was a problem of activeMQ and
apache paho version compatibility. Maybe this is why threads were being
killed for me. Now I am using activeMQ 5.9.0 and apache paho 1.1.0 and it is
working fine.
--
View this message in context:
http://activemq.2283324.n
