Barry, > possibly like I (incorrectly, because he was on UNIX) told a guy the other > day. > > Go to startup.bat, right click and change (under the Memory tab) > properties in the Initial Environment box from Auto to 4096 or higher.
This still isn't going to change anything: Modifying the environment for the startup.bat file doesn't change the memory size for the JVM or the number of threads it is allowed to create. The "initial environment size" in a windows process is the amount of memory (usually specified in kb) allocated for "the environment". That's where DOS stores environment variables like "PATH", "COMSPEC", "PROMPT", etc. You can see what's in the environment by running "cmd" or "command" and typing "set". Increasing the environment size will not change any of the JVM settings, because the JVM runs in a separate process started by the startup.bat file. The only way to modify the JVM settings is to do one of the following: 1. Modify the catalina.bat file and add your options to the JAVA_OPTS environment variable (you may have to add SET JAVA_OPTS=" [insert your java ops here] " to the script). 2. Set the JAVA_OPTS from the command line before launching startup.bat. #2 is nice to use because it's easy to test: open a command window (run "cmd" or "command"), set the JAVA_OPTS and then run startup.bat. If you run tomcat as a service, it doesn't invoke catalina.bat, so you'll have to read this document: http://tomcat.apache.org/tomcat-5.5-doc/windows-service-howto.html And set the JvmOptions command-line parameter. I've never done this myself, so you might need to get help from someone else if you need it. Also, this document is marked as obsolete, so there may be newer or better documentation out there for running tomcat as a windows service. Not sure why you'd want to run an app server on windoze, though ;) -chris
signature.asc
Description: OpenPGP digital signature
