-
15. Re: out-of-order messages after abrupt MDB termination
jmrecio May 9, 2013 11:19 AM (in response to ataylor)Thanks, Andy.
Not sure if the descriptions in the test case are very clear, I'll clarify if required.
-
16. Re: out-of-order messages after abrupt MDB termination
ataylor May 13, 2013 9:59 AM (in response to ataylor)fyi i have raised https://issues.jboss.org/browse/HORNETQ-1194 which may be the issue, should have a patch tomorrow
-
17. Re: out-of-order messages after abrupt MDB termination
jmrecio May 16, 2013 3:27 PM (in response to ataylor)Thanks, Andy, I'll test when available.
-
18. Re: out-of-order messages after abrupt MDB termination
clebert.suconic May 16, 2013 4:26 PM (in response to jmrecio)the fix has been merged already. maybe you could take a test?
-
19. Re: out-of-order messages after abrupt MDB termination
jmrecio May 17, 2013 6:27 PM (in response to clebert.suconic)You're right, Clebert, I realized right after replying.
I tried to deploy last 2.3.x over AS-7.2.0 but failed (probably my bad), so I have tested over AS-7.2.0.Final with a patched hornetq-2.3.0.CR1, it now works as expected, I can not reproduce the issue. Very good, excellent job.
As I think the patch is also valid for 2.2.x, I plan to patch a 2.2.x release and test over AS 5, I will post feedback.
Again, very good and thanks for the excellent support.
-
20. Re: out-of-order messages after abrupt MDB termination
clebert.suconic May 17, 2013 6:30 PM (in response to jmrecio)I don't remember if Andy has back ported this into the 2.2 branches will let him answer that... (I'm just lazy to try git log now ... Friday night! )... The releases on 2.2 branches are on EAP BTW.
-
21. Re: out-of-order messages after abrupt MDB termination
jmrecio May 19, 2013 5:38 AM (in response to clebert.suconic)Patch was over 2.3.x, but it is so simple (just one line ...) that I can easily apply it to 2.2.x.
I have tested on a patched 2.2.24 and behaviour doesn't appear, very good.
(I understand the patch won't be ported back to 2.2.x branches, no problem, if required I can maintain it myself, that's the joy of open source)
-
22. Re: out-of-order messages after abrupt MDB termination
clebert.suconic May 19, 2013 12:07 PM (in response to jmrecio)I would recommend you use a fork on github and keep tags for what you have in production. Say if you ever need us to look at a stack trace you can send us the GitHub account name and the tag you are using. We can't of course officially support it but we do our best to find issues.
-
23. Re: out-of-order messages after abrupt MDB termination
clebert.suconic May 19, 2013 12:07 PM (in response to clebert.suconic)Also keep version.propertties aligned with your branch
-
24. Re: out-of-order messages after abrupt MDB termination
jmrecio May 20, 2013 8:04 AM (in response to clebert.suconic)Thanks, Clebert, I am doing more or less that, but with a private git repo, your suggestions make a lot of sense.