AW: Recognize shutdown event in tomcats Realm instance

2018-08-30 Thread Arno Schäfer 
> Over-ride RealmBase.stopInternal() and don't forget to call
> super.stopInternal() when you do.

Thanks a lot Mark for the fast answer!
I have overlooked that, sorry.

- Arno

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Recognize shutdown event in tomcats Realm instance

2018-08-29 Thread Mark Thomas 
On 29/08/18 12:43, Arno Schäfer wrote:
> Hi all,
> 
> we use our own Realm implementation in our webapps. If tomcat shuts down, we 
> have to do some clean up
> in this instance to speed up the shutdown.
> In our web application we do this in the ServletContextListener instance in 
> 'contextDestroyed(...)' method.
> What is the right place to do this in tomcat's Realm instance? Do I have to 
> implement some notification code
> or does it work over a RealmBase method?

Over-ride RealmBase.stopInternal() and don't forget to call
super.stopInternal() when you do.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Recognize shutdown event in tomcats Realm instance

2018-08-29 Thread Arno Schäfer 
Hi all,

we use our own Realm implementation in our webapps. If tomcat shuts down, we 
have to do some clean up
in this instance to speed up the shutdown.
In our web application we do this in the ServletContextListener instance in 
'contextDestroyed(...)' method.
What is the right place to do this in tomcat's Realm instance? Do I have to 
implement some notification code
or does it work over a RealmBase method?

I found nothing about that in the documentation.

Best regards
- Arno
_

Vorsitzender des Aufsichtsrats: Lothar Pauly
Vorstand: Diederik Vos (CEO) ? Ralph Gillessen (COO) ? René Gawron (CFO)
Martin Hodgson (Executive Director Management Consulting)
SQS AG ? Stollwerckstraße 11 ? 51149 Köln
Sitz der Gesellschaft: Köln ? Amtsgericht Köln, HRB 12764

This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient
(or have received this e-mail in error) please notify the sender immediately 
and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden.