Upped memory guidance

[Nate Klingenstein]

Do we know what the validUntil time in the last signed edition of eduGAIN-less metadata was?  Do we anticipate that being poised on that day may be needed?

I ask because I've heard of IdP's that continued to operate on the last successfully loaded edition.  They logged horrible errors, but they didn't croak.

Happy glibc day, again,
Nate.

Semt frim mt iPone

> On Feb 19, 2016, at 15:53, Janemarie Duh <duhj at lafayette.edu> wrote:
> 
> Thank you, Tom. Yes: -Xmx1024m
> 
>> On 2/19/16 2:43 PM, Tom Scavo wrote:
>>> On Thu, Feb 18, 2016 at 7:08 PM, Janemarie Duh <duhj at lafayette.edu> wrote:
>>> 
>>> We just experienced our second production service incident since the
>>> InCommon production aggregate was synced with the preview aggregate.
>>> 
>>> On Monday the 15th (upon refreshing the metadata, and then again this
>>> evening, our IdP (v2.3.8 on RHEL 5.5) threw an out of memory error and
>>> stopped accepting requests.[1] Restarting the container (Tomcat 6)
>>> restored service. Java heap space is set to 1024K.
>> 
>> Is that a typo? Do you mean 1024MB?
>> 
>> Tom
> 
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net