Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 41538] Unable to run Tomcat as a Windows service
 under JDK 1.6
In-Reply-To: <bug-41538-78@https.issues.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Message-Id: <20080711132942.3F438234C168@brutus.apache.org>
Date: Fri, 11 Jul 2008 06:29:42 -0700 (PDT)

https://issues.apache.org/bugzilla/show_bug.cgi?id=41538


Dan Armbrust <daniel.armbrust.list@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |


--- Comment #30 from Dan Armbrust <daniel.armbrust.list@gmail.com>  2008-07-11 06:29:40 PST ---
(In reply to comment #29)
> As Mark points out, this is a JAVA bug.  It's contingent on the Sun Java
> installer
> to provide msvcr71.

Will, 

You are missing the important detail that sun DOES provide msvcr71.  So, in
their mind, they have done nothing wrong.

Tomcat is the provider of tomcat.exe - so Tomcat is the app provider which has
not provided the msvcr71 according to Sun's flawed logic. 

Now, tomcat shouldn't have to provide this library, because (if I understand
the issue correctly) if Sun hadn't messed up, then the jvm.dll would be able to
find the msvcr71 which sun provides.  But, Sun messed up.  So jvm.dll can't
find the msvcr71 which sun provides when you call the jvm.dll from a different
folder - the folder where tomcat.exe is located in this case.

> Please, don't waste your time and ours by reopening.

And that comment sounds an awful lot like Sun's response.  More buck passing. 
Seems pretty clear to me that if tomcat won't start as a service, and tomcat is
providing the service code, then we have a bug in tomcat.  It doesn't matter to
me as a user of tomcat where the source of the problem is - this bug should
still be open for tracking until the source of the problem is fixed, or a
workaround is put into the tomcat installer - either via the installer, or by
using a new version of commons-daemon which has a workaround.  

With the bug open, maybe then this bug would attract a developer who knows c
well enough to implement a workaround in commons-daemon to actually fix this
problem.  Unfortunately, I'm pretty sure I know even less c than Mark, so that
developer won't be me.


I have opened a bug in commons-daemon:
https://issues.apache.org/jira/browse/DAEMON-110

And, I'll risk wasting your time by reopening this bug - because I strongly
feel that this bug shouldn't be closed until the DAEMON bug is resolved, if
that is the path that is taken.  At worst, maybe the churn of reopening and
closing this bug will attract another developer who has the skills necessary to
actually fix this issue for the rest of the tomcat users.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

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