geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-2114) Timer already cancelled error when attempting to grab a connection from a pool
Date Tue, 13 Jun 2006 19:50:30 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-2114?page=comments#action_12416069 ] 

Kevan Miller commented on GERONIMO-2114:
----------------------------------------

Jay, thanks for your help with this issue!

Seems to be memory-related. Jay reported that Increasing the heap size seems to avoid the
problem.

A RuntimeException or Error (e.g. an OutOfMemoryError) could cause a Timer to appear to be
"cancelled". We should try to give some indication in AbstractSinglePoolConnectionInterceptor.FillTask.run()
if an error occurs... 

> Timer already cancelled error when attempting to grab a connection from a pool
> ------------------------------------------------------------------------------
>
>          Key: GERONIMO-2114
>          URL: http://issues.apache.org/jira/browse/GERONIMO-2114
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: databases
>     Versions: 1.1
>  Environment: Linux w/ 2.6 kernel
> mySQL 5.0 w/ connector/j
> Geronimo 1.1-rc1
>     Reporter: Jay D. McHugh
>  Attachments: PaLM.war, build_plc.sql, 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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message