RE: Jahia & SSL

Hi Michel,

 

I'm running Jahia 4.0.3 and I don't get any errors in the tomcat console
or any of the log files for tomcat.  I get the following error in the
isapi.log (the JK connector log)

 

[Tue Jun 08 07:44:22 2004]  [jk_ajp_common.c (1318)]: Error connecting
to tomcat. Tomcat is probably not started or is listening on the wrong
port. Failed errno = 61

[Tue Jun 08 07:44:22 2004]  [jk_isapi_plugin.c (928)]: HttpExtensionProc
error, service() failed

 

I'm guessing this has to do with the number of worker threads available
in Tomcat for handling AJP13 connections because it is an intermittent
problem which appears only under higher loads, but I have set the number
much higher than the number of clients accessing so I wouldn't expect
these problems.

 

Jesse

 

________________________________

From: Michel Romy [mailto:[email protected]] 
Sent: 07 June 2004 16:51
To: [email protected]
Subject: 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. 



--- 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.