roadmap

According to http://activemq.apache.org/new-features-in-60.html, Apollo is "unofficially declared dead". What does that mean for ActiveMQ? Is there a new "next-gen" candidate/heir apparent? -- View this message in context: http://activemq.2283324.n4.nabble.com/roadmap-tp4703678.html Sent

LevelDB setup

I'm trying to setup a leveldb cluster on Redhat 3 node cluster. I have ActiveMQ 5.12.1 zookeeper 3.4.6 installed but I keep getting this error. INFO | Initiating client connection, connectString=appdev041.corp.local:2181,appdev042.corp.local:2181,appdev043.corp.local:2181 sessionTimeout=2000

Re: roadmap

Yeah... Kafka. On Wed, Nov 4, 2015 at 3:22 PM, rjrizzuto wrote: > According to http://activemq.apache.org/new-features-in-60.html, Apollo is > "unofficially declared dead". What does that mean for ActiveMQ? Is there > a > new "next-gen" candidate/heir apparent? > > >

Re: roadmap

All kidding aside though (that was kind of rude on my part) that page you link does mention https://activemq.apache.org/artemis/ as the possible next gen. Thanks! James On Wed, Nov 4, 2015 at 4:09 PM, James Carr wrote: > Yeah... Kafka. > > On Wed, Nov 4, 2015 at 3:22

Broker OOM

Hi list, We have recently upgraded the ActiveMQ broker on one of our test servers from version 5.9 to 5.12.1. After the upgrade, we get lots of OutOfMemoryErrors from the broker and the broker becomes unusable. We increased the JVM memory from 128 MB (which is sufficient on the 5.9 production

Re: Request to Subscribe

Were you looking for this information? http://activemq.apache.org/mailing-lists.html On Nov 4, 2015 2:51 AM, "Deepak A" wrote: > -- > -- > > Deepak >

Can not configure enabledCipherSuites in activemq with openjdk

We are migrating to openjdk and the configuration of enabledCipherSuites that worked in OracleJDK 1.8 does not work with openjdk 1.8: http://activemq.apache.org/ssl-transport-reference.html According to openjdk code

Re: What happens with JMSRedelivered when server moves message to DLQ

I'm not actually talking about the counter, but the Boolean flag 'JMSRedelivered'. Anyways, you're right that it should work when setting persistJMSRedelivered=true (I forgot about this option). Regarding the "poison cause", is it not possible for the client side to return a non-null cause?

Re: AMQ CPP Consumer Receive() and receiveNoWait() does not return

On Tue, 3 Nov 2015 11:08:29 -0800 (PST), JackOfAllTrades wrote: >All I can do at the moment > > > >auto_ptr factory( new ActiveMQConectionFactory >(MY_BROKER_URL)); > >cms::Connection* conxn=null; >conxn=factory->CreatConnection(); > >auto_ptr

Re: AMQ CPP Consumer Receive() and receiveNoWait() does not return

Where or how does one set the prefetch policy for each connection? -- View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-CPP-Consumer-Receive-and-receiveNoWait-does-not-return-tp4703485p4703668.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Request to Subscribe

-- -- Deepak

Re: What happens with JMSRedelivered when server moves message to DLQ

that is intended. the dlq enqueue is a new message. the poison cause property will have some good information but it would make sense to add a property that captures the value of that counter. the only issue is that the value is typically interpreted client side and remains 1 on the broker so it