Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of gsexton@mhsoftware.com
 designates 216.17.130.186 as permitted sender)
Message-ID: <494012E6.6040004@mhsoftware.com>
Date: Wed, 10 Dec 2008 12:05:10 -0700
From: George Sexton <gsexton@mhsoftware.com>
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: tomcat5.exe on Windows x64
References: <493FFBA5.5060207@mhsoftware.com> <4940121C.1040604@apache.org>
In-Reply-To: <4940121C.1040604@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

When I looked at the Commons-Daemon one, all of the entries were 3 or 
more years old, so I didn't think it was in use.

Mark Thomas wrote:
> George Sexton wrote:
>> 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...
> 
> Commons daemon - it is in JIRA although it really is a Sun bug and a
> commons-daemon enhancement request.
> 
> Mark
> 
> 
>> 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.
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
> 

-- 
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