Re: Jahia & SSL

Hi jesse,

could you also mention the version of jahia you are running ? And can you
trace what the errors are ? Have you got some exception in the tomcat
console ?

Michel

Hi
all,

I’m having serious trouble getting Jahia to work under SSL
correctly. I am running on a Win 2K3 machine with SUN JDK 1.4.2_04
and have used all of the following configurations in various
combinations:

Tomcat 4.1.18 (as bundled with Jahia)

Tomcat 4.1.30

Tomcat 5.0.16

Tomcat 5.0.24

Apache 2.0.24 (with JK and JK2)

IIS (with JK)

The system works fine under these configurations for the most part, but
when I run a load test (using JMeter, though I have also written a custom
client in both Java and C# to rule out JMeter problems) after a while I
get connection refused exceptions in the client. Sometimes there
are errors in the jk log files, but not always. I increased the
maxConnections for the AJP connector in tomcat to well above the number
of client’s I am running, with no effect. The error rate runs at
anywhere between 0.01% and 2%, but the load on the server is not too
sever. The average response time for requests are well below 200
milliseconds, so I don’t think that the server is just running out of
steam.

All of the requests are coming out of the front cache since I spider the
website before running the load test to warm up the cache, so I don’t
think it is anything to do with the size of the DB connection pool
(though I wouldn’t expect that to cause the observed behaviour
anyway)

I’ve played with maxKeepAlive, minConnections, maxConnections,
acceptCount. I’ve used both the CoyoteConnector and the deprecated
AJP13Connector.

I’m kind of stuck now and would appreciate any suggestions might you
have.

Jesse

----------

--- Disclaimer ---

Unless otherwise agreed expressly in writing by a Director of Edina
Software, this communication is to be treated as confidential and the
information in it may not be used or disclosed except for the purpose for
which it has been sent. If you have reason to believe that you are not
the intended recipient of this communication, please contact the sender
immediately.