I all.
I'm trying to continue my troobleshooting..
I downgrade to activemq 5.5.1 because we used this version production and it
seems the problem is still observable.
With the old logger, I have a trace now: with a
concurrentModificationException.
Please, any help ?
mai 14, 2019 3:32:26 PM
org.a
Hi guys
A small up ! :-)
Any idea ?
TKs
denis
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi guys,
Here is the source code and associated unit tests.
https://github.com/denisbrondy/testactivemqnob
denis
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I will try to send you the unitary tests, however I have additional logbooks
hereafter.
Really confusing myself...It occurs after 50 successive calls when using
half duplex in between the two brokers. If I switch to only one DUPLEX, it's
fine.
===
THIS ONE IS FINE
=
Hi Tim,
Tks for your reply.
Ok for Config 2 not recommended but I agree config 1 and 3 should behave the
same.
I'm not using durable subscriptions, no persistency at all, only classic bus
capabilities.
I'm performing the same tests for all configuration and have clearly some
different results.
Hi guys,
I'm facing a very strange problem. I tested multiple versions of ACTIVEMQ
and I'm still seeing this issue on 5.15.9.
The setup is the following.
I have component which exposes a service interface with one basic method
which only perform a println. The exporter reads either a queue or a
