-
1. Re: Will HornetQ hit the filesystem if sending a non-persistent message?
Pavel Myshkin wrote:
My question is what if I want to use HornetQ as the JMS RA in JBoss AS and leverage it as a job executor for asynchronous jobs. Will HornetQ make hits to the files system from some self-management considerations if I submit jobs as non-persistent messages?
Thank you,
Non persistent messages wont be written to disk if thats what you mean
-
2. Re: Will HornetQ hit the filesystem if sending a non-persistent message?
Yes, thats right, but thats not what I mean.
For example: JBoss MQ could be hitting the DB tables even on receiving a non persistent message. I just want to be sure that it is not happening with HornetQ.
Any one can assert that HornetQ is not accessing its files on filesystem for any reason upon receing a non-persistent message?
-
3. Re: Will HornetQ hit the filesystem if sending a non-persistent message?
1 of 1 people found this helpfulwell if you are using a transaction then the transaction data would be written to disk.
-
4. Re: Will HornetQ hit the filesystem if sending a non-persistent message?
Thank you,
Can I bother you Andy for a short explanation as to why there is a need to persist stuff to disk about a non-persistent transactional message?
-
5. Re: Will HornetQ hit the filesystem if sending a non-persistent message?
Just set persistence-enabled to false, if you don't want anything persisted to disk.
See user manual for more info
-
6. Re: Will HornetQ hit the filesystem if sending a non-persistent message?
1 of 1 people found this helpfulPavel Myshkin wrote:
Thank you,
Can I bother you Andy for a short explanation as to why there is a need to persist stuff to disk about a non-persistent transactional message?
This is a requirement from XA.
If you prepared a XA transaction branch that contained nothing but non persistent operations, and you didn't record that branch to disk, then if the server later crashed before committing, then recovered, the transaction manager might try to resolve the branch, but no trace of it would exist, and you'd get an XA error, and the transaction would remain unresolved.