You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Sebastian Mancke (JIRA)" <ji...@apache.org> on 2007/04/16 10:54:15 UTC

[jira] Created: (DBCP-217) ding

ding
----

                 Key: DBCP-217
                 URL: https://issues.apache.org/jira/browse/DBCP-217
             Project: Commons Dbcp
          Issue Type: Bug
            Reporter: Sebastian Mancke




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Resolved: (DBCP-217) Closing of underlaying connection instead of the PoolGuardConnectionWrapper

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

Dain Sundstrom resolved DBCP-217.
---------------------------------

    Resolution: Fixed

Fixed as part of DBCP-11.

> Closing of underlaying connection instead of the PoolGuardConnectionWrapper
> ---------------------------------------------------------------------------
>
>                 Key: DBCP-217
>                 URL: https://issues.apache.org/jira/browse/DBCP-217
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Sebastian Mancke
>             Fix For: 1.3
>
>         Attachments: connectionCloseFix.patch
>
>
> Is state:
> If I obtain the Connection of a Statement (stmt.getConnection()), created with dbcp,
> the returned Object is the underlaying pooled connection. 
> Closing this connection multiple times may close the connection of another process.
> It should be:
> The Wrapper over the connection PoolGuardConnectionWrapper should be returned instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Updated: (DBCP-217) Closing of underlaying connection instead of the PoolGuardConnectionWrapper

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

Sebastian Mancke updated DBCP-217:
----------------------------------

    Attachment: connectionCloseFix.patch


This patch sets the wrapper (instance of PoolGuardConnectionWrapper)
as the connection of every created statement.

> Closing of underlaying connection instead of the PoolGuardConnectionWrapper
> ---------------------------------------------------------------------------
>
>                 Key: DBCP-217
>                 URL: https://issues.apache.org/jira/browse/DBCP-217
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Sebastian Mancke
>         Attachments: connectionCloseFix.patch
>
>
> Is state:
> If I obtain the Connection of a Statement (stmt.getConnection()), created with dbcp,
> the returned Object is the underlaying pooled connection. 
> Closing this connection multiple times may close the connection of another process.
> It should be:
> The Wrapper over the connection PoolGuardConnectionWrapper should be returned instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Updated: (DBCP-217) Closing of underlaying connection instead of the PoolGuardConnectionWrapper

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

Henri Yandell updated DBCP-217:
-------------------------------

    Fix Version/s: 1.3

> Closing of underlaying connection instead of the PoolGuardConnectionWrapper
> ---------------------------------------------------------------------------
>
>                 Key: DBCP-217
>                 URL: https://issues.apache.org/jira/browse/DBCP-217
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Sebastian Mancke
>             Fix For: 1.3
>
>         Attachments: connectionCloseFix.patch
>
>
> Is state:
> If I obtain the Connection of a Statement (stmt.getConnection()), created with dbcp,
> the returned Object is the underlaying pooled connection. 
> Closing this connection multiple times may close the connection of another process.
> It should be:
> The Wrapper over the connection PoolGuardConnectionWrapper should be returned instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Updated: (DBCP-217) Closing of underlaying connection instead of the PoolGuardConnectionWrapper

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

Sebastian Mancke updated DBCP-217:
----------------------------------

          Description: 

Is state:
If I obtain the Connection of a Statement (stmt.getConnection()), created with dbcp,
the returned Object is the underlaying pooled connection. 
Closing this connection multiple times may close the connection of another process.

It should be:
The Wrapper over the connection PoolGuardConnectionWrapper should be returned instead.


    Affects Version/s: 1.2.2
              Summary: Closing of underlaying connection instead of the PoolGuardConnectionWrapper  (was: ding)

> Closing of underlaying connection instead of the PoolGuardConnectionWrapper
> ---------------------------------------------------------------------------
>
>                 Key: DBCP-217
>                 URL: https://issues.apache.org/jira/browse/DBCP-217
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Sebastian Mancke
>
> Is state:
> If I obtain the Connection of a Statement (stmt.getConnection()), created with dbcp,
> the returned Object is the underlaying pooled connection. 
> Closing this connection multiple times may close the connection of another process.
> It should be:
> The Wrapper over the connection PoolGuardConnectionWrapper should be returned instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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