Brian,
Thanks, that worked. The ...pool.logfile... parameter was commented out
(don't know why), but I did not have the second line
(processor.xsp.pool.turbine.logs=database). Everything seems to be working
ok. Do I still need it?
Mark
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Brian P Millett
Sent: Thursday, September 13, 2001 2:37 PM
To: [EMAIL PROTECTED]; Mark Kent
Subject: Re: TurbineResources.properties error msg
Mark S. Kent wrote:
I've turned on esql pooling (which works great), but now the first time I
try to run an esql command in an XML file I get an error message in the
tomcat log file of:
java.lang.Exception: The logfile= property and the turbine.logs= property
in the TurbineResources.properties file are null or could not be found.
At least one of these properties must be defined in the
TurbineResources.properties file.
I then must restart tomcat and httpd to get the website to start
working
again.
Mark, those parameters are defined in the cocoon.properties file:
processor.xsp.pool.logfile=/opt/apache/jserv/logs/dbPool.log
processor.xsp.pool.turbine.logs=database
Make sure that they are set and that the cocoon.properties file can be seen
in the WEB-INF
directory.
--
Brian Millett
Enterprise Consulting Group Shifts in paradigms
(314) 205-9030 often cause nose bleeds.
[EMAIL PROTECTED] Greg Glenn
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faqs.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
