You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by Aaron J Angel <th...@aaronjangel.us> on 2010/10/12 19:20:01 UTC
JVM wrapper restarts too soon
When the directory service is busy with large operations, the JVM
wrapper kills the jvm and restarts after several unanswered pings.
Often times, I find that when the wrapper starts, it takes 2 or 3 tries
to get it up and running because it is impatient.
What settings can I tweak to make the wrapper more patient? Large
operations are quite common and I'm okay with the system hanging a bit
while it processes all the data (e.g., batch operations in studio),
because it needs to get done.
Re: JVM wrapper restarts too soon
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Alex,
On 13 oct. 2010, at 12:07, Alex Karasulu wrote:
> On Tue, Oct 12, 2010 at 8:27 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net>wrote:
>
>> Hi Aaron,
>>
>> You might want to have a look at the 'wrapper.ping.timeout' configuration
>> parameter.
>>
>> http://wrapper.tanukisoftware.com/doc/english/prop-ping-timeout.html
>>
>>
> We might want to have a better default setup in our wrapper.conf file for
> this setting based on Aaron's findings. I guess it does not hurt to bump it
> up a bit.
Good idea.
I created a JIRA to keep track of this.
https://issues.apache.org/jira/browse/DIRSERVER-1565
Regards,
Pierre-Arnaud
> Aaron please keep us informed based on your tests.
>
>
>> Hope this helps,
>> Pierre-Arnaud
>>
>> On 12 oct. 2010, at 19:20, Aaron J Angel wrote:
>>
>>> When the directory service is busy with large operations, the JVM
>>> wrapper kills the jvm and restarts after several unanswered pings.
>>> Often times, I find that when the wrapper starts, it takes 2 or 3 tries
>>> to get it up and running because it is impatient.
>>>
>>> What settings can I tweak to make the wrapper more patient? Large
>>> operations are quite common and I'm okay with the system hanging a bit
>>> while it processes all the data (e.g., batch operations in studio),
>>> because it needs to get done.
>>>
>>
>>
>
>
> --
> Alex Karasulu
> My Blog :: http://www.jroller.com/akarasulu/
> Apache Directory Server :: http://directory.apache.org
> Apache MINA :: http://mina.apache.org
> To set up a meeting with me: http://tungle.me/AlexKarasulu
Re: JVM wrapper restarts too soon
Posted by Alex Karasulu <ak...@apache.org>.
On Tue, Oct 12, 2010 at 8:27 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net>wrote:
> Hi Aaron,
>
> You might want to have a look at the 'wrapper.ping.timeout' configuration
> parameter.
>
> http://wrapper.tanukisoftware.com/doc/english/prop-ping-timeout.html
>
>
We might want to have a better default setup in our wrapper.conf file for
this setting based on Aaron's findings. I guess it does not hurt to bump it
up a bit.
Aaron please keep us informed based on your tests.
> Hope this helps,
> Pierre-Arnaud
>
> On 12 oct. 2010, at 19:20, Aaron J Angel wrote:
>
> > When the directory service is busy with large operations, the JVM
> > wrapper kills the jvm and restarts after several unanswered pings.
> > Often times, I find that when the wrapper starts, it takes 2 or 3 tries
> > to get it up and running because it is impatient.
> >
> > What settings can I tweak to make the wrapper more patient? Large
> > operations are quite common and I'm okay with the system hanging a bit
> > while it processes all the data (e.g., batch operations in studio),
> > because it needs to get done.
> >
>
>
--
Alex Karasulu
My Blog :: http://www.jroller.com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA :: http://mina.apache.org
To set up a meeting with me: http://tungle.me/AlexKarasulu
Re: JVM wrapper restarts too soon
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Aaron,
You might want to have a look at the 'wrapper.ping.timeout' configuration parameter.
http://wrapper.tanukisoftware.com/doc/english/prop-ping-timeout.html
Hope this helps,
Pierre-Arnaud
On 12 oct. 2010, at 19:20, Aaron J Angel wrote:
> When the directory service is busy with large operations, the JVM
> wrapper kills the jvm and restarts after several unanswered pings.
> Often times, I find that when the wrapper starts, it takes 2 or 3 tries
> to get it up and running because it is impatient.
>
> What settings can I tweak to make the wrapper more patient? Large
> operations are quite common and I'm okay with the system hanging a bit
> while it processes all the data (e.g., batch operations in studio),
> because it needs to get done.
>