Hi, Emmanuel Cecchet wrote: > Hi Ingo, >> i'm currently testing the 3.0 beta2 release and have some maybe issues >> found. >> >> my controller config: >> <SEQUOIA-CONTROLLER> >> <Controller name="node00304884C6C0" jdbcIpAddress="node00304884C6C0" >> jdbcPort="25322"> >> <JmxSettings jmxIpAddress="10.10.10.2" jmxPort="21090"/> >> <Report/> >> </Controller> >> </SEQUOIA-CONTROLLER> >> >> The param jmxIpAddress="10.10.10.2" does not cause the correct bound. >> The JMX >> port is always bound to all interfaces what is a problem for me due to >> security >> reasons. >> > What JRE are you using? > In fact JMX with 1.4 relies on mx4j and in 1.5 we use the one of the > JDK. So the code path to investigate is different for each case.
it's the same environment I mentioned in other postings: Environment: debian etch, java 1.5, 1 backend postgresql 8.1.4, EmbeddedRecoveryLog, sequoia 3.0 beta02, appia 3.2.4, hedera 1.5.6-cvs03.01.2007 BTW: I discovered an issue with using hostnames instead of IPs. So everbody should use IPs. If you use transfer dump (and maybe comparable commands like restore log ...) with hostnames as target the command fails with <ip> controller not in group exception because the controller list contain members with the value of jdbcIpAddress. If this is the hostname the comparison to its ip fails. The mapping between hostnames and ip's and the checks if these names of the same thing (the interface) could be improved in later versions. Greetings, )ngo _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
