-
1. Re: "Uncommitted transaction with id X found..." What does it mean?
clebert.suconic Oct 5, 2010 9:18 PM (in response to bobufuller30004)You killed the server before committs were accepted by the journal, when the journal restarted and reloaded, it couldn't find commit for those Transactions. and it will ignore them since it needs to guarantee ACID.
If you killed the server for a test that's a normal scenario.
-
2. Re: "Uncommitted transaction with id X found..." What does it mean?
bobufuller30004 Oct 5, 2010 9:34 PM (in response to clebert.suconic)Are journals (where the persistent messages are stored?) being used even if my queues are configured without paging or durability?
<address-setting match="myQueue">
<max-size-bytes>5242880</max-size-bytes>
<address-full-policy>DROP</address-full-policy>
</address-setting>
<queue name="myQueue">
<address>myQueue</address>
<durable>false</durable>
</queue>Thanks!
-
3. Re: "Uncommitted transaction with id X found..." What does it mean?
clebert.suconic Oct 5, 2010 10:10 PM (in response to bobufuller30004)1 of 1 people found this helpfulPersistent messages are always stored on the journal (after routed).
Read the paging chapter for more information.
-
4. Re: "Uncommitted transaction with id X found..." What does it mean?
clebert.suconic Oct 5, 2010 10:11 PM (in response to bobufuller30004)1 of 1 people found this helpfulSo, if you don't used paging, persistent messages will obviously be stored on the journal.
-
5. Re: "Uncommitted transaction with id X found..." What does it mean?
bobufuller30004 Oct 6, 2010 5:42 PM (in response to clebert.suconic)Hmm, ok, still a bit confused about how things work, but that's not unsual.
> If you killed the server for a test that's a normal scenario.
I'm not 'killing' the server, but using CTRL-C to cleanly shut it down. Does the WARN logging mean something in that scenario? Perhaps I've missed something to ensure HornetQ shuts down gracefully?
-
6. Re: "Uncommitted transaction with id X found..." What does it mean?
clebert.suconic Oct 6, 2010 5:55 PM (in response to bobufuller30004)Say you have your client holding forever on the commit, and then you shut down the server, you won't get the commit to the journal, when you restart that data will be rolled back.
The server will not wait you finish your transactions if you set it to shutdown.
If you see a scenario where you closed all your connections, committed all your data, you shutdown the system and still see those issues, I would recommend you to try trunk first, and if you still see an issue, please provide me a testcase.