Re: JMSDestination value different between 5.12.1 and 5.13.0

BTW, the page you linked to says "Set by the producer." Can you please provide the source for the statement that it's set by the consumer in 5.13.0? On Mar 28, 2017 9:35 AM, "Timothy Bish" wrote: > On 03/28/2017 10:32 AM, chiippy wrote: > >> Per the activeMQ message Properties definition : JMSD

Configure paging in Activemq 5.14.3

Hi, I am using Activemq 5.14.3 as a messaging subsystem for JBoss. I need to configure paging and drop policies in Activemq. I would like to know if Activemq 5.14.3 supports paging. If so, how do i configure it in Activemq 5.14.3 ? Thanks, Sudharsan -- View this message in context: http://act

Re: Artemis 2.0 client migration from ActiveMQ 5.14

On Tue, Mar 28, 2017 at 2:04 PM, mtod wrote: > Thats strange then because it would fail unless I put in a queue that was > already created. I think there's a bug here.. I hit something similar today when performing performance tests using quiver with openwire: https://github.com/ssorj/quiver >

Re: Artemis 2.0 client migration from ActiveMQ 5.14

Thats strange then because it would fail unless I put in a queue that was already created. Thanks Mike -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-2-0-client-migration-from-ActiveMQ-5-14-tp4724150p4724210.html Sent from the ActiveMQ - User mailing list archiv

Artemis 2.0 in Karaf 4.1.0 accessing via Camel issues

I'm running Karaf 4.1.0 and Artemis 2.0 on AWS EC2. It's running fine but when I setup a camel route that connects to Artemis I get the following errors. org.apache.activemq -- Cannot be resolved org.apache.activemq.camel.component -- Cannot be resolved Question 1 - When running Artemis do I hav

Re: JMSDestination value different between 5.12.1 and 5.13.0

On 03/28/2017 10:32 AM, chiippy wrote: Per the activeMQ message Properties definition : JMSDestination However, since 5.13.0, the JMSDestination has been changed to be set by the Consumer instead of the Producer ? When using camel ac

Re: Artemis 2.0 client migration from ActiveMQ 5.14

It does create queues dynamic. You can turn on or off.. but it's on by default. On Mon, Mar 27, 2017 at 7:17 PM, mtod wrote: > Thanks I got the uri to work my prod ActiveMQ implementation has dynamic > queue creation Artemis does not have that turned on or at least I don't know > how to do that y

JMSDestination value different between 5.12.1 and 5.13.0

Per the activeMQ message Properties definition : JMSDestination However, since 5.13.0, the JMSDestination has been changed to be set by the Consumer instead of the Producer ? When using camel activemq, I have Producer : to("active

Re: master/slave Zookeeper setup for Kahadb.

http://activemq.apache.org/shared-file-system-master-slave.html has all the details of how to configure a shared file system KahaDB. On Mar 28, 2017 8:03 AM, "Tim Bain" wrote: > There isn't one. KahaDB can't be replicated; when you have master/slave > groups using KahaDB, they use shared storage

Re: master/slave Zookeeper setup for Kahadb.

There isn't one. KahaDB can't be replicated; when you have master/slave groups using KahaDB, they use shared storage where only the master has a lock to access it, and if the master dies then a slave locks the storage and becomes the master. Zookeeper is not involved. Tim On Mar 28, 2017 7:39 AM,

Re: Sending exception to client: ActiveMQNonExistentQueueException[errorType=QUEUE_DOES_NOT_EXIST message=AMQ119017: Queue jms.queue.queueName does not exist]

If a client fails to create a consumer there is no message loss as there are no messages involved in the operation. Any messages on the broker before the failure will still be there after the failure. Justin - Original Message - From: "jelmer" To: users@activemq.apache.org Sent: Tues

Re: Sending exception to client: ActiveMQNonExistentQueueException[errorType=QUEUE_DOES_NOT_EXIST message=AMQ119017: Queue jms.queue.queueName does not exist]

This exception is sent back to the client in response to the client attempting to create a consumer on a queue which does not exist. Couple of questions... 1) Are you using the 1.1 client with the 1.5.3 broker? 2) Is the client able to receive messages successfully? 3) Are you using a sing

Re: Artemis 2.0 : Client with v2.0.x jars in the classpath to a v1.5.x server. is it supported?

> Again, thanks for your help (And the good job on Artemis) Give us a Star on github for that!? :D https://github.com/apache/activemq-artemis/

master/slave Zookeeper setup for Kahadb.

Hi All, Currently we are using Leveldb in Activemq, since level db deprecated we need to switch over to Kahadb, so we want to know the master/slave Zookeeper configuration for kahadb. Like we have in replicatedLevelDB in Leveldb. Regards, Srinivas. -- View this message in context: http://acti

Re: Artemis 2.0 : Client with v2.0.x jars in the classpath to a v1.5.x server. is it supported?

Thanks for your answer Yes I'm aware of some change in this area and I understand why it has been changed. JMSToolBox (JTB) is an "universal" eclipse-rcp based JMS client that deals with JMS messages in Queues and Topics based on one eclipse pulgin per Queue Manager (Artemis, IBM MQ, ActiveMQ

Configure Broker to manage publisher

Hi, I want to know if we can confugre Active MQ Mqtt Broker in such a way that we can restrict a publisher to publish on a specific set of topics. i.e. If the publisher client is to publish message in topics 'a','b' and 'c' then that client cannot send any message on a new topic say 'd'. I know w

Re: Artemis 2.0 : Client with v2.0.x jars in the classpath to a v1.5.x server. is it supported?

Ah I see you are using the JMSManagement API. This goes beyond plain JMS and unfortunately is not supported in 2.0.0. It was one of the main reasons we needed to do a major release as the architecture change required removal of server side JMS components. You can do all the same stuff using the

Re: Sending exception to client: ActiveMQNonExistentQueueException[errorType=QUEUE_DOES_NOT_EXIST message=AMQ119017: Queue jms.queue.queueName does not exist]

P.S Extra question, when this logging is seen, does this mean a message is not sent (E.G dataloss?) -- View this message in context: http://activemq.2283324.n4.nabble.com/Sending-exception-to-client-ActiveMQNonExistentQueueException-errorType-QUEUE-DOES-NOT-EXIST-message-tp4724170p4724171.html

Sending exception to client: ActiveMQNonExistentQueueException[errorType=QUEUE_DOES_NOT_EXIST message=AMQ119017: Queue jms.queue.queueName does not exist]

As team, we are migrating from active mq artemis V1.1 to version 1.5.3. To test the queue, we turned on debug logging and then we got the following DEBUG trace. What does this loggin mean, we see nothing on the side of the client/consumer in terms of exceptions or warnings. We expected the queue to