[jboss-jira] [JBoss JIRA] Reopened: (JBAS-7926) Quartz RA: Endpoint deactivation immediately stops classloader of (long running) quartz job

[Jason Greene (JIRA)]

     [ https://issues.jboss.org/browse/JBAS-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene reopened JBAS-7926:
--------------------------------



Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all unscheduled AS6 issues that are a year or less old. This will make it easier community members to find and work on them.

Future releases beyond 6.1 can be done provided a community member steps up to coordinate them.

> Quartz RA: Endpoint deactivation immediately stops classloader of (long running) quartz job
> -------------------------------------------------------------------------------------------
>
>                 Key: JBAS-7926
>                 URL: https://issues.jboss.org/browse/JBAS-7926
>             Project: Legacy JBoss Application Server 6 
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 6.0.0.M2
>            Reporter: Marcus Linke
>            Assignee: Ales Justin
>             Fix For: No Release
>
>         Attachments: connector.patch
>
>
> While undeploying/stopping the MDB the QuartzResourceAdapter's 'endpointDeactivation' hook calls the quartz scheduler method 'deleteJob(..)'. This method call is nonblocking and therefore the process of stopping the MDB is continued. As part of this the classloader of the quartz job is also stopped which may prevent a long running job to successfully complete. 
> One possible workaround may be to use a quartz job listener here to emulate the blocking behavior and wait until a running job completes. Eventually there is a need for a timeout value then, but this could be configured by the MDB itself via ActivationConfigProperties.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira