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 the running
Tomcat work?
Christian Jean wrote:
Here is the result for 'jakarta-tomcat-5.0.28/conf/server.xml':
<Server port="8005" shutdown="SHUTDOWN" debug="0">
<Connector port="8080"
<Connector port="8443"
<Connector port="8009"
<Connector port="8082"
Here is the result for 'apache-tomcat-5.5.17/conf/server.xml':
<Server port="8005" shutdown="SHUTDOWN">
<Connector port="8080" maxHttpHeaderSize="8192"
<Connector port="8443" maxHttpHeaderSize="8192"
Note that I'm using a slightly modified version of
'server-minimal.xml' for
the 5.5, but even using the standard server.xml (with SSL enabled)
gives me
the same results.
Thanks,
Jeach!
On 6/6/06, Andrew Miehs <[EMAIL PROTECTED]> 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 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 serveral years
>> > with the same certificate... all worked well.
>> >
>> > I wanted to test the stability of Tomcat 5.5.17, so
>> > I installed in on the
>> > same server but renamed all the 8XXX ports to 9XXX
>> > so that it could be run
>> > in parallel to the 5.0.28 server. When I started
>> > the 5.5.17 server, I
>> > noticed that I could not get the HTTPS (SSL) pages
>> > working correctly. The
>> > normal HTTP pages were working correctly though.
>> >
>> > Then the real trouble started!! I could not load
>> > any HTTPS pages from any
>> > server thereafter...
>> >
>> > The SSL pages DID work on the 5.0.28 prior to
>> > testing the 5.5.17, but now
>> > HTTPS no longer works at all. When trying to load
>> > the ssl pages from the
>> > browser it says nothing... just a timeout occures.
>> >
>> > The logs don't show a single trace that something (a
>> > page) was not properly
>> > sent.
>> >
>> > Using 'netstat -ln' shows that the ports are
>> > successfully bound.
>> >
>> > The only message I'm capable of getting is with
>> > lynx:
>> >
>> > bash> lynx https://localhost:8443
>> >
>> > Will display the following line:
>> >
>> > SSL error:Can't find common name in
>> > certificate-Continue? (y)
>> >
>> > Appart from installing and running server 5.5.17,
>> > nothing has changed on my
>> > server, so its weird that my production 5.0.28
>> > should stop working because
>> > of this test???
>> >
>>
>> Christian,
>>
>> You mention that no other changes were made on
>> the server, but did you happen to also install
>> jdk/jre 1.5 and/or change JAVA_HOME?
>>
>> -Bob
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam? Yahoo! Mail has the best spam protection around
>> http://mail.yahoo.com
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
F. Grant Johnson
566-0630 / [EMAIL PROTECTED]
Systems/Web Coordinator
RM 285 - Robertson Library
University of Prince Edward Island
***************
Attitude is IT!
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]