"javax.jms.InvalidClientIDException" with maxConnection in pooledConnectionFactory

Hi, ActiveMQ Broker: 5.8 I am using "*PooledConnectionFactory*" with "*maxConnections = 20*" for my java consumer. According to my understanding: Broker will allow consumer to have 20 connection at a time if it is required. Question: My Consumer is subscribing to a topic with durable subscript

Re: Activemq heap space issue activemq 5.8 c/stomp

Uploading the leak suspects details: leak_suspects.png -- View this message in context: http://activemq.2283324.n4.nabble.com/Activemq-heap-space-issue-activemq-5-8-c-stomp-tp4680436p4680548.html Sent from the ActiveMQ -

activemq master/slave with replicateddb - switch master

Hello, We have auto installer for zookeeper and activemq. When we update activemq it takes down one node at a time and updates it. If first node is master it will take down activemq and all the services that reply on availability of activemq untill other node takes over as master. Inshort we see d

Re: org.apache.activemq.broker.region.Queue.doBrowse never returns

Think u just need to apply the fix to your branch or build trunk. The fix is https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=9c247160 On 24 Apr 2014 17:29, "matteor" wrote: > I really appreciate your quick reply gary. Thanks. > > So it seems to me that a possible solution would

Re: org.apache.activemq.broker.region.Queue.doBrowse never returns

I really appreciate your quick reply gary. Thanks. So it seems to me that a possible solution would be trying to create a patch for this, right? Could I create an issue with a tentative patch? -- View this message in context: http://activemq.2283324.n4.nabble.com/org-apache-activemq-broker-re

Re: org.apache.activemq.broker.region.Queue.doBrowse never returns

it should not exceed the maxBrowsePageSize so any infinite loop is a bug :-( and I think one of the unit tests showed that bug up in a non standard env, just a little too late. On 24 April 2014 17:03, matteor wrote: > Hi! thanks for the response. > > Actually I activated periodic expiry checking

Re: INDIVIDUAL_ACKNOWLEDGE with a durable consumer

maybe use a transacted session for your consumer and only commit when you are happy. On 24 April 2014 16:15, meurwinn wrote: > Hi, thanks. > We persist messages in LevelDB storage. > > We needs this functionnality pretty soon in production so i think we have to > find another solution while you'r

Re: org.apache.activemq.broker.region.Queue.doBrowse never returns

Hi! thanks for the response. Actually I activated periodic expiry checking on purpose since we have massive message production and this is a way to tame the memory usage. I'll try with the maxBrowsePageSize and maxExpirePageSize settings. Anyway, do you think this infinite while loop is the expec

Re: org.apache.activemq.broker.region.Queue.doBrowse never returns

looks like the fix in not in 5.9.1 u need the workarounds or https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=9c247160 On 24 April 2014 16:44, Gary Tully wrote: > hmm. that is the result of the fix for > https://issues.apache.org/jira/browse/AMQ-4930 > > the intent is to limit a

Re: org.apache.activemq.broker.region.Queue.doBrowse never returns

hmm. that is the result of the fix for https://issues.apache.org/jira/browse/AMQ-4930 the intent is to limit a browse or expire check to available memory or max browse size. I think the fix is in 5.9.1 As a workaround, disable periodic expiry checking. policyEntry expireMessagesPeriod=0 and or co

org.apache.activemq.broker.region.Queue.doBrowse never returns

Version: AMQ 5.9.0 I'm dealing with a strange behavior of org.apache.activemq.broker.region.Queue.expireMessages() of org.apache.activemq.broker.region.Queue.expireMessagesTask. Basically this task stops working after few minutes after broker bootup. I tried to track down the source of the problem

Re: INDIVIDUAL_ACKNOWLEDGE with a durable consumer

Hi, thanks. We persist messages in LevelDB storage. We needs this functionnality pretty soon in production so i think we have to find another solution while you're working. Do you have any idea for an other way to do this or not ? Thanks for your help. -- View this message in context: http:/

Re: INDIVIDUAL_ACKNOWLEDGE with a durable consumer

hmm. this is a problem - see https://issues.apache.org/jira/browse/AMQ-3486 I reopened because I think kahadb can now handle this case ok but it needs some tests and some work to verify. On 24 April 2014 14:35, meurwinn wrote: > Ok, that's what i was thinking. > > So as i said, i want to ack or

Re: can we use store and dispatch with even levelDB and/or JDBC ?

found the answer: its only available for kahadb. thanks for reading :) -- View this message in context: http://activemq.2283324.n4.nabble.com/can-we-use-store-and-dispatch-with-even-levelDB-and-or-JDBC-tp4680521p4680522.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

