3 Replies Latest reply on Jan 28, 2013 11:29 AM by jbride

ack a consumed hornetq core message

jbride Jan 23, 2013 7:59 PM

Hi,

this post is in regards to the onMessage(....) function of the Hornetq InboundHandler.java

when working with the Hornetq Core API, i'm pretty certain that the clientMessage.acknowledge() function needs to be explicity invoked

otherwise, consumed messages are never ack'ed and flushed from the queue.

ackBatchSize seems to take affect once consumed messages are explicity acknowledged

i'm observering this behavior (consumed messages not being flushed from the queue) with Switchyard 0.7.0.Final layered in domain mode on EAP 6.0.1 (which uses Hornetq 2.2.23 )

thanks!

jeff

1. Re: ack a consumed hornetq core message

igarashitm Jan 23, 2013 9:35 PM (in response to jbride)

Hi Jeff,

Since it's working without acknowledge() on AS7.1.1, the behavior may be changed in EAP. Could you file a JIRA so that we can remember your suggestion when we hit it?

Thanks,
Tomo
1 of 1 people found this helpful
Actions
2. Re: ack a consumed hornetq core message

kcbabo Jan 24, 2013 9:45 AM (in response to igarashitm)

Thanks for pointing this out, Jeff. I would use the Camel JMS gateway or the JCA gateway to talk to HornetQ instead. You should get equivalent functionality through those gateways, but if you see something missing, please let us know.

We are going to remove the HornetQ gateway from our distribution in the 0.8 release:
https://issues.jboss.org/browse/SWITCHYARD-1270
Actions
3. Re: ack a consumed hornetq core message

jbride Jan 28, 2013 11:29 AM (in response to kcbabo)

Keith / Tomo .... thanks for the tips.
i switched to the SY jca-inflow as recommended and the consumed message is now successfully getting de-queued in the remote hornetq broker.
all is well

thanks again! jeff
Actions

Go to original post