-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michel,
On 2/11/2009 7:35 AM, michel wrote:
> The only other problem I see is that JK has to look at different ports
> before it binds to anything but I assume that it just means it takes a
> bit longer to start but that's all.
No. JK doesn't look at
Users List"
Sent: Tuesday, February 10, 2009 10:18 PM
Subject: Re: Fw: Still trying to get Tomcat 6 to work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michel,
On 2/10/2009 9:30 PM, michel wrote:
I get some messages in the catalina.out log but they don't seem to
indicate any prob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michel,
On 2/10/2009 9:30 PM, michel wrote:
> I get some messages in the catalina.out log but they don't seem to
> indicate any problem. I probably could fine-tune a few things but I am
> just happy to get it working.
>
> Feb 11, 2009 2:19:03 AM
> or
ote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-91.203.57.197-8080
- Original Message -
From: "Christopher Schultz"
To: "Tomcat Users List"
Sent: Tuesday, February 10, 2009 9:08 PM
Subject: Re: Fw: Still trying to get Tomcat 6 to work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michel,
On 2/10/2009 4:53 PM, michel wrote:
> connectionTimeout="2" redirectPort="8443" />
That looks fine to me. Does Tomcat startup cleanly? With an empty log
directory and Tomcat stopped, what is the full contents of catalina.out
after you st
Hi Chris,
connectionTimeout="2" redirectPort="8443" />
- Original Message -
From: "Christopher Schultz"
Sorry, I can't see the original messages (too old so they went out of my
inbox). Can you (re-)post your configurations from server.xml?
- -chris
-BEGIN PGP SIGNATUR
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: Fw: Still trying to get Tomcat 6 to work
>
> Sorry, I can't see the original messages (too old so they
> went out of my inbox). Can you (re-)post your
> configurations from server.xml?
The th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michel,
On 2/10/2009 7:45 AM, michel wrote:
> Much thanks to all and I got it working, but only on port 8090 so the
> URL has to include :8090. I am wondering if there isn't a start-up
> bug, because when I try some commands with all the servers stopp