The following is the use case:
The application is currently running as one standalone server (no cluster)
in production. We do not currently have a need to make it to run wildfly in
cluster mode, but we do have concern over a sudden shutdown of the wildfly
instance and no backup. In addition, we n
> I was trying to do similar things with data replication provider, but found
> the remaining messages were not processed by the newly elected HA singleton
> provider, and seemed to be lost. I am not sure if this is doable.
You'll have to go into more detail here for me to help further. A full
d
Thank
A+JYT
--
View this message in context:
http://activemq.2283324.n4.nabble.com/system-property-tp4715105p4715446.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi Justin,
I was able to test the scenario with collocated shared-store approach with
two wildfly instances which are set up as HA singleton (only one wildfly
will be active at anytime). The following is the configuration
wildfly #1 (master1 activemq + slave1 activemq)
wildfly #2 (master2 activem
I have two consumers and Every consumer has 4 threads.
I'm use two broker to from cluster:
There are 3000 message have dispatched on server168 and 2000 message on
server167
Im using the default prefetch size
I adjusted the parameters being observed.
Thanks
--
View this
i also done the test on CentOS and it's works fine when i change the
password after restart.
Kind regards.
*BENNOUR HASSEN*
*SOA **Architect **/ **Java **Software Engineer*
2016-08-11 21:27 GMT+02:00 Hassen Bennour :
> I tested that on windows
> Le 11 août 2016 21:26, "Hassen Bennour" a
> é
Hello Hassem,
Thank you for the support. I found out the issue. Just for the record the
only change needed was to modify the jetty-realm.properties. My issue was
that I had 2 versions activemq-5.10 and activemq-5.11 in the server. I
deleted the older version and the changes where finally applied.
