Metadata expiry and computing a new expiration time.

[Simon Fraser]

On Sat, Sep 12, 2015 at 11:15:52AM -0400, Tom Scavo wrote:

> On Sat, Sep 12, 2015 at 10:51 AM, Simon Fraser <srf at sanger.ac.uk> wrote:
> > On Sat, Sep 12, 2015 at 10:18:18AM -0400, Tom Scavo wrote:
> >>
> >> Simon, can you tell me how much heap you have allocated to the JVM?
> >
> > Tomcat7 is using its default:
> >
> >         JAVA_OPTS="-Djava.awt.headless=true -Xmx128M"
> 
> If and when you start to fiddle with that, and you find something that
> works, please report back. Much thanks in advance.

I'm a little confused, sorry - I'm not getting any memory or heap related
errors, the only thing in the logs is that it has successfully retrieved and
unmarshalled the federation metadata, and updated the expiry time, when it
hasn't. Is that heap related? If so I can experiment, I just don't know where
this request has come from.
 
> With respect to verifying the signature, if you could be specific
> about what stopped you in your tracks, that would be helpful. That
> particular aspect of the configuration is critical (as you know), and
> your experience might give us a clue what to recommend to deployers
> coming after you.

I apologise for being grouchy about the signature verification. 

To try this out, I would need to take a live service offline, which I will have
to book time for. I don't have a test environment that can download from the
federation. I'll see what I can do.

Simon.


-- 
 The Wellcome Trust Sanger Institute is operated by Genome Research 
 Limited, a charity registered in England with number 1021457 and a 
 company registered in England with number 2742969, whose registered 
 office is 215 Euston Road, London, NW1 2BE.