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

Posted to commits@tomee.apache.org by "Bodo Pfelzer (JIRA)" <ji...@apache.org> on 2017/03/16 11:11:41 UTC

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

Bodo Pfelzer created TOMEE-2027:
-----------------------------------

             Summary: 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, 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)