db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-635) Client socket connection doesn't report real socket exception
Date Fri, 10 Feb 2006 18:10:58 GMT
     [ http://issues.apache.org/jira/browse/DERBY-635?page=all ]
     
Satheesh Bandaram resolved DERBY-635:
-------------------------------------

    Fix Version: 10.2.0.0
     Resolution: Fixed

Fix merged into trunk.

> Client socket connection doesn't report real socket exception
> -------------------------------------------------------------
>
>          Key: DERBY-635
>          URL: http://issues.apache.org/jira/browse/DERBY-635
>      Project: Derby
>         Type: Improvement
>   Components: Network Client
>     Versions: 10.1.1.0
>     Reporter: John C. Landers
>     Assignee: Satheesh Bandaram
>     Priority: Minor
>      Fix For: 10.2.0.0

>
> When opening a connection with a network url: jdbc:derby://localhost:4000/data
> The netagent catchs the PrivilegedActionException but doesn't report the checked exception
in it.
> Changing these lines
>         try {
>             socket_ = (java.net.Socket) java.security.AccessController.doPrivileged(new
OpenSocketAction(server, port));
>         } catch (java.security.PrivilegedActionException e) {
>             throw new DisconnectException(this,
>                     e.getClass().getName() + " : Error opening socket to server " + server
+ " on port " + port + " with message : " + e.getMessage());
>         }
> To This returns the check exception information:
>         try {
>             socket_ = (java.net.Socket) java.security.AccessController.doPrivileged(new
OpenSocketAction(server, port));
>         } catch (java.security.PrivilegedActionException e) {
>             throw new DisconnectException(this,
>                     e.getException().getClass().getName() + " : Error opening socket
to server " + server + " on port " + port + " with message : " + e.getException().getMessage());
>         }
> It currently reports messages like this:
> Caused by: java.sql.SQLException: org.apache.derby.client.am.SqlException: java.security.PrivilegedActionException
: Error opening socket to server localhost on port 1527 with message : null
> With this fix it reports:
> org.apache.derby.client.am.DisconnectException: java.net.ConnectException : Error opening
socket to server localhost on port 1527 with message : Connection refused: connect

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message