I have diagnosed the problem little more and seems to be connected with
creation of NamingContext
Our beans use another beans and in order to access them we need to cerate a
naming context and then do lookup of their home interface.
What we were doing so far and what worked with Jonas/Jeremie 2.0 was that in
setEntityContext we create new InitialContext and keep it open and then
close it in unsetEntityContext.
To diagnose the problem with Jonas/Jeremie 2.1.1 & 2.2.2 I have changed the
code so the context is created and closed in setEntityContext (I verified
that we always call Context.close()). The number of created threads didn't
change.
Then the next step was that I made the naming context static so all beans
are reusing the same naming context. The number of created threads decreased
a lot (we still create NamingContext for each HTTP request in the servlets)
which signals me that the threads are connected as a consequence of creation
of naming context and these threads are never terminated when the naming
context is closed.
My questions are:
1. Is it correct what we do with naming context (to keep it open for longer
time)?
2. Is there a connection between creating naming context in the beans and
creation of threads in Jonas JVM?
3. Is is a bug in Jonas/Jeremie that these threads are not cleand up when we
close the naming context or is it our problem?
Thanks to everybody for help with diagnosing this problem,
Miroslav Halas
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
