Hi Konstantin,
On 09.05.2010 11:38, Konstantin Kolinko wrote:
2010/5/9 Rainer Jung<rainer.j...@kippdata.de>:
On 07.05.2010 20:08, Filip Hanik - Dev Lists wrote:
On 05/07/2010 08:03 AM, Rainer Jung wrote:
It's there after JDK start with some version of the JDK. It's not
there if I only start a plain Java test doing only a sleep using the
same JDK.
well, if the app uses java.net.URL to a https, then this would make
sense that the thread got started with the webapp's class loader
Yes, but there is no app. The thread is there even when I remove all webapps
(except for the ROOT context I kept). I guess I need to do more systematic
testing.
Some more research,
looking at the source code that I mentioned:
1. "SunPKCS11-Solaris" is not the default name. The default name of
the class instance would be "SunPKCS11-Dummy".
You may want to look at the "/lib/security/java.security" file in your
JRE. It should be configured there.
Yes, I knew. PKCS is in there, but it is by default. The file hasn't
been touched.
Here is some, though failing. example of trying to use this class:
http://forums.sun.com/thread.jspa?threadID=5431010
2. sun.security.pkcs11.SunPKCS11 extends java.security.AuthProvider
3. SunPKCS11() constructor calls initToken(slotInfo) and that method
will call createPoller() if the token is not present in the slot.
(Thus apparently it starts waiting for the token).
4. It is said that PKCS11 "defines a platform-independent API to
cryptographic tokens, such as Hardware Security Modules (HSM) and
smart cards."
The point is:
- there is no cryptographic hardware involved in my case
- Tomcat default configuration used, HTTPS connector disabled
- no tc native
- I don't want to use PKCS or any other crypto
Nevertheless the threads show up and is spotted by the memory leak
detection during manager shutdown/restart as belonging to the manager
webapp (by means of the TCCL), although in the dump before the restart
its TCCL was the system class loader and the thread also gets started
when no manager gets deployed.
My first priority is to remove the false positive for the leak
detection, only the second prio is getting rid of the thread.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
