Re: Non_persistent messages and qpid-jms-client-0.20.0.jar or higher.

Thank you for the quick response, Tim. I'm indeed confronted with the same problem as described in https://issues.apache.org/jira/browse/AMQ-7189. The JMS transformer is, as you indicated, the perfect workaround. Patrick --- -- Sent from:

Non_persistent messages and qpid-jms-client-0.20.0.jar or higher.

I'm not able to send non_persistent messages to an ActiveMQ broker (5.15.3) with version 0.20.0 or higher of the qpid-jms-client library. The messages are shown as persistent on the console and they behave also as persistent. Sending non_persistent messages with the qpid-jms-client 0.11.1 or lower

The ActiveMQ Web Console doesn’t support a plus (+) sign in the ClientID.

I’m trying to use an ISO 8601 date/time as part of the ClientID. For example : connection.setClientID("|2017-08-01T09:20:18.936+03:00"); The following error is generated when clicked on the url in the Web Console | Connections page : "No connection could be found for ID |2017-08-01T09:20:18.936

Re: How to Force a Connection Failover in an ActiveMQ Replicated LevelDB Cluster ?

The JMX operations "stop", "start" (or "restart") on the Master Broker do the job. -- View this message in context: http://activemq.2283324.n4.nabble.com/How-to-Force-a-Connection-Failover-in-an-ActiveMQ-Replicated-LevelDB-Cluster-tp4720385p4720571.html Sent from the ActiveMQ - User mailing

How to Force a Connection Failover in an ActiveMQ Replicated LevelDB Cluster ?

Currently I stop the ActiveMQ Master Node (by a systemd service) to force a Slave become the new Master. Afterwards I restart the stopped ActiveMQ Master Node (by a systemd service) which will become a new Slave. Is there another way to Force a Connection Failover without stopping and restarting

Re: Problem with setting JMSCorrelationID in ActiveMQ 5.14.1 with java Qpid client.

I had used client version 0.9.0. And I had used the JMSMessageID of an incoming message. I have redone my test with client version 0.11.0 and now the JMSCorrelationID is set correctly ! -- View this message in context:

Problem with setting JMSCorrelationID in ActiveMQ 5.14.1 with java Qpid client.

When the JMSCorrelationID starts with 'ID:' then 'ID:' is trimmed when setting the JMSCorrelationID with a java Qpid client. For me it is unexpected behavior but does anyone know the reason for that ? Patrick -- DISCLAIMER http://www.tvh.com/glob/en/email-disclaimer "This message

Re: A configured queuePrefetch of one in ActiveMQ 5.14.1 with AMQP 1.0 behaves like a queuePrefetch of two.

Great idea ! But I don't experience any improvement with a usePrefetchExtension set to "false". I don't know of the broker destination policy settings in general work together with an AMQP client ? -- View this message in context:

Re: A configured queuePrefetch of one in ActiveMQ 5.14.1 with AMQP 1.0 behaves like a queuePrefetch of two.

I have opened JIRA https://issues.apache.org/jira/browse/AMQ-6530. I will certainly try ActiveMQ 5.14.2 at the moment it is released ! -- View this message in context:

Re: A configured queuePrefetch of one in ActiveMQ 5.14.1 with AMQP 1.0 behaves like a queuePrefetch of two.

Your explanation is very valuable and completely correct in my opinion. Nevertheless there are some differences concerning the queuePrefetch between version 5.14.1 and 5.13.3. The Dispatched Queue contains maximum one message in 5.13.3 with a queuePrefetch of one and that at any point in time.

A configured queuePrefetch of one in ActiveMQ 5.14.1 with AMQP 1.0 behaves like a queuePrefetch of two.

I'm talking about queues with a low message volume and high processing time. In such a setup is it important that messages are not "heaping up" in the dispatch queue. The queueprefetch must be one in order to keep it workable. I have done some tests with an ActiveMQ 5.14.1 broker and an AMQP

Re: StorePercentUsage increasing above 100% for slaves in ActiveMQ Replicated LevelDB Cluster (5.14.1).

Tim, I have submitted a bug report in JIRA : https://issues.apache.org/jira/browse/AMQ-6502 Patrick -- View this message in context: http://activemq.2283324.n4.nabble.com/StorePercentUsage-increasing-above-100-for-slaves-in-ActiveMQ-Replicated-LevelDB-Cluster-5-14-1-tp4719072p4719105.html

StorePercentUsage increasing above 100% for slaves in ActiveMQ Replicated LevelDB Cluster (5.14.1).

The StorePercentUsage of the master node is increasing and decreasing but remains more or less stable over the time. The StorePercentUsage of the slave nodes (JMX), on the other hand, is increasing all the time. I have already noticed values of 200% and more. The HA Cluster seems to work and I

Re: Consuming problem with topics in ActiveMQ 5.14.1 with AMQP Qpid client.

Hi Tim, I have submitted following JIRA bug report : https://issues.apache.org/jira/browse/AMQ-6500 Patrick -- View this message in context: http://activemq.2283324.n4.nabble.com/Consuming-problem-with-topics-in-ActiveMQ-5-14-1-with-AMQP-Qpid-client-tp4718988p4719067.html Sent from the

Consuming problem with topics in ActiveMQ 5.14.1 with AMQP Qpid client.

There could only be 500 topic messages be consumed with the AMQP Qpid client with ActiveMQ 5.14.1. We get the following situation (subscriber info) at the moment a subscriber connects with the Qpid client. The Inflight value becomes -1000 what is very strange. Pending Queue Size | Inflight |

Authorization problem in Apache Apollo

I have a problem with configuring the access control rules in Apache Apollo. Everything works fine when I don't use the attribute id or when the attribute id="*". At the moment that I want to use a real queue name for the attribute id then it goes wrong. What format does the attribute "id"