[ http://jira.jboss.com/jira/browse/EJBTHREE-898?page=all ] Carlo de Wolf updated EJBTHREE-898: ----------------------------------- Fix Version/s: AS 4.2.0 CR2 -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-898?page=all ] Carlo de Wolf updated EJBTHREE-898: ----------------------------------- Fix Version/s: Branch_4_2 (was: AS 4.2.0 GA) -- 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

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

[ http://jira.jboss.com/jira/browse/EJBTHREE-898?page=comments#action_12389083 ] Nathan Wray commented on EJBTHREE-898: -------------------------------------- Thanks Kahli, that was a promising suggestion. I tried it this morning but it didn't resolve the warning messages with each iteration of the timer (30 seconds in this case). The only relief I've found is restricting com.arjuna to "ERROR" in jboss-log4j.xml, which isn't really a solution after all. I added the suggested "allowMultiple" directly at the beginning of the JTA segment: <properties depends="arjuna" name="jta"> <property name="com.arjuna.ats.jta.allowMultipleLastResources" value="true"/> and commented out the log4j restriction on com.arjuna. I'm getting the following every 30 seconds in the server log: 2007-11-26 09:23:33,671 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@1767f1 2007-11-26 09:24:03,609 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@18a36e6 2007-11-26 09:24:33,656 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@1f1c748 2007-11-26 09:25:03,609 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@1815614 2007-11-26 09:25:33,593 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@ff3813 2007-11-26 09:26:03,609 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@68ef48 -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-898?page=comments#action_12409970 ] Marek Nazarko commented on EJBTHREE-898: ---------------------------------------- I have the same error with Hibernate Search and Seam everytime I do full text search 13:33:59,374 WARN [arjLoggerI18N ?] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoordinator.afterCompletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@bb8cd2 -- 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

[ https://jira.jboss.org/jira/browse/EJBTHREE-898?page=com.atlassian.jira.p... ] Carlo de Wolf resolved EJBTHREE-898. ------------------------------------ Resolution: Done Assignee: Carlo de Wolf The code in EJBTHREE-1850 does additional logging when something fails in beforeCompletion or afterCompletion. -- 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