[opencms-dev] Antwort: Re: server is not reacting after a time of inactivity

[Roman Uhlig Maxity.de]

Hi Frank,

if you have no activity on the weekends, this approach will cause the
connection to fail on monday again. ;)
IMO it's a better and more solid solution to use the pooling ping from
the OpenCms connection pooling. This way, the pooling frequently pings
the connection (e.g. once a hour) and keeps it alive no matter how long
there is no activity. I think it's quite self-explaining, just have a
look at these pooling options:
 
db.pool.default.testWhileIdle=true
db.pool.default.timeBetweenEvictionRuns=3600000
db.pool.default.numTestsPerEvictionRun=3
db.pool.default.minEvictableIdleTime=1800000
db.pool.default.testQuery=SELECT 1 

Since OpenCms is using Apache DBCP (afaik), you may look up the exact
meanings of the parameters here:

http://commons.apache.org/dbcp/configuration.html

Roman

________________________________

Von: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Frank Pertack
Gesendet: Dienstag, 27. April 2010 09:47
An: The OpenCms mailing list
Betreff: [opencms-dev] Antwort: Re: server is not reacting after a time
of inactivity



Hello Brett,

yes I think that helped.
Yesterday I implemented those two lines into the my.ini and today
morning it started right away.
I hope that stays that way.

Thank you very much for your advise.

Best regards

Frank


Inactive hide details for Brett Sheeran ---26.04.2010 12:28:26---Frank
Pertack wrote: > After a certain time of inactivity the Brett Sheeran
---26.04.2010 12:28:26---Frank Pertack wrote: > After a certain time of
inactivity the server does not respond:



Von:	 
Brett Sheeran <brett.sheeran at gmail.com>	

An:	 
opencms-dev at opencms.org	

Datum:	 
26.04.2010 12:28	

Betreff:	 
Re: [opencms-dev] server is not reacting after a time of inactivity	

Gesendet von:	 
opencms-dev-bounces at opencms.org	
________________________________




Frank Pertack wrote:
> After a certain time of inactivity the server does not respond:
> Server Error 500
> After a Browser-Refresh (F5) the page appears normally.
> I don't understand this opencms-error, what causes this error?
> Did anybody else experience this behaviour of OpenCms, what can I do
to

Hi Frank,

I suggest editing your MySQL config file to increase the following two
values from their defaults (of 8 hours) to 24 hours (as shown below):
wait_timeout=86400
interactive_timeout=86400

As I understand it, the default value for wait_timeout is 28800
(seconds) or 8 hours. After 8 hours of inactivity, MySQL closes the
connection. The next time OpenCMS calls that connection, you get an
error.

I have had similar problem on systems that did not receive page
requests outside working hours. The first request of the day would
generate an error, but things would be fine after that. Since
increasing those wait_timeout and interactive_timeout values, I have
had no further problems.

HTH.

Regards

Brett

_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please
visit
http://lists.opencms.org/mailman/listinfo/opencms-dev