[jboss-jira] [JBoss JIRA] Commented: (JBAS-4083) Ejb timers fire before the ear completely deploys

[Kahli Burke (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-4083?page=comments#action_12368528 ] 
            
Kahli Burke commented on JBAS-4083:
-----------------------------------

I have seen this occur with a Seam application I'm working on.  If a timer is past the time it is due, the timer will fire as soon as the Seam jar is deployed, but when the rest of the application has not yet been deployed.  Since the seam dispatcher needs the web application to be available for its lifecycle to work, the timer event fails.

> Ejb timers fire before the ear completely deploys
> -------------------------------------------------
>
>                 Key: JBAS-4083
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4083
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB2, Scheduling/Timers
>    Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA
>         Environment: WinNT, Sun JDK 1.5
>            Reporter: Vadim Kopichenko
>         Assigned To: Scott M Stark
>
> Consider the following usecase.
> The is an ear containing several ejb modules.
> One of them has a ejb2.1 timed cmp entity bean.
> If the timer associated with the bean fires during application deployment unexpected errors happen, cause other beans could be not already deployed.
> This breaks application logic.
> The problem happens both while server starts/stops and while hot ear's redeployment.
> It would be much better if timers began to fire after the application had completely deployed.
> I've also experienced a similar problem with undeployment.
> Timer code was executed about a half of second after the undeployment had begun. Several ejb modules had been already undeployed by that moment.
> I guess that timer actually fired exactly before the undeployment had begun but the ejbTimeout executed later due to threads syncronization issue.
> Please, try also to investigate if this can be avoided.
> PS
> Some kind of patch or workaround for 4.0.5 (or even a hint about how this can be fixed) would be greatly appreciated.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira