You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrei Dragomir (Created) (JIRA)" <ji...@apache.org> on 2011/12/02 15:57:40 UTC

[jira] [Created] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Cached HRegionInterface connections crash when getting UnknownHost exceptions
-----------------------------------------------------------------------------

                 Key: HBASE-4936
                 URL: https://issues.apache.org/jira/browse/HBASE-4936
             Project: HBase
          Issue Type: Bug
          Components: regionserver
    Affects Versions: 0.92.0
            Reporter: Andrei Dragomir


This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 

1. Start the HBase cluster locally, on network A (DNS A, etc)
2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
3. Change network location (go home)
4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)

If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 

The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Posted by "Andrei Dragomir (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrei Dragomir updated HBASE-4936:
-----------------------------------

    Attachment: HBASE-4936.patch
    
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4936
>                 URL: https://issues.apache.org/jira/browse/HBASE-4936
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>         Attachments: HBASE-4936.patch
>
>
> This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 
> The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164203#comment-13164203 ] 

Hudson commented on HBASE-4936:
-------------------------------

Integrated in HBase-TRUNK #2523 (See [https://builds.apache.org/job/HBase-TRUNK/2523/])
    HBASE-4936 Cached HRegionInterface connections crash when getting UnknownHost exceptions

stack : 
Files : 
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/catalog/CatalogTracker.java

                
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4936
>                 URL: https://issues.apache.org/jira/browse/HBASE-4936
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>            Assignee: Andrei Dragomir
>             Fix For: 0.94.0
>
>         Attachments: HBASE-4936-v2.patch, HBASE-4936.patch
>
>
> This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 
> The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164284#comment-13164284 ] 

Hudson commented on HBASE-4936:
-------------------------------

Integrated in HBase-TRUNK-security #24 (See [https://builds.apache.org/job/HBase-TRUNK-security/24/])
    HBASE-4936 Cached HRegionInterface connections crash when getting UnknownHost exceptions

stack : 
Files : 
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/catalog/CatalogTracker.java

                
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4936
>                 URL: https://issues.apache.org/jira/browse/HBASE-4936
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>            Assignee: Andrei Dragomir
>             Fix For: 0.94.0
>
>         Attachments: HBASE-4936-v2.patch, HBASE-4936.patch
>
>
> This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 
> The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162255#comment-13162255 ] 

Hadoop QA commented on HBASE-4936:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12505896/HBASE-4936.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/435//console

This message is automatically generated.
                
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4936
>                 URL: https://issues.apache.org/jira/browse/HBASE-4936
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>         Attachments: HBASE-4936.patch
>
>
> This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 
> The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Posted by "Ted Yu (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162272#comment-13162272 ] 

Ted Yu commented on HBASE-4936:
-------------------------------

+1 on patch.

@Andrei:
Please re-attach patch using --no-prefix option.
HadoopQA uses -p0 to apply patches.
                
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4936
>                 URL: https://issues.apache.org/jira/browse/HBASE-4936
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>         Attachments: HBASE-4936.patch
>
>
> This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 
> The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-4936:
-------------------------

       Resolution: Fixed
    Fix Version/s: 0.94.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Committed to TRUNK.  Thanks Andrei.
                
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4936
>                 URL: https://issues.apache.org/jira/browse/HBASE-4936
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>            Assignee: Andrei Dragomir
>             Fix For: 0.94.0
>
>         Attachments: HBASE-4936-v2.patch, HBASE-4936.patch
>
>
> This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 
> The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Posted by "Ted Yu (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu reassigned HBASE-4936:
-----------------------------

    Assignee: Andrei Dragomir
    
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4936
>                 URL: https://issues.apache.org/jira/browse/HBASE-4936
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>            Assignee: Andrei Dragomir
>         Attachments: HBASE-4936.patch
>
>
> This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 
> The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Posted by "Andrei Dragomir (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrei Dragomir updated HBASE-4936:
-----------------------------------

    Status: Patch Available  (was: Open)

Catch UnknownHostException
                
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4936
>                 URL: https://issues.apache.org/jira/browse/HBASE-4936
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>
> This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 
> The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161677#comment-13161677 ] 

Hadoop QA commented on HBASE-4936:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12505896/HBASE-4936.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/424//console

This message is automatically generated.
                
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4936
>                 URL: https://issues.apache.org/jira/browse/HBASE-4936
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>         Attachments: HBASE-4936.patch
>
>
> This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 
> The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162321#comment-13162321 ] 

Hadoop QA commented on HBASE-4936:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12506023/HBASE-4936-v2.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 javadoc.  The javadoc tool appears to have generated -160 warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    -1 findbugs.  The patch appears to introduce 71 new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit warnings.

     -1 core tests.  The patch failed these unit tests:
                       org.apache.hadoop.hbase.client.TestAdmin
                  org.apache.hadoop.hbase.replication.TestReplication
                  org.apache.hadoop.hbase.client.TestInstantSchemaChange

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/440//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/440//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/440//console

This message is automatically generated.
                
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4936
>                 URL: https://issues.apache.org/jira/browse/HBASE-4936
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>            Assignee: Andrei Dragomir
>         Attachments: HBASE-4936-v2.patch, HBASE-4936.patch
>
>
> This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 
> The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HBASE-4936) Cached HRegionInterface connections crash when getting UnknownHost exceptions

Posted by "Andrei Dragomir (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrei Dragomir updated HBASE-4936:
-----------------------------------

    Attachment: HBASE-4936-v2.patch

Re-attached with --no-prefix. Thanks Ted !
                
> Cached HRegionInterface connections crash when getting UnknownHost exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4936
>                 URL: https://issues.apache.org/jira/browse/HBASE-4936
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0
>            Reporter: Andrei Dragomir
>            Assignee: Andrei Dragomir
>         Attachments: HBASE-4936-v2.patch, HBASE-4936.patch
>
>
> This isssue is unlikely to come up in a cluster test case. However, for development, the following thing happens: 
> 1. Start the HBase cluster locally, on network A (DNS A, etc)
> 2. The region locations are cached using the hostname (mycomputer.company.com, 211.x.y.z - real ip)
> 3. Change network location (go home)
> 4. Start the HBase cluster locally. My hostname / ips are not different (mycomputer, 192.168.0.130 - new ip)
> If the region locations have been cached using the hostname, there is an UnknownHostException in CatalogTracker.getCachedConnection(ServerName sn), uncaught in the catch statements. The server will crash constantly. 
> The error should be caught and not rethrown, so that the cached connection expires normally. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira