Re: JMX remote and JDK 1.5
Remy Maucherat wrote: Hi, It looks like the new JDK has an easy way to add a connector (and even SNMP) to a VM, without the need for explicit support in the application, using system properties (on the command line) like: - com.sun.management.config.file - com.sun.management.snmp.port - com.sun.management.jmxremote.port I expect other vendors will provide a similar feature :) As a result, there's no need to reinvent the wheel inside Tomcat, and I'm shelving my plans to add a listener to instantiate JMX remote (no need to add complexity), and will unbundle JMX remote (only the JMX RI core will be bundled); instead, I'll add a little chapter about JMX in the docs :) What does it mean ? I saw the 1.5 jmx stuff, but as usual this only works with 1.5 while most people will keep using 1.3 or 1.4 for few years. I hope we're not falling into the forced upgrade trap :-) I agree that tomcat should't reinvent the wheel - but provide some mechanism for 1.4, maybe similar ( or identical ) with what 1.5 provides. This would also allow people with 1.3 or 1.4 to enjoy JMX now. Costin With this JDK, JMX remote powered clients are going to become a standard almost instantly, since the only requirement is that the server is instrumented though JMX. So good job to the J2SE team, this doesn't seem beta (although they didn't test JBoss, it doesn't work right now, as a side effect of bundling JMX :-( ). On the performance side, my (client) VM seems as fast as JDK 1.4.2, but does seem to use a little bit less memory. So unless it turns out to be really unstable (it does seem better than almost all the other Sun JDKs I've tried, so far), final 1.5.0 should be really successful when it's released. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JMX remote and JDK 1.5
[EMAIL PROTECTED] wrote: Remy Maucherat wrote: What does it mean ? I saw the 1.5 jmx stuff, but as usual this only works with 1.5 while most people will keep using 1.3 or 1.4 for few years. I hope we're not falling into the forced upgrade trap :-) I agree in general. However, I've played with the beta, and it basically feels like 1.4.3, with the added language features. I didn't test the stability in production, of course, but it looks good so far. I do not think we'll end up in a situation like with Java 1.4 when: - coders didn't want to use the new APIs since they weren't stable and tested (NIO) - people didn't want to upgrade as the JVM itself wasn't stable I agree that tomcat should't reinvent the wheel - but provide some mechanism for 1.4, maybe similar ( or identical ) with what 1.5 provides. This would also allow people with 1.3 or 1.4 to enjoy JMX now. I'm talking about JMX remote here. AFAIK, no clients support it right now. JDK 1.5 will make it a standard in a hurry, given that you don't have to configure or add anything in the application itself. Given that there's already support for the other JMX remoting connectors in Tomcat, I don't see the need to add something which will only become used once JDK 1.5 is out. Now, if someone feels like adding it, I won't complain, but I won't do it myself ;) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JMX remote and JDK 1.5
Hi, It looks like the new JDK has an easy way to add a connector (and even SNMP) to a VM, without the need for explicit support in the application, using system properties (on the command line) like: - com.sun.management.config.file - com.sun.management.snmp.port - com.sun.management.jmxremote.port I expect other vendors will provide a similar feature :) As a result, there's no need to reinvent the wheel inside Tomcat, and I'm shelving my plans to add a listener to instantiate JMX remote (no need to add complexity), and will unbundle JMX remote (only the JMX RI core will be bundled); instead, I'll add a little chapter about JMX in the docs :) With this JDK, JMX remote powered clients are going to become a standard almost instantly, since the only requirement is that the server is instrumented though JMX. So good job to the J2SE team, this doesn't seem beta (although they didn't test JBoss, it doesn't work right now, as a side effect of bundling JMX :-( ). On the performance side, my (client) VM seems as fast as JDK 1.4.2, but does seem to use a little bit less memory. So unless it turns out to be really unstable (it does seem better than almost all the other Sun JDKs I've tried, so far), final 1.5.0 should be really successful when it's released. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
