-
1. Re: Co-located Failover/Failback Issue Wildfly 8.2.1
jbertram Apr 11, 2016 1:55 PM (in response to amsinha)Are you setting <check-for-live-server> as discussed in the documentation?
Also, if you really think there is a bug I recommend you reproduce on the latest version (which in this case would be Wildfly 10.0.0.Final).
-
2. Re: Co-located Failover/Failback Issue Wildfly 8.2.1
amsinha Apr 11, 2016 4:30 PM (in response to jbertram)Yes, <check-for-live-server> is set to be true on both nodes for each primary hornetq server (True for both wildfly 8.2.1 as well as EAP 6.4.0 environments)
is there anything else that can be done to either confirm or rule or if this is a bug or not?
And if this is to be a bug, Is trying with 10.0.0 the only path forward or would a bug patch to 8.2.1 be a possibility?
Thanks!
-
3. Re: Co-located Failover/Failback Issue Wildfly 8.2.1
jbertram Apr 11, 2016 9:29 PM (in response to amsinha)is there anything else that can be done to either confirm or rule or if this is a bug or not?
I personally do not have many resources to spend on an issue in a legacy release that may be fixed already upstream which is why I encourage you to reproduce the problem on a current release. If there actually is an issue that hasn't been fixed already then I'd have some motivation to investigate more and fix it. That said, my guess is that this is some kind of configuration error or incorrect expectation since EAP releases are run through a series of colocated, replicated tests before making it out the door. Colocated, replicated use-cases involving fail-over are relatively complex and a 4 point explanation of what's happening isn't much to go on. If you had a test-case that reproduced the behavior that you're seeing that I could run easily that would help your cause.
And if this is to be a bug, Is trying with 10.0.0 the only path forward or would a bug patch to 8.2.1 be a possibility?
HornetQ is no longer under active development so there wouldn't be any kind of patch release for it. Also, I don't think Wildfly does patch releases either. Community projects are more like the bleeding edge of development - you really need to stay on the current release to have all the latest fixes. If you want long-term stability then I recommend not just using EAP but getting support subscription from Red Hat so that you can actually get patches for bugs. Of course, if something is fixed upstream that you want in a previous release you can always back-port it and recompile it yourself. This is open-source after all.
-
4. Re: Co-located Failover/Failback Issue Wildfly 8.2.1
mnovak Apr 20, 2016 6:09 AM (in response to jbertram)Could you share your configuration with us?
Thanks,
Mirek