You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by James Turck <ja...@db.com> on 1999/01/29 13:52:40 UTC
mod_jserv/3792: Threads in Servlet not being killed on class reload
>Number: 3792
>Category: mod_jserv
>Synopsis: Threads in Servlet not being killed on class reload
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: jserv
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Fri Jan 29 05:00:00 PST 1999
>Last-Modified:
>Originator: james.turck@db.com
>Organization:
apache
>Release: Apache 1.3.2 Apache Jserv 1.0b2
>Environment:
SunOS sclsd1 5.6 Generic_105181-05 sun4u sparc SUNW,Ultra-5_10
gcc version 2.8.1
Apache Jserv 1.0b2
>Description:
In our servlet we have a thread that polls for database updates. When we upload a new set of classes, the servlet is reinitialised with the new classes, and a new thread is created, however the old thread is not destroyed. This means that we have multiple database update threads. Whilst this is not a critical problem it does lead to us using up all of our database driver licences after some time.
>How-To-Repeat:
There is unfortunately no publicly available URL. A simple Servlet using a thread and showing a list of all threads in the group should support this though.
>Fix:
Possibly starting the main Servlet in a new threadgroup and then killing all threads in that group on class reload would solve the problem.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request ]
[from a developer. ]
[Reply only with text; DO NOT SEND ATTACHMENTS! ]