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

[Jack Cox (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12425302#action_12425302 ] 

Jack Cox commented on JBAS-4083:
--------------------------------

I am seeing the same behavior under JBoss AS 4.2.2

Is there a way to postpone activation of the timer until the containing ear is fully deployed.

Thanks

> Ejb timers fire before the ear completely deploys
> -------------------------------------------------
>
>                 Key: JBAS-4083
>                 URL: https://jira.jboss.org/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.4.GA, JBossAS-4.0.5.GA
>         Environment: WinNT, Sun JDK 1.5
>            Reporter: Vadim Kopichenko
>            Assignee: 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira