Log in

No account? Create an account

Previous Entry | Next Entry

Stupid Configuration Documentation

I'm trying to find out how to get iPlanet to use a JVM that's not the default JVM because I'd like to see what happens on a test port to our app if I upgrade from 1.3 to 1.4 before I actually make a system-wide change. I was hoping that there would be a simple place to specify the path to the JVM, but if there is such a simple place, I haven't seen it yet. So, off to the web I go looking for documentation. I found the iPlanet Web Server, Enterprise Edition Programmer's Guide to Servlets: Appendix C JVM Configuration, which hasn't solved my problem, but did offer the following information about setting additional JVM settings:
However, if you need to specify settings for the JVM, such as additional classpath information, you can configure the JVM properties for iPlanet Web Server via the Administrator interface. You can add as many other properties as you want to (up to 64).
So, which is it -- can I add as many other properties as I want to, or am I limited to 64? They could have completely left out that part about "as many other properties as you want."

I am amused.


Aug. 26th, 2004 01:59 pm (UTC)
Yeah, there's a new process for each instance. You can modify the JVM parameters on a per-instance basis, e.g. But the JAVA_HOME for all instances is set on a global level. Why? Because iPlanet is poo.

To their credit, in newer versions of iPlanet, you can do what I wanted to do. But when we upgrade our app server, it'll be to Apache/Tomcat, not to a newer version of iPlanet.
Aug. 26th, 2004 02:22 pm (UTC)
Have you ever taken a look at Resin from Caucho? Free to try and develop on, $500 to deploy with it commercially, source code is available, support licence is $2K. If you are just doing Servlets/JSP, it's great. Or it was, 2 1/2 years ago, when I used it.

Latest Month

June 2013

Page Summary

Powered by LiveJournal.com
Designed by Tiffany Chow