The Tomcat is currently up and running - all I've done is just set the Xms256m. I already sent all the log information I was able to collect on the debug level, see my first post. Unfortunately, the JVM is an old one - JRE 1.4.2 (with all the extensions needed to run Tomcat 5.5.17). It works just fine, I tested it.
@Andre: Yes, you are correct (and it's not nitpicking). Plus the Windows service calls the Tomcat executable which invokes the JVM via JNI (if I'm not mistaken). It may be the case you are describing, but shouldn't it tell something like: "Not enough memory" or "Cannot allocate Java Heapspace" or something like that? Jiri On Fri, Jul 24, 2009 at 2:31 PM, André Warnier <a...@ice-sa.com> wrote: > Goddard Jiri wrote: > >> Here you are: >> http://dredwerkz.ic.cz/tomcat_init_vm.png >> >> I set -Xms256m -Xmx1024m. It should be more than enough for that app. The >> tomcat didn't want to start without the Xms (or Xms0m). >> >> Not to nitpick, but just to be precise : > the Xms and Xmx parameters are parameters for the JVM, not for Tomcat. > It is the JVM that does not want to start, not Tomcat. > When the error occurs, the JVM probably has not even started to load the > Tomcat code. > As far as I know, these JVM parameters are never required. But if you do > not specify Xms, Java tries to start with a /default/ starting heap size. > This default heap size (of which I don't know where it is set), may be set > too large for the type of machine architecture you have, which is why > omitting the Xms parameter will not allow the JVM to start. > > There was just another thread on this list giving information on this > topic. You may want to check it, it contains some technically precise > information on the subject. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- web: http://dredwerkz.ic.cz group: http://groups.google.com/group/dr3dwerkz icq: 218 659 431
