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/10/10 15:29:20 UTC

[jira] [Resolved] (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:all-tabpanel ]

Timothy Ward resolved ARIES-1617.
---------------------------------
    Resolution: Fixed

A range of fixes applied:

revisions:
1764108, 1764109, 1764110, 1764111, 1764120

Together these common up much of the resource provider code to make it easier to do lifecycle tracking and prevent further leaks in the future.

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