Hi Eric
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.
Cool, this is certainly valid and good approach..
Just another question: If not using script mediator, is it save to use Java 6 with Synapse?
Yes, I believe so.. however, I guess all developers are currently on JDK
1.5.x by default, and we do not load test etc with JDK 1.6 yet
Does someone already use this combination in production? Do all other
Unit-Tests pass?
Not to my knowledge, as we recommended JDK 1.5 for the last release..
But we will certainly look to support both 1.5 and 1.6 for the next
release of Synapse 1.3
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
