make an initialization servlet that gets loaded when your application starts
up and make it use whatever methods are needed to start the JCE.

matt
----- Original Message -----
From: "Gerry Duhig" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>; "David Wall"
<[EMAIL PROTECTED]>
Sent: Tuesday, November 13, 2001 1:36 PM
Subject: Re: cryptography - slow starting????


> I guessed as much! How do I force it to happen at startup?
>
> Gerry
>
> ----- Original Message -----
> From: "David Wall" <[EMAIL PROTECTED]>
> To: "Tomcat Users List" <[EMAIL PROTECTED]>
> Sent: Tuesday, November 13, 2001 6:08 PM
> Subject: Re: cryptography - slow starting????
>
>
> > It's the SecureRandom initialization.  You could just force such an
> > initialization at startup so that startup has a bit of a slowdown, but
> then
> > it runs fast the rest of the time.
> >
> > David
> >
> >
> > ----- Original Message -----
> > From: "Gerry Duhig" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, November 13, 2001 10:02 AM
> > Subject: cryptography - slow starting????
> >
> >
> > Hi!
> >
> > I have successfully built a servlet that uses JCE to encrypt data and
> > deployed it under JBoss Tomcat 2.4.1-3.2.2.
> >
> > The very first access is VERY slow as the cryptography classes do some
> sort
> > of initialisation. I don't know what.
> >
> > Subsequent actions seem very quick.
> >
> > Is this to be expected? Can I speed it up? Can I get this initialisation
> to
> > take place at start-up before a user accesses the servlet?
> >
> > Gerry
> >
> >
> >
> >
> > --
> > To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> > For additional commands: <mailto:[EMAIL PROTECTED]>
> > Troubles with the list: <mailto:[EMAIL PROTECTED]>
> >
>
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to