Luckily, we are using *NO* stateful session beans for this user. For each
user, we keep track of a timestamp of when the last time the getUser method
was called. If it has been more than an hour, we remove them and the next
call will pull that user back from the database, and back into the users
cache. But the thread that *reaps* this table gets spawned everytime we
restart, and since the program never exits, the threads do not get cleaned
up.
James Birchfield
Ironmax
a better way to buy, sell and rent construction equipment
5 Corporate Center
9960 Corporate Campus Drive,
Suite 2000
Louisville, KY 40223
|--------+------------------------------------>
| | Andrej Gabara |
| | <[EMAIL PROTECTED]> |
| | Sent by: |
| | owner-orion-interest@orion|
| | server.com |
| | |
| | |
| | 11/13/00 04:05 PM |
| | Please respond to |
| | Orion-Interest |
| | |
|--------+------------------------------------>
>------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: Orion-Interest <[EMAIL PROTECTED]>
|
| cc:
|
| Subject: RE: UserManager shutdown hook?
|
>------------------------------------------------------------------------------------------------------------------------------------|
How do you determine expired user references? Will you be
able to cleanup stateful session beans that were in use by
that user?
Thank's
Andrej
> -----Original Message-----
> From: Robert Krueger [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 13, 2000 7:43 AM
> To: Orion-Interest
> Subject: Re: UserManager shutdown hook?
>
>
> At 08:41 13.11.00 , you wrote:
>
> >We have implemented our own usermanager, and it all works
> great. But we
> >would like to know when the server is restarted at least, if
> not shutdown.
> >We start up a 'raper' thread, which is responsible for
> cleaning up expired
> >user references.
>
