I just noticed something quite by accident because I accidentally mistyped my TOMCAT_OPTS inside of the tomcat.sh file. (3.2.4, standalone, linux, jdk 1.3).
I don't know if this is "common knowledge" or not, but I thought I would share with the group: the TOMCAT_OPTS affects not only the VM that runs tomcat (i.e., "./tomcat.sh start") but also appears to be read in order to start up the VM that stops tomcat (i.e., "./tomcat.sh stop"). Does this mean we need to be careful as far as allocating memory with -Xms params? I mean, let's say you run a large application and your TOMCAT_OPTS is: -Xms256m -Xmx768m Because I made a typo editing TOMCAT_OPTS, when i went to run "./tomcat.sh stop" it said there was an error in the initialization of the VM because of incompatible heap sizes yadda yadda yadda, and it made me stop and think for a second! I guess this prompts a few questions: 1. Is this effect real? or is it just coincidence? 2. if so, is it intentional? I don't want my "stopper" VM to start at 256m on a machine with 512mb when my running tomcat is taking 384mb as is. Would that cause a bunch of paging, etc. (linux/nt/etc.)? I'm going to probably hack on tomcat.sh a little for my purposes (I don't want this behavior), if anyone else would like my changes you can email me. Or if anyone thinks that there's something I'm being really dumb about, please let me know that too! cheers fillup -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
