For all configurations of ActiveMQ 5. X, it will take effect only after the service is restarted？

Hi When i use activemq，i hava to change some configuration,for example :add users, change transportConnector port. Complete the above modification in the activmq. XML file.I have to restarted the broker and this change can effect. Why in this way of design, It's troublesome to use this way,Can't

?????? Use jolokia to read messages from the queue, up to 400 messages??

Thanks??After your explanation, there is really no need to read too much message content --  -- ??: "users"

Artemis clusters and large messages

Hello, I'm testing the handling of large messages in an Artemis cluster, while using CORE protocol everywhere. My messages are up to 1Mb, but I want to keep them in memory, not as large messages, so I'm using the option 'minLargeMessageSize=100' in the client connection-url. And also in the

Re: Cannot detect closed session from client

> Is the consumer connection factory configured to retry connections after a failure? No. > For JMS, the best way for an application to detect a lost connection is via the ConnectionListener. Did you mean ExceptionListener? If so, that's only relevant for connection problems which is not the iss

Re: Cannot detect closed session from client

Is the consumer connection factory configured to retry connections after a failure? If so, in the test, is there some additional step that prevents the client from reconnecting? For most applications, I recommend that consumers try indefinitely without interrupting the application. Any logic pla

RE: Cannot detect closed session from client

Thanks, opened: https://issues.apache.org/jira/browse/ARTEMIS-3351 Closing the connection does throw an exception as expected, so the issue is related to closing the session. > This looks like a bug to me. Can you open a Jira [1]? > In the meantime it looks like you can close the *consumer* via t

Re: Cannot detect closed session from client

This looks like a bug to me. Can you open a Jira [1]? In the meantime it looks like you can close the *consumer* via the web console instead of the session. That should trigger an exception on the client as expected. Justin [1] https://issues.apache.org/jira/projects/ARTEMIS On Wed, Jun 16, 20

Cannot detect closed session from client

Hello, I am using Artemis 2.17.0. I am trying to see how to detect a closed session from a client consumer. My use case is this: * Create a consumer (using JMS or core, same behavior) * I use a thread to loop indefinitely using consumer.receive(1000); * I create a producer and

Re: Truncated messages in 5.16.1 when using Postman

Andrew, Let me make sure I'm understanding the specific question. I think you're saying that messages are traversing the broker as expected, but that logging of messages larger than 64KB is now outputting the message bodies in debug log lines in a way that is different from the behavior under 15.1

Re: Use jolokia to read messages from the queue, up to 400 messages？

That matches my understanding: the queue browser is meant to be a way to view small numbers of messages from among those that would be consumed next, not a way to view every message in a huge queue. If you need that ability, one option is to use the JDBC backing store type, since then you can quer