In short, no. The "updateClusterClients" attribute is only supported by
OpenWire clients.
Justin
On Wed, Jun 26, 2019 at 8:51 PM Daniel Blando wrote:
> Hey all,
>
> I am wondering for each protocols the attribute "updateClusterClients"
> works. It does works for openwire. Does anyone know if
Hey all,
I am wondering for each protocols the attribute "updateClusterClients"
works. It does works for openwire. Does anyone know if it works for
STOMP, AMQP,
or MQTT?
Cheers,
Daniel
Yeah I thought about that. Updating ActiveMQ is a longer process for us
because multiple teams use it in a different ways. I've seen where some people
suggest removing the java.exe, javaw.exe executables from the windows\system32
folder and that seems to work. Those versions were reporting as
On 6/26/19 5:34 PM, Mike Garcia wrote:
Hi,
We just updated our systems to Java 8 and now ActiveMQ 5.14.2 fails to launch.
We get the following error message in the wrapper.log file when we try to
launch the ActiveMQ service:
Error: Registry key 'Software\JavaSoft\Java Runtime Environment'\
Hi,
We just updated our systems to Java 8 and now ActiveMQ 5.14.2 fails to launch.
We get the following error message in the wrapper.log file when we try to
launch the ActiveMQ service:
Error: Registry key 'Software\JavaSoft\Java Runtime Environment'\CurrentVersion'
has value '1.8', but '1.
Just re-discovered this...
I tested this scenario with 2.4.0 and the attached configs, and I couldn't
make it fail like described in the original message. Fail-over and
fail-back worked without any of the issues described.
> To us, this meant that the current master (which was the original slave)
hi all...
i am newbie trying to run some artemis examples... using artemis 2.9.0
with java 1.8.0_172. i run some examples successfully, but when i try
the examples for REST in examples\features\standard\rest i get the below
error when running mvn jetty:run
i looked at Substitutions$Target_Pa
Thank you Justin. I will try it when version 2.9 is included in a new wildfly
version.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
my application tracks new clients by listening to ActiveMQ.Advisory.Queue for
queue creation messages, once a queue is created then it listens to the
Queues advisory topic for a producer message and at that point starts a
listener on the queue.
After a certain time the broker gets into a state whe