Hey Sebastian, Testing the different JVM's out there sure sounds like good fun to me. I had tried testing the difference of the jdk1.2.2 and the jdk1.3.1 by running a thread dump on each VM. Some interesting stuff I saw was that the 1.2 dumps to the err log while the 1.3 dumps to the out log. There is definitely a lot of VM-dependent behavior out there.
Going back to the question, yes it is sufficient to simply change the path to the Java Executable via the JMC. What will happen here is the change will be reflected in the relevant server's local.properties file. You could also change this value directly through the local.properties file by editing this property: java.exe=C:\\j2dk1.4.0\\bin\\javaw.exe Another option would be to edit this value in the global.properties. What will happen here is all of your JRun servers (i.e.- Admin and Default) will use the JVM that you define. Regards, Alex -----Original Message----- From: Sebastian Millies [mailto:[EMAIL PROTECTED]] Sent: Monday, March 18, 2002 4:14 PM To: JRun-Talk Subject: Switching between JRE's Hello, I'd like to do a few experiments to see how JRun3.1 behaves using either Sun's jre1.3.1_02 or IBM's JRE1.3 on my Red Hat box. Is it sufficient to change the path to the Java Executable for the relevant server using the JMC, or are there any more things to watch out for? Best, Sebastian -------------------------------------------------------------------------- Sebastian Millies, IDS Scheer AG Postfach 10 15 34, 66015 Saarbr�cken Zimmer 2.34, email: [EMAIL PROTECTED] fon +49-681-210-3221, fax +49-681-210-1311 ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
