As noted in the docs currently redistribution requires ON_DEMAND. There is
already a JIRA [1] to change this.
All things being equal, this would be really easy to implement with just a
few changes to
org.apache.activemq.artemis.core.postoffice.impl.BindingsImpl. However, it
would be inadvisable to
As a newbee on Fedora 30 I installed Artemis ActiveMQ. I created a broker in
/var/lib/broker. So far everything works fine but when I start the broker
every 5 seconds I get the following message in the logfile.
2019-11-06 15:21:55,552 WARN [org.apache.activemq.artemis.core.server]
AMQ16: Secu
Hi,
I have set up a symmetrical Artemis cluster, running with lots of different
clients and addresses. I want the clients to be able to connect to any of
the brokers and receive messages sent to any other broker in the cluster. As
such, it is is configured with message-load-balancing "ON_DEMAND" a
Near the bottom of the second link there's information about how to turn on
SSL debug on the broker, which the page says will let you "see what goes
wrong and why you get connections closed." If you didn't already try that,
I'd start there.
But ultimately the question is which SSL ciphers your ver
Thanks for the update !
Great you figured it out and always happy to help.
Regards
JB
On 05/11/2019 16:27, Jonathan Roby wrote:
> Hi All
>
>
> just an update: I figured out the issue. It was due to the software we use
> (fedora-commons/tomcat) using its own set of configuration files and dat
Great, I'm glad you got it sorted out. Thanks for closing the loop and
letting us know.
Tim
On Tue, Nov 5, 2019, 8:27 AM Jonathan Roby
wrote:
> Hi All
>
>
> just an update: I figured out the issue. It was due to the software we
> use (fedora-commons/tomcat) using its own set of configuration f
> We have configured to use NIO journal, but we used MAPPED on our previous
tests
Just curious, why you've changed from MAPPED?
If possible, try ASYNCIO if you need disk failure guarantees
(journal-datasync = true), for performance reasons.
Choose NIO if OS won't alow to use ASYNCIO, falling b
> 1) Which type of journal are u using?
We have configured to use NIO journal, but we used MAPPED on our previous
tests
> 2) Have you tried NIO or Mapped to see if is happening the some with them?
We've experienced same kind of performance on both
--
Sent from: http://activemq.2283324.n4.nab
