[
https://issues.apache.org/jira/browse/GERONIMO-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Muñoz updated GERONIMO-3832:
------------------------------------
Affects Version/s: 2.1.1
> Timers created using the Timer Services are not dropeed when the associated
> ejb module is stopped or undeployed.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-3832
> URL: https://issues.apache.org/jira/browse/GERONIMO-3832
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: OpenEJB
> Affects Versions: 2.0.2, 2.1.1
> Environment: windows 2000, jdk 1.5.0
> Reporter: Antonio Muñoz
> Priority: Minor
>
> When a periodic timer is scheduled using the geronimo timer service, the
> ejbtimeout method is called properly every time the period is reached. The
> problems comes when our ejb module is stopped or undeployed because the
> ejbtimeout is tried to be called again and again every time the period is
> reached even when the ejb module is already stopped. The logical solution
> should be stopping every timer associated to the ejb module is being stopped
> or undeployed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
