Re: Unmatched acknowledge: MessageAckExpected - message count (1) differs from count in dispatched-list (2)

Hi Tim, Thanks for the reply. I already submitted this as a bug in JIRA, see https://issues.apache.org/jira/browse/AMQ-6622 , but no one responded there so I had to cross post on the forum. I would like to know if there is any workaround for this

Re: Unmatched acknowledge: MessageAckExpected - message count (1) differs from count in dispatched-list (2)

Please submit this as a bug in JIRA. Tim On Mar 12, 2017 11:48 PM, "xabhi" wrote: > Observed below exceptions in STOMP consumer after failover. The consumer > continued to receive messages but this exception kept coming on both client > and server side and when the master activemq instance took

Re: Unmatched acknowledge: MessageAck (start of ack) in XA transaction initiated by Oracle Service Bus

Hello Ionut, The jms.prefetchPolicy.all=0 is not work for me. if I set jms.prefetchPolicy.all=0, the MDBs can't consume messages. My activemq is Master-slave(using embeded borker in jboss), the consumers(MDBs) are distrubited in cluster nodes. When broker fails, new master is starting up. there i

Re: Unmatched acknowledge: MessageAck (start of ack) in XA transaction initiated by Oracle Service Bus

Hello aphor, I managed to get it working by doing the following 2 things: 1. In the JNDI provider on the Weblogic server in the provider URL I used the property *jms.prefetchPolicy.all=0* i.e. tcp://:61616?jms.prefetchPolicy.all=0 2. In the OSB proxy flow if you have a "Service Callout" or a "Pub

Re: Unmatched acknowledge: MessageAck (start of ack) in XA transaction initiated by Oracle Service Bus

Did you get solution? I got similar issue and post at http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-after-failover-td4719934.html -- View this message in context: http://activemq.2283324.n4.nabble.com/Unmatched-acknowledge-MessageAck-start-of-ack-in-XA-transaction-initiated-by-O

Re: Unmatched acknowledge: MessageAck

but i'm already using AMQ 5.11.1 and i have this issue (end of ack) not (start of ack) which solved by AMQ issue 5476 lastMessageId = ID:QVM1-59072-1431443299564-14:1:5:1:2, destination = temp-queue://ID:QVM1-59068-1431443290141-4:1:2, transactionId = null, messageCount = 1, poisonCause = null}; Co

Re: Unmatched acknowledge: MessageAck

It's similar, but a) Salma's running 5.11.1 which has that fix, and b) the bug references "start of ack" whereas this stack trace references "end of ack". I've been hoping Gary will throw out some insight here based on his fix for that issue, since they could easily be very similar problems with s

Re: Unmatched acknowledge: MessageAck

Problably related to https://issues.apache.org/jira/browse/AMQ-5476 ? Do you use batch processing and different message priorities? -- View this message in context: http://activemq.2283324.n4.nabble.com/Unmatched-acknowledge-MessageAck-tp469641

Re: Unmatched acknowledge errors in pure master slave configuration with activemq 5.5

I have the same problem. Is there any way to get rid of this annoying error message?. Is this a bug? cheers -- View this message in context: http://activemq.2283324.n4.nabble.com/Unmatched-acknowledge-errors-in-pure-master-slave-configuration-with-activemq-5-5-tp3548344p4176403.html Sent from th

Re: Unmatched acknowledge

thanks for completing the loop on this one with your reply :-) On 21 November 2010 05:37, Andre vd Merwe wrote: > Hi, > > For anyone else having this problem; > > I originally circumvented the issue by using the event based interface. > > However I have found the correct way of pulling a message

RE: Unmatched acknowledge

Hi, For anyone else having this problem; I originally circumvented the issue by using the event based interface. However I have found the correct way of pulling a message on demand from multiple threads. Simply use the INDIVIDUAL_ACKNOWLEDGE acknowledge mode. From: http://activemq.apache.org/