Mike,
Basically I've got this directory structure:
/usr/local
|
|- tomcat-servers
| |
| |- server1
| | |
| | |- bin
| | |- conf
| | |- lib
| | |- logs
| | |- src
| |
| |- server2
| | |
| | |- bin
| | |- conf
| | |- lib
| | |- logs
| | |- src
|
|- server1
| |
| |- dir1
| |- index.html
|
|- server2
| |
| |- dir1
| |- index.html
Each server directory under tomcat-servers contains a complete copy of Tomcat at
this point. (If someone can suggest a way to reduce the duplication while still
being able to run multiple instances that are not aware of or affected by each
other I'm open to suggestions.)
Each server has its own server.xml file which is basically the default
server.xml file with these changes:
- ports for HTTP and HTTPS have been changed to 80 and 443 respectively.
- inet values have been added to each HttpConnectionHandler as suggested by
Ritchie Young
- keystore location has been set for HTTPS
- ClientAuth="false" for HTTPS
- the ContextManager has a "home" variable set to
/usr/local/tomcat-servers/server#
- a Context has been created:
<Context path=""
docBase="/usr/local/server#"
crossContext="false"
debug="1"
reloadable="true">
</Context>
In each server's startup.sh the following happens:
- TOMCAT_HOME is set to /usr/local/tomcat-servers/server#
- BASEDIR is set to /usr/local/tomcat-servers/server#
- the -f /path/to/server.xml option is used
So, server1 gets started and the user goes to http://123.456.789.012 and is
presented with a link to dir1. If they click on the link, they are presented
with index.html which displays a "Login" link. The login link points to a JSP
file which does some processing to present the user with an actual Login page.
Everything works just fine.
However, same server, same links, just going to https://123.456.789.012 and
clicking on the link to dir1 fails. The link is relative, so the source code for
the page shows the link as /dir1 and hovering the mouse over the link makes the
status bar shows https://123456789.012/dir1 as the destination. Clicking on the
link makes the status bar show "Connect: Host 123.456.789.012:80 contacted.
Waiting for reply..." and the process stops there. The browser just sits and
waits.
The tomcat.log for that server shows this:
2001-01-11 01:44:27 - ContextManager: ProcessRequest: R( /dir1)
2001-01-11 01:44:27 - ContextManager: Host = 123.456.789.012
2001-01-11 01:44:27 - ContextManager: SM: Prefix match /dir1 -> null null
2001-01-11 01:44:27 - ContextManager: SimpleMapper1: Default map /dir1 null
2001-01-11 01:44:27 - ContextManager: SimpleMapper1: SM: After mapping R( +
/dir1 + null) null
2001-01-11 01:44:27 - Ctx( ): Get real path /dir1 /usr/local/server1/dir1
/usr/local/server1
2001-01-11 01:44:27 - ContextManager: Error mapping the request R( + /dir1 +
null) 302
2001-01-11 01:44:27 - Ctx( ): Handler tomcat.redirectHandler(null/null)
tomcat.redirectHandler
Any ideas?
Dion Vansevenant
Internetwork Administrator
MRO.com
|--------+----------------------->
| | "Mike |
| | Spreitzer" |
| | <mspreitz@us.|
| | ibm.com> |
| | |
| | 2001/01/09 |
| | 13:09 |
| | Please |
| | respond to |
| | tomcat-user |
| | |
|--------+----------------------->
>--------------------------------------------------------|
| |
| To: [EMAIL PROTECTED] |
| cc: (bcc: Dion Vansevenant/PSDI) |
| Subject: Re: Is ANYONE doing this?? TC3.2.1 |
| standalone + SSL + multiple instances on |
| multiple IP's |
>--------------------------------------------------------|
Dion,
I am not doing the full combination you gave, but I *am* succeeding with
my own app + SSL using Tomcat 3.2.1 in standalone mode (your problem #1).
In my case, I am succeeding on AIX 4.3.3 with IBM's JDK 1.3 (and I'm
failing on Linux, but that's another story, elsewhere in this mailing
list). I am not using symlinks, so I can't speak to your exact
circumstances. Have you tried restructuring your directories to be
completely vanilla? A bit more complete details on your server.xml and
directory/link structure would indeed be helpful to anyone trying to
figure this out. I suspect you can expect a redirect anytime you ask for
"foo" and expect to get "foo/index.html".
Good luck,
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
