Olivier Fambon wrote: > Ingo Kampe wrote [01/17/2007 02:26 PM]: >> 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. >> > > You can workaround this issue and go live by forcing the ip addresses > (or host-names) in the controller.xml config file: > > config/controller/controller.xml: > > <Controller jdbcIpAddress="node50" jdbcPort="25322"> > <JmxSettings jmxIpAddress="node50"/> > ... This just works in 3.0 beta02. We like to use not a beta version and tested 2.10.4. Nevertheless I already posted problems with java 1.5 and the above setting in 3.0 too. The JMX process not binds exclusive to the given port and if you use hostnames instead of IP transfer dump commands not match the controller in group and does not work.
So again voting for the BUGFIX ;-) Regards, )ngo
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
