[
https://issues.apache.org/jira/browse/TOMEE-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved TOMEE-2027.
------------------------------------
Resolution: Auto Closed
Hi there!
We wanted to reach out and let you know that we're currently working on
cleaning up open issues in Jira that specifically impact unsupported versions,
including 1.7.x, 7.0.x, and 7.1.x.
If you had previously reported this issue on one of these unsupported versions,
we kindly ask you to check if the problem still persists and can be reproduced
on a supported version such as 8.0.x or 9.0.x. If you find that it is indeed
reproducible on a supported version, you're more than welcome to re-open this
issue.
Thanks!
> 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
> Priority: Major
> Attachments: QuartzPersistenceForEJBTimers2Test.java,
> SimpleBean.java, SimpleLocal.java, catalina.out, 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
(v8.20.10#820010)
