which vm for pier

> i have two new pier sites going up, and i am not sure where the issue
> is, but the headless server seems to die after a few hours..
>
> i got the vm from one of the cog prebuilt binaries, but i would have
> to go searching around to find out where..
>
> the details are:
>
> VM Version:     Croquet Closure Cog VM [CoInterpreter VMMaker.oscog-eem.140]
> VM Type:        32bit
> Endianness:     little
>
> anyway.. i was wondering which one everyone was currently using on
> their deployed systems..
>
> thanks!
>
> --
> ----
> peace,
> sergio
> photographer, journalist, visionary
>
> http://www.CodingForHire.com
> http://www.coffee-black.com
> http://www.painlessfrugality.com
> http://www.twitter.com/sergio_101
> http://www.facebook.com/sergio101
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> On Thu, Feb 2, 2012 at 23:20, sergio_101 <[hidden email]> wrote:
>> i have two new pier sites going up, and i am not sure where the issue
>> is, but the headless server seems to die after a few hours..
>>
>> i got the vm from one of the cog prebuilt binaries, but i would have
>> to go searching around to find out where..
>>
>> the details are:
>>
>> VM Version:     Croquet Closure Cog VM [CoInterpreter VMMaker.oscog-eem.140]
>> VM Type:        32bit
>> Endianness:     little
>>
>> anyway.. i was wondering which one everyone was currently using on
>> their deployed systems..
>>
>> thanks!
>>
>> --
>> ----
>> peace,
>> sergio
>> photographer, journalist, visionary
>>
>> http://www.CodingForHire.com
>> http://www.coffee-black.com
>> http://www.painlessfrugality.com
>> http://www.twitter.com/sergio_101
>> http://www.facebook.com/sergio101
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
>

>
> On 03 Feb 2012, at 18:00, John Toohey wrote:
>
>> When the COG VM is running in headless mode, any exceptions will cause
>> the VM to exit, logging the exception to the PharoDebug.log file.
>> Check the log for an exception.
>
> Correction: any unhandled exceptions at 'top level'.
> The 'older' behavior was to open a debugger.
> The result is the same in both cases: thread stopped.
>
> Most if not all servers will/should abandon and stop that request/thread but continue to service new requests until they run out of resources.
>