Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Date: Fri, 11 Feb 2005 23:24:26 +0100
Message-Id: <200502112224.j1BMOQCO024259@ajax.apache.org>
From: bugzilla@apache.org
To: commons-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 33529]  -
    [dbcp] improved Exception nesting in ConnectionPool

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33529>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33529


dirk.verbeeck@pandora.be changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


------- Additional Comments From dirk.verbeeck@pandora.be  2005-02-11 23:24 -------
Good suggestion. The underlying exception was already visible in the stacktrace
but the message can be improved.

How about using the following catch block in the connect method.

} catch(SQLException e) {
    throw e;
} catch(NoSuchElementException e) {
    throw new SQLNestedException("Cannot get a connection, pool error: " +
e.getMessage(), e);
} catch(RuntimeException e) {
    throw e;
} catch(Exception e) {
    throw new SQLNestedException("Cannot get a connection, general error: " +
e.getMessage(), e);
}


-- Dirk 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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