You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "John C. Landers (JIRA)" <de...@db.apache.org> on 2005/10/20 22:48:49 UTC

[jira] Created: (DERBY-635) Client socket connection doesn't report real socket exception

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
    Priority: Minor


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


[jira] Commented: (DERBY-635) Client socket connection doesn't report real socket exception

Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-635?page=comments#action_12332709 ] 

Kathey Marsden commented on DERBY-635:
--------------------------------------

Could you submit your change as a patch?




> 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
>     Priority: Minor

>
> 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


[jira] Commented: (DERBY-635) Client socket connection doesn't report real socket exception

Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-635?page=comments#action_12365937 ] 

Satheesh Bandaram commented on DERBY-635:
-----------------------------------------

Submitted this simple change (from e.getMessage() to e.getException().getMessage()) to trunk. (10.2) Please submit patches as attachments, instead of posting them in the description. This would allow contributors to grant licence to Apache, if they choose to.

Sending        java\client\org\apache\derby\client\net\NetAgent.java
Transmitting file data .
Committed revision 376777.

> 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


[jira] Commented: (DERBY-635) Client socket connection doesn't report real socket exception

Posted by "John C. Landers (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-635?page=comments#action_12332707 ] 

John C. Landers commented on DERBY-635:
---------------------------------------

Forgot to mention this is in org.apache.derby.client.net.NetAgent.java

> 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
>     Priority: Minor

>
> 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


[jira] Resolved: (DERBY-635) Client socket connection doesn't report real socket exception

Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
     [ 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


[jira] Assigned: (DERBY-635) Client socket connection doesn't report real socket exception

Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-635?page=all ]

Satheesh Bandaram reassigned DERBY-635:
---------------------------------------

    Assign To: Satheesh Bandaram

> 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

>
> 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


[jira] Closed: (DERBY-635) Client socket connection doesn't report real socket exception

Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-635?page=all ]
     
Satheesh Bandaram closed DERBY-635:
-----------------------------------


> 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