Keeping the server side object alive !!! 2007-01-15 - By Leon Rosenberg
Back
I think what you need is a ContextListener. With it, you will be
notified when the context (webapp) starts and can perform
initialization, and when the context is destroyed you can perform
de-initialization (stop your threads, cleanup ressources and such).
regards
Leon
On 1/15/07, Luis Rivera <luiggiilca@(protected)> wrote:
> Hi,
>
> I would like to know how could I jump start my web service in tomcat before
> any call from the client is made. My first version only needed to be
> stateless and that worked fine, since I noticed that each call from the
> client creates a new object in the server. However, now I would like to
> create some threads because I have a custom administration module
> (session/security/database).
>
> I can create them when the first call is made (using statics), but I would
> like to get rid of the overhead in the first call by somehow jump starting
> the application to do the loading and initialization that the application
> threads need to do, so that the when the first call is made, there is no
> overhead to pay.
>
> I am not sure. Is this possible? I am probably not understanding fully the
> servlet model or how tomcat/axis is supposed to be stateful at the server
> side.
>
> I guess, if there is a smarter way to do this without using threads/statics
> I would like to know where I could find an example.
>
> Thanks in advance,
> --Luis R.
>
>
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)
|
|
