Re: Configuring peer transport with shared data directory

2016-12-08 Thread JordanC
Just to clarify, I won't have multiple brokers running on the same JVM. Each broker will be running on a separate JVM instance along with my J2EE application. Thank you for the suggestion about master/slave Tim. I am now trying to use master/slave as follows to support the high availability needed

Re: [!!Mass Mail]Re: Regarding replicated DB store solutions

2016-12-08 Thread Clebert Suconic
There are a many users using it in production. Artemis had the first release In may 2015 so it is been some time under load. you need to test it just like any software as you of course need to configure it properly to your needs. On Thu, Dec 8, 2016 at 9:26 AM, JR John Roach (5298) wrote: > Tha

VMTransport threading

2016-12-08 Thread rsargant
Hi, We have ~100 remote brokers establishing a duplex SSL network connector to a single central "hub" broker. We use this for store and forward of messages in both directions. All JMS consumers and producers execute in-process against their local broker and JMS resources are pooled with PooledCo

Re: [!!Mass Mail]Re: Regarding replicated DB store solutions

2016-12-08 Thread JR John Roach (5298)
Thank you for that information it cleared up a lot of things, I was a little hesitant on implementing Artemis in a production environment. Have an awesome day! John -Original Message- From: Christopher Shannon Reply-To: "users@activemq.apache.org" Date: Wednesday, December 7, 2016 at

JmsConnector.doConnectorInit() suppresses exceptions

2016-12-08 Thread DraCzech
*Configuration:* Hi, I'm using ActiveMQ 5.14.1 to connect from a device (running linux derivate OS) to Azure IoT Hub. With Qpid JMS client 0.11.1 providing AMQPS based JmsConnection implementation. I'm using Destination bridges to connect my local queues to remote queues. And connection state is ha

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

2016-12-08 Thread Timothy Bish
On 12/08/2016 07:24 AM, Patrick Vansevenant wrote: 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: http://acti

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

2016-12-08 Thread Patrick Vansevenant
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: http://activemq.2283324.n4.nabble.com/A-configured-queuePrefetc

Acrivemq-rar failover - consumer stop to consume messages

2016-12-08 Thread aphor
Hi All,I use embeded broker in jboss eap 6.4. when failover occured, I got following exceptions.Attached log, thread dump file on new master node. thread_dump_1208.txt activemq.log

Re: Possible loop after enabling DEBUG?

2016-12-08 Thread sealy
mf wrote > Yes, > confirmed. > Just setting 'log4j.logger.org.eclipse.jetty' to DEBUG breaks web console. > > Looks like same problem with 5.13 and 5.11.3, have not checked further. > > Mats hi, i've met the same problem with you. Please tell me the problem solved or not, and how to solve it. Th

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

2016-12-08 Thread lichtin
What about setting the usePrefetchExtension policy to "false"? Then the broker will wait for the consumer to acknowledge that the message is processed before refilling the prefetch buffer. tabish...@gmail.com wrote > On 12/07/2016 05:09 PM, Patrick Vansevenant wrote: >> I have opened JIRA https:/

Re: Possible loop after enabling DEBUG?

2016-12-08 Thread mf
The problem is not solved and no workaround apart from not setting the 'DEBUG' value. It would be useful to find out my original problem trying to debug setting up LDAPS auth for web interface logins. I'm not sure how to file a bug or if I have to... -- View this message in context: http:/