What is the proper way to acknowledge a message in a REST Push Consumer?

[kevingscott111]

I have a REST API that is accepting messages from a HornetQ via a Push configuration.  Everything is working great, except that the messages are not getting acknowledged and so they continue to show in the Delivering Count field on the queue and eventually cause new messages to block (once the queue fills).  My question is what is the proper way to acknowledge this messages?  I looked through the documentation and see that if you are doing a pull consumer there is a header that gives an address to send acknowledges, but I do not see that header on the messages I am getting from hornet.  Currently, my API is responding with just an HTTP 200, is there another code that could be used to indicate a successful message?

[jbertram]

Messages sent from a push subscription to a URL are automatically acknowledged if the push is successful.  You can turn on debug level logging for org.hornetq.rest.HornetQRestLogger to see details of this.  It would be helpful to see this logging if the message is not being acknowledged appropriately.

[kevingscott111]

Hi Justin,

Thanks for the response.  I tried to turn on the logging for the HornetQRestLogger but I'm still seeing any more logging.  Do you have example of turning the logging level on in JBoss 6?

I tried setting the loggers line in logging.properties thus:

loggers=org.jboss.system.server.ServerInfo,org.hornetq.rest.HornetQRestLogger

Thanks

[jbertram]

Are you talking about JBoss EAP 6 or JBoss AS 6?

[kevingscott111]

Sorry for the confusion.  It's JBoss AS 6.1

[jbertram]

The logging configuration for JBoss AS 6.1 is in <JBOSS_HOME>/server/<profile>/deploy/jboss-logging.xml.

Also, what version of HornetQ are you using?  This may change the logger name I indicated previously.

[kevingscott111]

Unfortunately, we are stuck on HornetQ 2.2.14 because that's what our business partner is using

[jbertram]

Technically speaking, things are a bit different in later versions but the semantics are roughly the same - the message should be acked if the URL push succeeds.  However, the logging category would be "org.hornetq.rest.queue.push.PushConsumer".

[kevingscott111]

Hi Justin,

Thanks for your help, I increased the logging level for PushConsumer and now I see messages in the log like

2015-03-12 14:43:43,216 DEBUG [org.hornetq.rest.queue.push.PushConsumer] (Thread-0 (group:HornetQ-client-global-threads-770715614)) Acknowledging: 40802189549

However, the new message still shows up in the "Delivering Count" in the JMS Queues screen of the Admin Console, so I believe that they aren't being acknowledged.  Are there other classes that I should try to increase logging for?

[jbertram]

Looking more closely at the code I believe I see a problem.  The message is being acknowledged, but the session used to consume the message is created with autoCommitAcks = false and the session is never committed by the PushConsumer which means the message is never truly acknowledged.  I see now that this problem was already fixed upstream and that's why the code is different.  I recommend you and your business partner upgrade.

[jbertram]

Here's the JIRA related to the problem https://issues.jboss.org/browse/HORNETQ-1091.  It was reported and fixed in November 2012.

[kevingscott111]

Justin Bertram wrote:

.  I recommend you and your business partner upgrade.

Yea, I think we are going to have to.  Thanks for your help!