[
https://issues.apache.org/jira/browse/TOMEE-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928104#comment-15928104
]
Romain Manni-Bucau commented on TOMEE-2027:
-------------------------------------------
If you have a fix a PR is fine, if you share a failing project to show us the
issue I (maybe personal) prefer a separate project yes
> 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)
