HornetQ version is 2.5.0 final.
When I restart HornetQ in between (after bringing down the jboss), the no of messages on queue after broker restart are same as them before broker restart.
That durable on activation would be used only if this was a topic subscription.. which is not the case.
Can you try this on AS7? (just as a test)?
Make sure you enable persistence on the standalone.xml.
You can also take a look on what PrintData is showing. (If these messages are being ACKed or not):
java -Xmx2G -cp /path-to-jars/hornetq-logging.jar:/path-to-jars/hornetq-core.jar:/path-to-jars/netty.jar org.hornetq.core.persistence.impl.journal.PrintData /path-to-journal/bindins /path-to-journal/journal
This should tell you excatly what you have inside the journal.
Also: it was not clear to me if you're using the MDB in-vm or remotely.. it seems you removed the in-vm acceptor.
Take a look also at the consumer-window-size. It seems you need to disable client buffering.
Thanks for the reply.
Let me try out with setting consumer window size to 0. I was not aware of PringData. So couldnt find ACK logs. I will check on that.
I have remote MDB listening to queue. Since HornetQ is running as standalone and JBoss connecting to standalone HornetQ using JCA resource adapter. Is something wrong with the config?
I tried with consumer window size as 0. Still facing same problem.
Attaching PrintData logs when JBoss was brought down.
I set following in ra.xml
<description>The consumer window size</description>
Also on hornetq-jms.xml following is set.
This is very abrupt behaviour. Am i missing some configurations? I am attaching PrintData logs.
PrintData1234.txt.zip 567.8 KB
You didn't post your bindings.. you probably used a wrong directory.
it seems something weird on this:
### Message Counts ###
message reference count
queue id 81589,count=7346
queue id 7,count=8660
prepared message count=0
But I need to look at the bindings to what you have.
Maybe it would worth to try a checkout of the branch and buildling it?
Attaching PrintData logs with small set of 100 messages. Even with small set the problem is same. If I am reading the logs correctly, all the messages have been acknowledged. However I didint get them on MDB. There are absolutely no other consumers to this queue.
op.txt.zip 3.8 KB