You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Sam Kim <ol...@ivyproductions.com> on 1999/03/18 20:48:34 UTC

mod_jserv/4084: servlet is not expiring at configured time

>Number:         4084
>Category:       mod_jserv
>Synopsis:       servlet is not expiring at configured time
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Mar 18 11:50:00 PST 1999
>Last-Modified:
>Originator:     oldman@ivyproductions.com
>Organization:
apache
>Release:        Apache 1.3.4 + Apache JServ 1.0b
>Environment:
Linux, JDK 1.1.7v1a
>Description:
I have a servlet that creates a DB handle in init() and closes it in destroy().
I put in a check to see if the DB handle was being closed at termination, but
it seems the servlet does not terminate when it was supposed to expire.  I guess
I haven't tested if destroy() actually gets executed...
>How-To-Repeat:
Have the destroy() method do System.err.println() to check if it expires at set
expiration time.
>Fix:
No...
>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!         ]