You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2005/03/23 23:43:22 UTC
[jira] Created: (DIRMINA-12) Timing dependent deadlock
Timing dependent deadlock
-------------------------
Key: DIRMINA-12
URL: http://issues.apache.org/jira/browse/DIRMINA-12
Project: MINA
Type: Bug
Environment: Linux Fedora Core 3
JDK Versions:
java version "1.5.0_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09)
Java HotSpot(TM) Client VM (build 1.5.0_02-b09, mixed mode, sharing)
Trustin,java version "1.5.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode)
Reporter: Alex Karasulu
Assigned to: Trustin Lee
Priority: Blocker
Fix For: 0.7
Trustin,
Ok just so there is no confusion with the shutdown issues we've been having I tried to reproduce the deadlock by just rTrustin,
Ok just so there is no confusion with the shutdown issues we've been having I tried to reproduce the deadlock by just running the MINA tests. So the apacheds stuff is not in the picture at all. So I was finally able to catch the deadlock using the following test case:
./src/test/org/apache/mina/examples/echoserver/AcceptorTest.java.
The deadlock occurs on my machine 1 out of every 10 runs when running using shell with maven. Here's the thread dump. I've asked enrique to try this on his machine as well to make sure.
Signal Dispatcher@3 daemon prio=10, in group "system", status: RUNNING
Finalizer@4 daemon prio=8, in group "system", status: WAIT
wait():-1, Object.java
remove():116, ReferenceQueue.java
remove():132, ReferenceQueue.java
run():159, Finalizer.java
Reference Handler@5 daemon prio=10, in group "system", status: WAIT
wait():-1, Object.java
wait():474, Object.java
run():116, Reference.java
main@1 prio=5, in group "main", status: WAIT
wait():-1, Object.java
wait():474, Object.java
bind():126, SocketAcceptor.java
bind():79, SocketAcceptor.java
setUp():77, AbstractTest.java
runBare():125, TestCase.java
protect():106, TestResult.java
runProtected():124, TestResult.java
run():109, TestResult.java
run():118, TestCase.java
runTest():208, TestSuite.java
run():203, TestSuite.java
run():325, JUnitTestRunner.java
executeInVM():848, JUnitTask.java
execute():556, JUnitTask.java
execute():532, JUnitTask.java
perform():341, Task.java
doTag():185, AntTag.java
run():279, TagScript.java
run():135, ScriptBlock.java
invokeBody():233, TagSupport.java
doTag():88, IfTag.java
run():279, TagScript.java
run():135, ScriptBlock.java
runBodyTag():79, MavenGoalTag.java
performAction():110, MavenGoalTag.java
fire():639, Goal.java
attain():575, Goal.java
attainPrecursors():488, Goal.java
attain():573, Goal.java
attainPrecursors():488, Goal.java
attain():573, Goal.java
attainGoals():671, PluginManager.java
attainGoals():263, MavenSession.java
doMain():488, App.java
main():1239, App.java
invoke0():-1, NativeMethodAccessorImpl.java
invoke():39, NativeMethodAccessorImpl.java
invoke():25, DelegatingMethodAccessorImpl.java
invoke():585, Method.java
run():551, Forehead.java
main():581, Forehead.java
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (DIRMINA-12) Timing dependent deadlock
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-12?page=history ]
Alex Karasulu closed DIRMINA-12:
--------------------------------
It works like a champion after 100 runs.
> Timing dependent deadlock
> -------------------------
>
> Key: DIRMINA-12
> URL: http://issues.apache.org/jira/browse/DIRMINA-12
> Project: MINA
> Type: Bug
> Environment: Linux Fedora Core 3
> JDK Versions:
> java version "1.5.0_02"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09)
> Java HotSpot(TM) Client VM (build 1.5.0_02-b09, mixed mode, sharing)
> Trustin,java version "1.5.0_01"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
> Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode)
> Reporter: Alex Karasulu
> Assignee: Trustin Lee
> Priority: Blocker
> Fix For: 0.7
>
> Trustin,
> Ok just so there is no confusion with the shutdown issues we've been having I tried to reproduce the deadlock by just rTrustin,
> Ok just so there is no confusion with the shutdown issues we've been having I tried to reproduce the deadlock by just running the MINA tests. So the apacheds stuff is not in the picture at all. So I was finally able to catch the deadlock using the following test case:
> ./src/test/org/apache/mina/examples/echoserver/AcceptorTest.java.
> The deadlock occurs on my machine 1 out of every 10 runs when running using shell with maven. Here's the thread dump. I've asked enrique to try this on his machine as well to make sure.
> Signal Dispatcher@3 daemon prio=10, in group "system", status: RUNNING
> Finalizer@4 daemon prio=8, in group "system", status: WAIT
> wait():-1, Object.java
> remove():116, ReferenceQueue.java
> remove():132, ReferenceQueue.java
> run():159, Finalizer.java
> Reference Handler@5 daemon prio=10, in group "system", status: WAIT
> wait():-1, Object.java
> wait():474, Object.java
> run():116, Reference.java
> main@1 prio=5, in group "main", status: WAIT
> wait():-1, Object.java
> wait():474, Object.java
> bind():126, SocketAcceptor.java
> bind():79, SocketAcceptor.java
> setUp():77, AbstractTest.java
> runBare():125, TestCase.java
> protect():106, TestResult.java
> runProtected():124, TestResult.java
> run():109, TestResult.java
> run():118, TestCase.java
> runTest():208, TestSuite.java
> run():203, TestSuite.java
> run():325, JUnitTestRunner.java
> executeInVM():848, JUnitTask.java
> execute():556, JUnitTask.java
> execute():532, JUnitTask.java
> perform():341, Task.java
> doTag():185, AntTag.java
> run():279, TagScript.java
> run():135, ScriptBlock.java
> invokeBody():233, TagSupport.java
> doTag():88, IfTag.java
> run():279, TagScript.java
> run():135, ScriptBlock.java
> runBodyTag():79, MavenGoalTag.java
> performAction():110, MavenGoalTag.java
> fire():639, Goal.java
> attain():575, Goal.java
> attainPrecursors():488, Goal.java
> attain():573, Goal.java
> attainPrecursors():488, Goal.java
> attain():573, Goal.java
> attainGoals():671, PluginManager.java
> attainGoals():263, MavenSession.java
> doMain():488, App.java
> main():1239, App.java
> invoke0():-1, NativeMethodAccessorImpl.java
> invoke():39, NativeMethodAccessorImpl.java
> invoke():25, DelegatingMethodAccessorImpl.java
> invoke():585, Method.java
> run():551, Forehead.java
> main():581, Forehead.java
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (DIRMINA-12) Timing dependent deadlock
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-12?page=comments#action_61434 ]
Alex Karasulu commented on DIRMINA-12:
--------------------------------------
Enrique it seems could not reproduce it with 15 tries. I will write a script to see if we can find it with more trials.
> Timing dependent deadlock
> -------------------------
>
> Key: DIRMINA-12
> URL: http://issues.apache.org/jira/browse/DIRMINA-12
> Project: MINA
> Type: Bug
> Environment: Linux Fedora Core 3
> JDK Versions:
> java version "1.5.0_02"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09)
> Java HotSpot(TM) Client VM (build 1.5.0_02-b09, mixed mode, sharing)
> Trustin,java version "1.5.0_01"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
> Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode)
> Reporter: Alex Karasulu
> Assignee: Trustin Lee
> Priority: Blocker
> Fix For: 0.7
>
> Trustin,
> Ok just so there is no confusion with the shutdown issues we've been having I tried to reproduce the deadlock by just rTrustin,
> Ok just so there is no confusion with the shutdown issues we've been having I tried to reproduce the deadlock by just running the MINA tests. So the apacheds stuff is not in the picture at all. So I was finally able to catch the deadlock using the following test case:
> ./src/test/org/apache/mina/examples/echoserver/AcceptorTest.java.
> The deadlock occurs on my machine 1 out of every 10 runs when running using shell with maven. Here's the thread dump. I've asked enrique to try this on his machine as well to make sure.
> Signal Dispatcher@3 daemon prio=10, in group "system", status: RUNNING
> Finalizer@4 daemon prio=8, in group "system", status: WAIT
> wait():-1, Object.java
> remove():116, ReferenceQueue.java
> remove():132, ReferenceQueue.java
> run():159, Finalizer.java
> Reference Handler@5 daemon prio=10, in group "system", status: WAIT
> wait():-1, Object.java
> wait():474, Object.java
> run():116, Reference.java
> main@1 prio=5, in group "main", status: WAIT
> wait():-1, Object.java
> wait():474, Object.java
> bind():126, SocketAcceptor.java
> bind():79, SocketAcceptor.java
> setUp():77, AbstractTest.java
> runBare():125, TestCase.java
> protect():106, TestResult.java
> runProtected():124, TestResult.java
> run():109, TestResult.java
> run():118, TestCase.java
> runTest():208, TestSuite.java
> run():203, TestSuite.java
> run():325, JUnitTestRunner.java
> executeInVM():848, JUnitTask.java
> execute():556, JUnitTask.java
> execute():532, JUnitTask.java
> perform():341, Task.java
> doTag():185, AntTag.java
> run():279, TagScript.java
> run():135, ScriptBlock.java
> invokeBody():233, TagSupport.java
> doTag():88, IfTag.java
> run():279, TagScript.java
> run():135, ScriptBlock.java
> runBodyTag():79, MavenGoalTag.java
> performAction():110, MavenGoalTag.java
> fire():639, Goal.java
> attain():575, Goal.java
> attainPrecursors():488, Goal.java
> attain():573, Goal.java
> attainPrecursors():488, Goal.java
> attain():573, Goal.java
> attainGoals():671, PluginManager.java
> attainGoals():263, MavenSession.java
> doMain():488, App.java
> main():1239, App.java
> invoke0():-1, NativeMethodAccessorImpl.java
> invoke():39, NativeMethodAccessorImpl.java
> invoke():25, DelegatingMethodAccessorImpl.java
> invoke():585, Method.java
> run():551, Forehead.java
> main():581, Forehead.java
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DIRMINA-12) Timing dependent deadlock
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-12?page=history ]
Trustin Lee resolved DIRMINA-12:
--------------------------------
Resolution: Fixed
I checked in fixes. Worker threads stopped themselves even if there were works to do (binding and unbinding).
> Timing dependent deadlock
> -------------------------
>
> Key: DIRMINA-12
> URL: http://issues.apache.org/jira/browse/DIRMINA-12
> Project: MINA
> Type: Bug
> Environment: Linux Fedora Core 3
> JDK Versions:
> java version "1.5.0_02"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09)
> Java HotSpot(TM) Client VM (build 1.5.0_02-b09, mixed mode, sharing)
> Trustin,java version "1.5.0_01"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
> Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode)
> Reporter: Alex Karasulu
> Assignee: Trustin Lee
> Priority: Blocker
> Fix For: 0.7
>
> Trustin,
> Ok just so there is no confusion with the shutdown issues we've been having I tried to reproduce the deadlock by just rTrustin,
> Ok just so there is no confusion with the shutdown issues we've been having I tried to reproduce the deadlock by just running the MINA tests. So the apacheds stuff is not in the picture at all. So I was finally able to catch the deadlock using the following test case:
> ./src/test/org/apache/mina/examples/echoserver/AcceptorTest.java.
> The deadlock occurs on my machine 1 out of every 10 runs when running using shell with maven. Here's the thread dump. I've asked enrique to try this on his machine as well to make sure.
> Signal Dispatcher@3 daemon prio=10, in group "system", status: RUNNING
> Finalizer@4 daemon prio=8, in group "system", status: WAIT
> wait():-1, Object.java
> remove():116, ReferenceQueue.java
> remove():132, ReferenceQueue.java
> run():159, Finalizer.java
> Reference Handler@5 daemon prio=10, in group "system", status: WAIT
> wait():-1, Object.java
> wait():474, Object.java
> run():116, Reference.java
> main@1 prio=5, in group "main", status: WAIT
> wait():-1, Object.java
> wait():474, Object.java
> bind():126, SocketAcceptor.java
> bind():79, SocketAcceptor.java
> setUp():77, AbstractTest.java
> runBare():125, TestCase.java
> protect():106, TestResult.java
> runProtected():124, TestResult.java
> run():109, TestResult.java
> run():118, TestCase.java
> runTest():208, TestSuite.java
> run():203, TestSuite.java
> run():325, JUnitTestRunner.java
> executeInVM():848, JUnitTask.java
> execute():556, JUnitTask.java
> execute():532, JUnitTask.java
> perform():341, Task.java
> doTag():185, AntTag.java
> run():279, TagScript.java
> run():135, ScriptBlock.java
> invokeBody():233, TagSupport.java
> doTag():88, IfTag.java
> run():279, TagScript.java
> run():135, ScriptBlock.java
> runBodyTag():79, MavenGoalTag.java
> performAction():110, MavenGoalTag.java
> fire():639, Goal.java
> attain():575, Goal.java
> attainPrecursors():488, Goal.java
> attain():573, Goal.java
> attainPrecursors():488, Goal.java
> attain():573, Goal.java
> attainGoals():671, PluginManager.java
> attainGoals():263, MavenSession.java
> doMain():488, App.java
> main():1239, App.java
> invoke0():-1, NativeMethodAccessorImpl.java
> invoke():39, NativeMethodAccessorImpl.java
> invoke():25, DelegatingMethodAccessorImpl.java
> invoke():585, Method.java
> run():551, Forehead.java
> main():581, Forehead.java
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira