[jira] [Updated] (TOMEE-2825) Connection tracking for database connections

["CS Tan (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TOMEE-2825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

CS Tan updated TOMEE-2825:
--------------------------
    Attachment: Connection.GIF

> Connection tracking for database connections
> --------------------------------------------
>
>                 Key: TOMEE-2825
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2825
>             Project: TomEE
>          Issue Type: New Feature
>            Reporter: Jonathan Gallimore
>            Assignee: Jonathan Gallimore
>            Priority: Major
>         Attachments: Connection.GIF
>
>
> Consider some code where in an EJB we do something like this:
>  
> {{@Resource}}{{private DataSource ds;}}
> {{}}{{public void doWork() {}}{{  }}
> {{  final Connection conn = ds.getConnection();}}{{  }}
> {{  // do something with the connection}}{{ }}
> {{  // forget to close it}}
> {{} }}{{// transaction ends or connection object goes out of scope}}
>  
> This ticket could potentially go in a number of different directions:
>  * TomEE could provide additional connection tracking like we do for JCA resource adapter connections
>  * Use the Tomcat jdbcInterceptors, document these on the TomEE website with examples
>  * Do other connection pools provide connection tracking? We could consider introducing support for these.
> First step would be to gather some examples where connections are not closed, and TomEE could track them, but doesn't - particularly if competing app servers are able to track and cleanup.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)