You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Timothy Ward (JIRA)" <ji...@apache.org> on 2016/09/22 07:23:21 UTC

[jira] [Commented] (ARIES-1617) Hikari pools are not closed by the JPA Resource Providers

    [ https://issues.apache.org/jira/browse/ARIES-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512453#comment-15512453 ] 

Timothy Ward commented on ARIES-1617:
-------------------------------------

A Mislabeled commit was attached to the wrong JIRA

Commit 1761786 from Timothy Ward in branch 'aries/trunk'
[ https://svn.apache.org/r1761786 ]
ARIES-1616 Clean up Local JPA resources properly


> Hikari pools are not closed by the JPA Resource Providers
> ---------------------------------------------------------
>
>                 Key: ARIES-1617
>                 URL: https://issues.apache.org/jira/browse/ARIES-1617
>             Project: Aries
>          Issue Type: Bug
>          Components: tx-control
>    Affects Versions: tx-control-0.0.1
>            Reporter: Timothy Ward
>             Fix For: tx-control-0.0.2
>
>
> When shutting down the Aries JPA Resource Provider (both XA and non XA) the Hikari pool (if created) does not get closed. This leads to Hikari maintenance threads being left running, which leaks class loaders and may prevent framework shutdown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)