You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tomcat.apache.org by craig franke <cr...@harlingen.tstc.edu> on 2002/09/19 20:31:28 UTC

Re: Shut down IIS and replace w/standalone Tomcat -- consequences?

You don't have to shut down IIS completely. I have IIS and Apache both running on my W2K domain controller. All I did was go to Internet Services Manager and Stop the Default Website and the Administration Website. Once you do that, port 80 is free and you can run tomcat on that port.

Craig

>>> lists@skubick.com 09/19/02 12:07PM >>>
Is it "OK" to shut down IIS entirely on a computer running Windows 2000
Server and run ONLY Tomcat (bound to port 80) in "standalone" configuration
as a service? The question might seem patently ridiculous to anyone who
runs Unix, but I've gotten the definite impression that there are several
fundamental system services (Active Directory being one of them) that depend
upon having IIS up and running for their own operation.

About a year and a half ago, I experimented with shutting down IIS using the
service control panel. ActiveDirectory failed almost immediately, and
Windows rapidly went into meltdown as service after service failed before
ending on a BSOD. Fortunately, I hadn't changed the IIS startup from
"Automatic" to "Manual", so rebooting put things back to normal.
Nevertheless, it was a sobering experience that's left me quite hesitant to
disable or try to replace IIS with ANYTHING -- especially in a way that's
semi-permanent and would survive a reboot should it kill the OS.

On the other hand, I know that lots of people seem to successfully run
Apache under Windows 2000 Server. My suspicion is that the Windows version
of Apache might actually implement one or more Microsoft-specified class
interfaces and take on additional responsibilities that the Unix version
doesn't -- assuming the role of IIS and delegating requests that go beyond
Apache's own scope to the original IIS .dll libraries. Either that, or
Apache users just don't run ActiveDirectory or any other services that
depend upon IIS to run.

In any case, the impression I've gotten is that trying to disable IIS to
give port 80 to Tomcat 4 is a Bad Idea likely to cause FAR more problems
than it solves. Is that accurate? Or is it possible to shut down IIS
entirely and replace it only with Tomcat 4 without compromising the rest of
the OS?

--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>