[seam-issues] [JBoss JIRA] (JBSEAM-5072) Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context

Thu Sep 26 08:26:02 EDT 2013

    [ https://issues.jboss.org/browse/JBSEAM-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12807576#comment-12807576 ] 

Claus Elsborg commented on JBSEAM-5072:
---------------------------------------

It looks like java:global JNDI is not available until the application is fully deployed. 
This means that quartz jobs that fires during startup throws a javax.naming.NameNotFoundException: appname/jboss-seam/EjbSynchronizations -- service jboss.naming.context.java.global.appname.jboss-seam.EjbSynchronizations.
If Quartz jobs are persisted in a database, the quartz jobs gets scheduled during the QuartzDispatcher.java Startup. 
If using RAM store, it is normal to schedule the jobs by observing the org.jboss.seam.postInitialization event. But even here it still fails. After deployment is complete the jobs works fine.

For the described workaround to be useful I need a way to schedule quartz jobs during deployment or a least just after deployment completes in order to handle "misfires" during server down time. Any ideas of how to do this?

> Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context 
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-5072
>                 URL: https://issues.jboss.org/browse/JBSEAM-5072
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.2.0.GA, 2.2.1.Final, 2.2.2.Final
>            Reporter: Luan Cestari
>
> Description of problem:
> Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context. In other words, Seam can`t find the beans in context, even that they are there (due the annotations and logs that confirm that).
> EAP 6`s documentation that gives the steps to migrate Seam 2 applications: https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Application_Platform/6/html-single/Migration_Guide/index.html#sect-Migrate_Seam_2.2_Applications
> Version-Release number of selected component (if applicable):
> Seam 2.2 in EAP 6
> How reproducible:
> Just create a Seam and Quartz bean and another Seam and EJB bean that on Startup will lookup for Seam/Quartz bean, but can`t find it.
> Actual results:
> Can`t find the bean
> Expected results:
> Find the bean
> Additional info:
> salesforce link: https://c.na7.visual.force.com/apex/Case_View?id=500A000000CQzrg&sfdc.override=1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira