You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2007/03/05 22:26:50 UTC

[jira] Resolved: (GERONIMO-2114) Timer already cancelled error when attempting to grab a connection from a pool

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

Kevan Miller resolved GERONIMO-2114.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-beta1

I've added code to capture and log runtime errors in TimerTask run methods. This should allow us to capture the root cause of problems like this.

I've only fixed in 2.0. Don't think it's critical enough to put in 1.2... If somebody feels otherwise, speak now... 

> Timer already cancelled error when attempting to grab a connection from a pool
> ------------------------------------------------------------------------------
>
>                 Key: GERONIMO-2114
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2114
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: databases
>    Affects Versions: 1.1
>         Environment: Linux w/ 2.6 kernel
> mySQL 5.0 w/ connector/j
> Geronimo 1.1-rc1
>            Reporter: Jay D. McHugh
>         Assigned To: Kevan Miller
>             Fix For: 2.0-beta1
>
>         Attachments: build_plc.sql, PaLM.war, plc_db.deploy.g1.1.xml
>
>
> After a relatively small number of connections to the database, a 'timer already cancelled' error comes up and the server no longer functions properly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.