Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 81320 invoked from network); 8 Aug 2004 06:44:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 8 Aug 2004 06:44:36 -0000 Received: (qmail 79989 invoked by uid 500); 8 Aug 2004 06:44:10 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 79961 invoked by uid 500); 8 Aug 2004 06:44:09 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 79948 invoked by uid 99); 8 Aug 2004 06:44:09 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received: from [66.111.4.26] (HELO out2.smtp.messagingengine.com) (66.111.4.26) by apache.org (qpsmtpd/0.27.1) with ESMTP; Sat, 07 Aug 2004 23:44:06 -0700 Received: from server2.messagingengine.com (server2.internal [10.202.2.133]) by mail.messagingengine.com (Postfix) with ESMTP id 5CCADC141B7 for ; Sun, 8 Aug 2004 02:44:04 -0400 (EDT) Received: by server2.messagingengine.com (Postfix, from userid 99) id 692D586643; Sun, 8 Aug 2004 02:44:04 -0400 (EDT) Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.4 (F2.72; T1.001; A1.62; B3.01; Q3.01) References: <452548B29F0CCE48B8ABB094307EBA1C068CD410@USRV-EXCH2.na.uis.unisys.com> Subject: RE: 1067 error when starting service after allocating more memory to JVM In-Reply-To: <452548B29F0CCE48B8ABB094307EBA1C068CD410@USRV-EXCH2.na.uis.unisys.com> To: "Tomcat Users List" Date: Sun, 08 Aug 2004 01:44:04 -0500 From: "Stephen Charles Huey" X-Sasl-Enc: 0REYqr+xVErqLQl4FnapTA 1091947444 Message-Id: <1091947444.12637.201910292@webmail.messagingengine.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Sorry to be a pain, but I'm not exactly sure I understood what I was supposed to do from your fourth paragraph? Could you possibly give me an example of how to find that out? Aren't the parameters -Xmx and -Xms specific to tomcat.exe and not to Windows? I'm also not sure if you meant that I should put -version on the end of my command line string that I mentioned in the first post, or if I should do it just with the memory flags, or what... I'm just saying that I don't know how to find out what my environment can handle! Thanks for the help, Stephen ----- Original message ----- From: "Caldarale, Charles R" To: "Tomcat Users List" Date: Sat, 7 Aug 2004 13:31:29 -0500 Subject: RE: 1067 error when starting service after allocating more memory to JVM > From: Stephen Charles Huey [mailto:stephenhuey@fastmail.fm] > Subject: 1067 error when starting service after allocating more memory to JVM > > Hey, we've been running Tomcat 4.1.27 for a couple of years on our > webserver, and we just upgraded the server from 2GB of memory to 3GB. > We've been allocating 1GB to the JVM when installing Tomcat as a > service, but now we'd like to do 2GB, so I just changed the two > instances of 1024 to 2048 in this: The short answer is you can't do that. The long answer is, as usual, a bit more complicated. First, Windows normally splits the 4GB virtual space into 2GB for each user process, and 2GB for the operating system, shared across all processes. There is an option for Windows Server bootstrap to change this boundary to 3GB for user processes and 1GB for the OS (sorry, I don't remember the tag). Second, the virtual space that Windows gives each user process is fragmented by DLLs scattered around in it, and the Sun JVM insists on having one contiguous area for its heap (at least it did in 1.4.1; have not verified this in 1.4.2). This makes it difficult to get a whole lot more than 1GB for the heap. Third, there is (or possibly was) a bug in the JVM heap initialization that failed to treat the specified sizes as unsigned, so 2GB and above was treated as negative. Lots of weird results from that. Again, I haven't looked in the 1.4.2 code, so this may have been fixed by now. Your best bet is to do a binary search with -Xms/-Xmx and see what your environment will handle. You don't need to do this with Tomcat - just specifying -version will suffice. (Just make sure you put the heap settings before -version, because anything on the command line after -version is ignored.) - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL 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 attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org