Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
From: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>
To: Tomcat Users List <users@tomcat.apache.org>
Date: Fri, 24 Jul 2009 08:37:47 -0500
Subject: RE: Error during initialization of VM
Thread-Topic: Error during initialization of VM
Thread-Index: AcoMXb9+jXgXE+ZzS66dyW6Dl6RW2QAA0/jg
Message-ID: 
 <0AAE5AB84B013E45A7B61CB66943C17229B028DCCD@USEA-EXCH7.na.uis.unisys.com>
References: <d1c1e2c60907240458r1379cadctc4f1ca1a62559da2@mail.gmail.com>
	 <20090724120602.07E3040387@relay8.relay.dfw.mlsrvr.com>
	 <d1c1e2c60907240513y177b65a6w63f37137f690f96a@mail.gmail.com>
	 <4A69A998.2090203@ice-sa.com>
 <d1c1e2c60907240552g3100ba23qa960206df6ef7c9f@mail.gmail.com>
In-Reply-To: <d1c1e2c60907240552g3100ba23qa960206df6ef7c9f@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> From: Goddard Jiri [mailto:g0dd4rd@googlemail.com]
> Subject: Re: Error during initialization of VM
>=20
> The Tomcat is currently up and running - all I've done is=20
> just set the Xms256m.

If the value was zero in the Tomcat registry settings, that will cause the =
error you observed.  The Tomcat service wrapper always specifies minimum an=
d maximum heap sizes when starting the JVM, so if either registry entry was=
 missing or corrupted, it likely used a value of zero.  Note that these are=
 *not* the default=20
heap size limits, which are plenty to allow the JVM to initialize, although=
 it may not be able to load much in the way of user classes.

(The request to show CATALINA_OPTS is irrelevant, since you're running this=
 as a Windows service, and environment variables aren't used.  Also, the am=
ount of RAM on the system doesn't matter, since we're talking about virtual=
, not real, space here.)

> 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

It may work fine, but you'll get much, much better performance with a newer=
 JVM.  I'd strongly recommend upgrading.

> It may be the case you are describing, but shouldn't it tell=20
> something like: "Not enough memory" or "Cannot allocate Java
> Heapspace" or something like that?

The message you're getting is produced by the JVM only when initialization =
fails so early that none of the internal error mechanisms are available.  N=
ewer JVMs do produce more descriptive messages - another reason to upgrade.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MA=
TERIAL and is thus for use only by the intended recipient. If you received =
this in error, please contact the sender and delete the e-mail and its atta=
chments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org