Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 24086 invoked from network); 10 Dec 2008 17:26:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Dec 2008 17:26:35 -0000 Received: (qmail 88073 invoked by uid 500); 10 Dec 2008 17:26:35 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 88025 invoked by uid 500); 10 Dec 2008 17:26:35 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 87997 invoked by uid 99); 10 Dec 2008 17:26:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2008 09:26:34 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gsexton@mhsoftware.com designates 216.17.130.186 as permitted sender) Received: from [216.17.130.186] (HELO mail.mhsoftware.com) (216.17.130.186) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Dec 2008 17:26:19 +0000 Received: from [192.168.0.254] (c-24-8-34-101.hsd1.co.comcast.net [24.8.34.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.mhsoftware.com (Postfix) with ESMTPSA id 296892544E for ; Wed, 10 Dec 2008 10:25:58 -0700 (MST) Message-ID: <493FFBA5.5060207@mhsoftware.com> Date: Wed, 10 Dec 2008 10:25:57 -0700 From: George Sexton User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Tomcat Developers List Subject: tomcat5.exe on Windows x64 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Before I get flamed, I looked at a way to report this bug through bugzilla/jira and couldn't seem to find the right project... I just went through a troubleshooting session getting tomcat5.exe to work on Windows 2008 x64 with x64 jre 1.6.0 Update 11. I was using the tomcat5.exe x64 binaries that I downloaded from svn. The JVM the service was created with was "auto". Attempts to start the service wrote: [2008-12-10 10:04:24] [174 javajni.c] [error] The specified module could not be found. [2008-12-10 10:04:24] [994 prunsrv.c] [error] Failed creating java [2008-12-10 10:04:24] [1269 prunsrv.c] [error] ServiceStart returned 1 in the jakarta_server_xxxxx.log file. After fooling around with it, I noticed that the jre installer created bad registry entries for HKLM\Software\JavaSoft\Java Runtime Engine\1.6\RuntimeLib the value was: C:\Program Files\Java\jre6\bin\client\jvm.dll The issue is that this file does not exist. Evidently, the Windows x64 JRE does not include the client JVM, only the server jvm. The file: C:\Program Files\Java\jre6\bin\server\jvm.dll does exist. If I manually edit the registry entry, the service starts as expected. I've submitted this as an installer bug to Sun. It might be helpful if the code in tomcat5.exe actually checked for the existence of the jvm. It would have saved a lot of trouble if the log entry had actually said something like: "Configured JVM: C:\Program Files\Java\jre6\bin\client\jvm.dll does not exist. Check the configured value for the JVM." even: "The specified module (C:\Program Files\Java\jre6\bin\client\jvm.dll) could not be found." would be an improvement. -- George Sexton MH Software, Inc. Voice: +1 303 438 9585 URL: http://www.mhsoftware.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org