You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "jiraposter@reviews.apache.org (JIRA)" <ji...@apache.org> on 2012/05/02 01:50:52 UTC
[jira] [Commented] (OOZIE-826) TestCoordKillXCommand's
testCoordKillXCommandUniqueness testcase is failing after interrupt changes
[ https://issues.apache.org/jira/browse/OOZIE-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266250#comment-13266250 ]
jiraposter@reviews.apache.org commented on OOZIE-826:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4959/
-----------------------------------------------------------
Review request for oozie, Mohammad Islam and Alejandro Abdelnur.
Summary
-------
https://issues.apache.org/jira/browse/OOZIE-826
Patch for 3.2 and trunk
This addresses bug oozie-826.
https://issues.apache.org/jira/browse/oozie-826
Diffs
-----
trunk/core/src/main/java/org/apache/oozie/command/coord/CoordKillXCommand.java 1332884
trunk/core/src/test/java/org/apache/oozie/command/coord/TestCoordKillXCommand.java 1332884
Diff: https://reviews.apache.org/r/4959/diff
Testing
-------
Thanks,
Virag
> TestCoordKillXCommand's testCoordKillXCommandUniqueness testcase is failing after interrupt changes
> ---------------------------------------------------------------------------------------------------
>
> Key: OOZIE-826
> URL: https://issues.apache.org/jira/browse/OOZIE-826
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: 3.2.0
> Reporter: Alejandro Abdelnur
> Priority: Critical
> Fix For: 3.2.0
>
>
> Some of the interrupt related changes are making callables to be executed after the services have been destroyed.
> {code}
> 14:27:29,129 ERROR TestCoordKillXCommand$MyCoordKillXCommand:536 - USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST] JOB[0000000-120501142722768-oozie-tucu-C] ACTION[-] Exception,
> java.lang.IllegalMonitorStateException
> at java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryRelease(ReentrantReadWriteLock.java:317)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1239)
> at java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.unlock(ReentrantReadWriteLock.java:992)
> at org.apache.oozie.util.MemoryLocks$LockToken.release(MemoryLocks.java:59)
> at org.apache.oozie.command.XCommand.releaseLock(XCommand.java:223)
> at org.apache.oozie.command.XCommand.call(XCommand.java:296)
> at org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> 14:27:29,135 WARN CallableQueueService$CallableWrapper:542 - USER[-] GROUP[-] TOKEN[-] APP[-] JOB[-] ACTION[-] exception callable [coord_kill], E0607: Other error in operation [java.lang.IllegalMonitorStateException], {1}
> org.apache.oozie.command.CommandException: E0607: Other error in operation [java.lang.IllegalMonitorStateException], {1}
> at org.apache.oozie.command.XCommand.call(XCommand.java:318)
> at org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.IllegalMonitorStateException
> at java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryRelease(ReentrantReadWriteLock.java:317)
> at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1239)
> at java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.unlock(ReentrantReadWriteLock.java:992)
> at org.apache.oozie.util.MemoryLocks$LockToken.release(MemoryLocks.java:59)
> at org.apache.oozie.command.XCommand.releaseLock(XCommand.java:223)
> at org.apache.oozie.command.XCommand.call(XCommand.java:296)
> ... 4 more
> 14:27:30,603 INFO TestCoordKillXCommand:539 - Waiting up to [2,979] msec
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira