>> Security.setProperty("networkaddress.cache.ttl", myValue1);
>> Security.setProperty("networkaddress.cache.negative.ttl", myValue2);
> So I believe you do not want to set this to a specific hard coded value in >
> the startup scripts?
Yes Asankha, you are right with your assumption. :-) Setting the corresponding
Java System properties at startup works, but there is no optimal value for all
situations. The default of caching forever is generally a good thing. Only in
certain situations I want to be able to *temporally* change those values
without having to restart the JVM.
Currently the workaround I see (if having a loadbalanced cluster in place) per
node before and after any IP change:
- switch to maintenance
- do JVM-restart with changed values (incorporated into startup scripts)
With Java 6 I can have a small management console, iterate over all nodes and
call a simple MBean method in one single step without introducing much overhead
- seems to work pretty well.
Just another question: If not using script mediator, is it save to use Java 6
with Synapse? Does someone already use this combination in production? Do all
other Unit-Tests pass?
Regards,
Eric
