What I think you need to consider is the risk of running TC in this manner
dependant on where and what the TC instance is being deployed for.
The risk MAY be acceptable if you are intending on running a TC instance
internally on an intranet or something similar, as then you only have to
worry
I am intending to run in a fully internet exposed
environment and I only have ONE physical machine to
use for deployment. It will be directly connected to
the internet at co-location service provider. So ...
In a conversation from yesterday, it appears another
user had a similar question. How
- Original Message -
From: Justin Jaynes [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Thursday, May 27, 2004 3:19 AM
Subject: RE: standalone production?
I am intending to run in a fully internet exposed
environment and I only have ONE physical machine to
use for deployment
The http://jakarta.apache.org/tomcat/tomcat-5.0-doc/setup.html
isn't the way for doing jsvc that I used (it didn't work
right).
You should already have jsvc.tar.gz in the bin dir
for tomcat; unpack it, and follow the instructions
in INSTALL.txt for building jsvc. There's a page for
it at
: standalone production?
The http://jakarta.apache.org/tomcat/tomcat-5.0-doc/setup.html
isn't the way for doing jsvc that I used (it didn't work
right).
You should already have jsvc.tar.gz in the bin dir
for tomcat; unpack it, and follow the instructions
in INSTALL.txt for building jsvc. There's a page
AM
Subject: RE: standalone production?
Hi,
Good post. I've added it to the FAQ:
http://jakarta.apache.org/tomcat/faq/security.html#jsvcExample.
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: RJ [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 27, 2004 8:17 AM
:00 AM
To: Tomcat Users List
Subject: Re: standalone production?
If this is the case, then why not fix the
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/setup.html
page to show the correct(updated) information?
Doug
- Original Message -
From: Shapira, Yoav [EMAIL PROTECTED]
To: Tomcat
