In regards to my original problem sent a few hours ago, if someone could
test the following, it would be greatly appreciated...
1. If you have a version of Tomcat 5.0.28 running on ports 8080 and 8443
using a valid (signed) certificate and NOT running as root.
2. Make sure that the above both res
eously.
Thanks,
Jeach!
On 6/6/06, Grant Johnson <[EMAIL PROTECTED]> wrote:
I am not an expert but
Both tomcat's look like they are trying to "do stuff" on ports 8005,
and connector ports 8080 and 8443.
What if you stopped both tomcat's and started one. Does t
8080
change port 8443 to 18443
Regards
Andrew
On 06/06/2006, at 4:39 PM, Christian Jean wrote:
> Here is the result for 'jakarta-tomcat-5.0.28/conf/server.xml':
>
>
>
> Here is the result for 'apache-tomcat-5.5.17/conf/server.xml':
>
>
Here is the result for 'jakarta-tomcat-5.0.28/conf/server.xml':
wrote:
In both tomcat/conf directories do a
grep 'port=' server.xml
Regards
Andrew
On 06/06/2006, at 4:25 PM, Christian Jean wrote:
> JDK 1.5 (AMD 64-bit) had been installed for severa
JDK 1.5 (AMD 64-bit) had been installed for several months already with
JAVA_HOME configured correctly.
Jeach!
On 6/6/06, Bob Hall <[EMAIL PROTECTED]> wrote:
--- Christian Jean <[EMAIL PROTECTED]> wrote:
> I've been successfully using various version of
> Tomcat for se
Please help, my production server is down because of this mess
I've been successfully using various version of Tomcat for serveral years
with the same certificate... all worked well.
The last server I was using was 5.0.28... which kept crashing every day!
Looking at the log files did not giv