I never bounce them - even with EOF ;)

> On Aug 5, 2020, at 07:07, Jesse Tayler via Webobjects-dev 
> <webobjects-dev@lists.apple.com> wrote:
> 
> What do you use to keep an eye on memory? JAVA has such an old-school 
> approach with the VM I use AWS and really don’t have any good automated 
> visualizing report on how instances or JAVA is running under the hood.
> 
> My apps seem to run for a long time as a few times my scheduler has failed 
> and they racked up 10X or even 100X normal sessions, but who knows what the 
> user patterns were really — I have had to increase my JAVA VM and set memory 
> stuff from JavaMonitor to keep things sane.
> 
> 
> 
>> On Aug 5, 2020, at 3:35 AM, Jérémy DE ROYER via Webobjects-dev 
>> <webobjects-dev@lists.apple.com> wrote:
>> 
>> Hi Aaron,
>> 
>> (I’m still using EOF) and, for the main apps, I bounce every morning.
>> 
>> After updates I sometimes forget to activate the schedules without any 
>> problems… but I’m used to do it in the pasts where I had a lot of meomry 
>> leaks so I still do it.
>> 
>> Jérémy
>> 
>>> Le 5 août 2020 à 00:04, Hugi Thordarson via Webobjects-dev 
>>> <webobjects-dev@lists.apple.com> a écrit :
>>> 
>>> Never. Uptime on my apps is usually weeks or months.
>>> 
>>> Cycled regularly when I used EOF though. That thing leaks.
>>> 
>>> - hugi
>>> 
>>> 
>>> 
>>>> On 4 Aug 2020, at 21:31, Aaron Rosenzweig via Webobjects-dev 
>>>> <webobjects-dev@lists.apple.com> wrote:
>>>> 
>>>> Personally I feel better bouncing my .woa instances daily. Even if it is a 
>>>> small site I have at least two instances and I gracefully cycle them on a 
>>>> daily schedule. I feel better knowing that it is fresh every morning for 
>>>> the new day. 
>>>> 
>>>> On the other hand, I could see an argument that a java app shouldn’t have 
>>>> any memory leaks. The garbage collector should get everything. If it 
>>>> cannot do so, then you’ve got something messed up in your app that you 
>>>> should track down and rectify. So maybe it’s better to just leave your 
>>>> .woa instances running forever until the next redeployment to get new 
>>>> features. 
>>>> 
>>>> What does the community do? Do you cycle often (daily, twice per day, or 
>>>> once per week) or do you leaving your instances running without a 
>>>> scheduled restart? 
>>>> 
>>>> Thanks to all those who chime in :-)
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
>>>> Help/Unsubscribe/Update your Subscription:
>>>> https://lists.apple.com/mailman/options/webobjects-dev/hugi%40karlmenn.is
>>>> 
>>>> This email sent to h...@karlmenn.is
>>> 
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/webobjects-dev/jeremy.deroyer%40ingencys.net
>>> 
>>> This email sent to jeremy.dero...@ingencys.net
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com
>> 
>> This email sent to jtay...@oeinc.com
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/kenlists%40anderhome.com
> 
> This email sent to kenli...@anderhome.com
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to