Marc Herbert wrote: > Ingo Kampe <[EMAIL PROTECTED]> writes: > >> Due to the HA setup I need to manage a virtual IP controller by heartbeat >> which >> jumps between HA members. The problem now is that sequoia/appia/hedera takes >> this virtual IP as member name and not the primary first IP of the network >> interface. This works without problems in the setup moment but the whole >> thing >> is running completly mad if this virtual ip switch over to the other machine. >> >> So I would suggest to improve the IP detection and that you try to always use >> the IP configured in appia config. >> > > This seems related to <https://forge.continuent.org/jira/browse/SEQUOIA-366>
I'd like to vote for this BUG to be fixed soon and maybe in 2.10.5!? This is the last blocker for us to go live with a sequoia enabled release. I read that this issues improved in java 1.6. The whole network interface access stuff. But this isn't an option yet. So in my opinion the static usage of configured IPs (from appia.xml) would fit best. Thank you, )ngo
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
