www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Turck <james.tu...@db.com>
Subject mod_jserv/3792: Threads in Servlet not being killed on class reload
Date Fri, 29 Jan 1999 12:52:40 GMT

>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
>Originator:     james.turck@db.com
>Release:        Apache 1.3.2 Apache Jserv 1.0b2
SunOS sclsd1 5.6 Generic_105181-05 sun4u sparc SUNW,Ultra-5_10
gcc version 2.8.1
Apache Jserv 1.0b2

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.
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.
Possibly starting the main Servlet in a new threadgroup and then killing all threads in that
group on class reload would solve the problem.
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@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!         ]

View raw message