[jira] [Updated] (TOMEE-2027) Persistent timers eat connection pool

["Bodo Pfelzer (JIRA)" <ji...@apache.org>]

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

Bodo Pfelzer updated TOMEE-2027:
--------------------------------
    Attachment: QuartzPersistenceForEJBTimers2Test.java

Adding

DataSourceCreator=tomcat

caused the expected failure. I don't know how to add the required dependencies, so I moved the test case to tomee-jdbc and also copied

import-QuartzPersistenceForEJBTimersDB.sql

from openejb-core's test resources.

> Persistent timers eat connection pool
> -------------------------------------
>
>                 Key: TOMEE-2027
>                 URL: https://issues.apache.org/jira/browse/TOMEE-2027
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 7.0.4
>            Reporter: Bodo Pfelzer
>         Attachments: catalina.out, QuartzPersistenceForEJBTimers2Test.java, SimpleBean.java, SimpleLocal.java, system.properties
>
>
> I use persistent timers with a configuration similar to the one use in openejb-core test QuartzPersistenceForEJBTimersTest (see attached system.properties). A simple bean uses this timer service to create new a new timer whenever one expires. After 33 iterations the underlying connection pool is exhausted (see catalina.out). The same example works in tomee-1.7.x.
> I also tried to create an equivalent maven test based by modifying QuartzPersistenceForEJBTimersTest. But I was not able to reproduce the problem there. But it seems, that a different connection pool is used in the test environment.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)