commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15123] New: - Incorrect stack trace shown when abandoned connections are closed
Date Thu, 05 Dec 2002 23:24:04 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15123>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15123

Incorrect stack trace shown when abandoned connections are closed

           Summary: Incorrect stack trace shown when abandoned connections
                    are closed
           Product: Commons
           Version: 1.0 Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: shankar@cotagesoft.com


The stack trace shown when an abandoned connection is closed
(removeAbandoned=true, logAbandoned=true) is the wrong one: it's the trace of
where the connection was *first created* from, not where it was *last allocated*
from.

I believe the cause is as simple as a missing setStackTrace() call in
AbandonedObjectPool.borrowObject(). (the createdBy object is only initialized in
the AbandonedTrace constructor, via the init() call, but is not reset each time
the object is allocated from the pool).

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message