can we use store and dispatch with even levelDB and/or JDBC ?

or is it only limited to KahaDB (given how it handles message persistence) ?? -- View this message in context: http://activemq.2283324.n4.nabble.com/can-we-use-store-and-dispatch-with-even-levelDB-and-or-JDBC-tp4680521.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: INDIVIDUAL_ACKNOWLEDGE with a durable consumer

Ok, that's what i was thinking. So as i said, i want to ack or not each message received in a session. The AUTO_ACK is not the good way and the CLIENT_ACK neither ("Acknowledging a consumed message automatically acknowledges the receipt of all messages that have been consumed by its session.").

Re: INDIVIDUAL_ACKNOWLEDGE with a durable consumer

the ack mode is only relevant to message consumers. have a read of http://docs.oracle.com/javaee/1.4/tutorial/doc/JMS6.html On 24 April 2014 13:41, meurwinn wrote: > Sorry but i really don't understand. > > I just need to ack or not each message received in a session that stay open > all the time

Re: WARN : AMQPersistenceAdapter - The ReferenceStore is not valid - recovering

Hi All, I am facing issue with activemq 5.5.1 at production: activemq broker able to receive email into pendding queue but its not getting dequeue. i restarted the activemq server still its not dequeue and it shows me below message: >From activemq.log i got single line of WARN at the end is

Re: INDIVIDUAL_ACKNOWLEDGE with a durable consumer

Sorry but i really don't understand. I just need to ack or not each message received in a session that stay open all the time. So when in send a message to a durable topic, wich one ack mode does i need to use ? When i received a message from this durable topic, wich one ack mode does i need to

why message can't be consumed in apollo?

there are 400 consumers on a queue, and in the web ui, it says there are 526 messages. I clicked the message and it shows Messages(0) Sequence Codec Persistent Expires Prefetched Acquirer Size 17370 openwire true no false 217.78 kb what's wrong with it?

Re: Non persistent Messages Not getting expired even after expiration time exceeded

@art: Yes. If durable subscriber went offline, broker has to keep persistent or non persistent both message somewhere(tmp storage). So that when the subscriber comes up again, broker should be able to send the messages to subscriber. @raj: Test case is pretty simple. Steps: 1) Run a java consumer

Re: INDIVIDUAL_ACKNOWLEDGE with a durable consumer

s/Session.AUTO_ACKNOWLEDGE/Session.CLIENT_ACKNOWLEDGE/ and call javax.jms.Message#acknowledge when you are done with a received message On 24 April 2014 10:25, meurwinn wrote: > Hi, not shure to understand what you mean. > In my client code to consume the messages, i have : > > /ActiveMQConnecti

Re: INDIVIDUAL_ACKNOWLEDGE with a durable consumer

Hi, not shure to understand what you mean. In my client code to consume the messages, i have : /ActiveMQConnectionFactory factory = new ActiveMQConnectionFactory(serverUrl); connection = factory.createTopicConnection(userName, password); session = ((TopicConnection) connection).createTopicSession(

Re: INDIVIDUAL_ACKNOWLEDGE with a durable consumer

Use client ack mode? On 24 Apr 2014 09:36, "meurwinn" wrote: > Up, > any idea about how to process ? Or any explain. > I can't find any documentation about the way to follow... > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/INDIVIDUAL-ACKNOWLEDGE-with-a-durable

Re: INDIVIDUAL_ACKNOWLEDGE with a durable consumer

Up, any idea about how to process ? Or any explain. I can't find any documentation about the way to follow... -- View this message in context: http://activemq.2283324.n4.nabble.com/INDIVIDUAL-ACKNOWLEDGE-with-a-durable-consumer-tp4680403p4680505.html Sent from the ActiveMQ - User mailing list

delay failover transfer

Hi guys. I am using failover + broker network for disaster transfer. So i config two brokers using static network and on client side i specifies failover like this. failover:(tcp://localhost:61617,tcp://localhost:61618)?randomize=false) My question is, when i kill the main broker, I may need the