I've never done SSL with Tomcat, but setting up the certificates should be
close to or the same as Apache. In Apache you need the server certificate,
any intermediate certificates, and the private key. The following makes me
uneasy, but if you password protect your key, Apache won't start.
--
OK. You may have reinstalled Java already, but there is another way to do
this.
You can use the 8.3 file name for C:\Program Files. Windows always creates
this for every directory and file that doesn't fall into the pattern. This
works on XP and Server 2003. I assume it will work on any
From: Jonathan Mast
Subject: Problem with Custom Access Log Format
However, I would like to define a custom pattern for logging this
information.
The problem is that I don't see a pattern code that corresponds to the
User-Agent or to the Referrer.
Your reference
Have you tried adding
welcome-file-list
welcome-filemain_page.html/welcome-file
/welcome-file-list
to your application's web.xml file?
-- Bill
-Original Message-
From: jeusdi [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 22, 2008 4:28 AM
To: users@tomcat.apache.org
From: Caldarale, Charles R
Subject: Server.xml Host Configuration
Remove the Context element; it should never be placed in server.xml and
you don't need one.
As an addendum. If you want to remove the Context element but still create
an access log, you can create a context.xml file.
Place
PROTECTED]
Sent: Tuesday, July 22, 2008 8:35 AM
To: Tomcat Users List
Subject: RE: Server.xml Host Configuration
From: Radcliffe, William H. [mailto:[EMAIL PROTECTED]
Subject: RE: Server.xml Host Configuration
As an addendum. If you want to remove the Context element but still
create an access
Joe wrote:
I'm not getting any exceptions on startup, and the exact war file that I'm
pointing is found because it's serving HTML
and even my servlet just fine.
But when I get a ServletContext, it's null. I've got a set of tomcat jars
in the classpath (catalina, annorations-api,
We recently upgraded to Tomcat 6.0.16 and Apache 2.2.8. We started receiving
intermittent exceptions that we hadn't seen under Tomcat 5.0 and Apache 2.0.
They usually occur when we are receiving moderate to heavy traffic, but we
have never seen two thrown the same day closer than 15 minutes apart.
We recently upgraded to Tomcat 6.0.16 and Apache 2.2.8. We started receiving
intermittent exceptions that we hadn't seen under Tomcat 5.0 and Apache 2.0.
They usually occur when we are receiving moderate to heavy traffic, but we
have never seen two thrown the same day closer than 15 minutes apart.
