Craig R. McClanahan wrote:
Yes, it's disabled by default.On Mon, 30 Dec 2002, Costin Manolache wrote:I agree. Is 'reloadabl' disabled by default ?Yes ... at least in HEAD of 4.1 and 5.0. I'm pretty sure it's always been that way.
BTW, can't Linux 2.5/2.6 handle thousands of threads without any problem ? I remember reading an iterview of Ingo who said JVM performance and thread handling should be way better in 2.6.
The idea is that there's nothing wrong with designing with threads in mind (I think that's good design), but the problem is that it doesn't quite work too well with most current OSes.
I added (theorical) support for MC4J in 5.0 some time ago, BTW. The only problem is that there's a version clash with MX4J (Tomcat has to use an API which changed between MX4J 1.1 and 1.1.1 to start the JRMP connector, and MC4J only works with MX4J 1.1 at the moment).BTW - another way to do reload-on-demand is using JMX ( the html interface provided by either jmx-ri or mx4j - or any other jmx adaptor ). It may be a good idea to make the manager webapp more powerfull - i.e. support generic ( simple ) get/set operations via JMX.I agree. We could pretty easily provide JMX-based operations for everything that manager does (so that they're accessible from a JMX-based client), and have the manager webapp itself just be wrappers around those same MBean operations (for easy integration into non-JMX clients that can perform HTTP requests).
After hacking to get it to work, in order to test the feature, I noticed the start/stop/reload operations weren't declared on the model MBeans.
Remy
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
