Hi Pierre,
I entered this config line into the following files:
/opt/apacheds-1.5.2/conf/apacheds.conf
/var/lib/apacheds/default/conf/apacheds.conf
I tried just the one in /var/lib/apacheds/default/conf/ first, then
the one in /opt/apacheds-1.5.2/conf, then both. I still get the same
result. It takes 37 seconds from the time I enter /etc/init.d/apacheds
start default to when the wrapper stops. That's with both of the
config files altered. Without the timeout line you recommended, it
took 40 seconds.
Is there anything else I can try? Any other info I can provide?
Thank You,
Troy
On Jul 17, 2008, at 9:17 AM, Pierre-Arnaud Marcelot wrote:
Hi Troy,
I think this issue is related to the Tanuki wrapper we're using.
You may have a "slow" machine and with the ping timeout of the
wrapper set by default to 30 seconds, it may not be enough time for
the server to start up.
Try to increase this timeout time with the following line in you
server instance configuration:
wrapper.ping.timeout=180 (3 minutes)
See this page (http://wrapper.tanukisoftware.org/doc/english/prop-ping-timeout.html
) for more information.
Hope this helps,
Pierre-Arnaud
On Thu, Jul 17, 2008 at 5:33 AM, Troy Davis <[EMAIL PROTECTED]> wrote:
> which JVM are you using ?
Of course, sorry to have neglected this:
jre1.6.0_06 from Sun's installer jre-6u6-linux-i586-rpm.bin
Thank You,
Troy
