[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-898) Logging stays silent when a RuntimeException is thrown from preDestroy method

Nathan Wray (JIRA) jira-events at lists.jboss.org
Tue Sep 25 10:43:41 EDT 2007


    [ http://jira.jboss.com/jira/browse/EJBTHREE-898?page=comments#action_12378582 ] 
            
Nathan Wray commented on EJBTHREE-898:
--------------------------------------

I think the description of this issue is misleading, at least in my case, the WARN from TwoPhaseCoordinator.afterCompletion has no obvious cause.

I'm using an EJB interval timer and getting the following warning with each iteration.  I'm not seeing any other error or warning and everything seems to be working so it's not clear what the warning is referring to.  
This is the block of messages I get with each iteration.  I'm using If any addtl info is needed please let me know.
jboss-4.2.1.GA under xp and  seam nightly build jboss-seam-CVS.2007-08-26_23-34-36

2007-09-25 10:35:19,265 DEBUG [com.fsb.set.task.processor.TaskProcessor] Running task processor
2007-09-25 10:35:19,265 INFO  [STDOUT] Hibernate: select task0_.TASK_SK_SEQ as col_0_0_ from Task task0_ where task0_.STATUS=? and task0_.SERVER_IDENT=?
2007-09-25 10:35:19,281 INFO  [STDOUT] Hibernate: select count(task0_.TASK_SK_SEQ) as col_0_0_ from Task task0_ where task0_.STATUS=?
2007-09-25 10:35:19,281 INFO  [STDOUT] Hibernate: select task0_.TASK_SK_SEQ as TASK1_0_, task0_.OWNER as OWNER0_, task0_.CREATE_DATE as CREATE3_0_, task0_.COMPLETE_DATE as COMPLETE4_0_, task0_.RESET_AFTER_TIME_MILLIS as RESET5_0_, task0_.DESCRIPTION as DESCRIPT6_0_, task0_.STATUS as STATUS0_, task0_.TYPE as TYPE0_, task0_.SERVER_IDENT as SERVER9_0_, task0_.REQUEST_FILENAME as REQUEST10_0_, task0_.RESULT_BASE_FILENAME as RESULT11_0_ from Task task0_ where task0_.STATUS=? order by task0_.TASK_SK_SEQ asc
2007-09-25 10:35:19,312 INFO  [STDOUT] Hibernate: select task0_.TASK_SK_SEQ as col_0_0_ from Task task0_ where task0_.STATUS=? and task0_.RESET_AFTER_TIME_MILLIS<?
2007-09-25 10:35:19,328 WARN  [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoordinator.afterCompletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple at 1d3ecae

The task processor local is defined as
    @Asynchronous
    public Timer runTaskQueue(@Expiration
    Date date, @IntervalDuration
    Long interval);


The task processor class is declared as
@Stateless
@Name("taskProcessor")
public class TaskProcessor implements TaskProcessorInterface


The async call is kicked off from the @Create method of the following class:
@Stateful
@Startup
@Scope(ScopeType.APPLICATION)
@Name("taskProcessorDriver")
public class TaskProcessorDriver implements TaskProcessorDriverInterface







> Logging stays silent when a RuntimeException is thrown from preDestroy method
> -----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-898
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-898
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 4.2.0 GA
>            Reporter: Carlo de Wolf
>            Priority: Critical
>             Fix For: Branch_4_2
>
>
> 09:48:47,432 INFO  [STDOUT] ContainedBean.preDestroy
> 09:48:47,432 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoordinator.afterCompletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple at 1ccc3ea

-- 
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

        



More information about the jboss-jira mailing list