You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2006/03/20 16:51:34 UTC
DO NOT REPLY [Bug 39036] New: - Thread Deadlock using Graph Results
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39036>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39036
Summary: Thread Deadlock using Graph Results
Product: JMeter
Version: 2.1.1
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Main
AssignedTo: jmeter-dev@jakarta.apache.org
ReportedBy: eric.dalquist@doit.wisc.edu
Using a large thread group I can consistently lock up jMeter while the Graph
Results listener is active. Once the program locks I did a thread dump and every
sampling thread is locked waiting to lock the GraphVisualizer object. The
GraphVisualizer object is locked by a thread updating it and that thread is
waiting to lock a swing component which is locked by the AWT-Event thread. The
thread dump is available here:
https://mywebspace.wisc.edu/dalquist/web/jMeter/ThreadDump.txt and graph of the
threads & locks here: https://mywebspace.wisc.edu/dalquist/web/jMeter/locktree1.png
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 39036] - Thread Deadlock using Graph Results
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39036>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39036
------- Additional Comments From sebb@apache.org 2006-03-21 14:47 -------
More likely a bug in JMeter which is exposed by the dual-core system.
It would be useful to know if the problem occurs with Java 1.4 as well - if
that is easy for you to test.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 39036] - Thread Deadlock using Graph Results
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39036>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39036
------- Additional Comments From woolfel@yahoo.com 2006-03-20 19:14 -------
doh! if that's the case, then it would appear to be an issue with JDK1.5 on dual
core CPU's. I tried searching Sun's bugparade and didn't see any issues related
to dual core.
peter
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 39036] - Thread Deadlock using Graph Results
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39036>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39036
sebb@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
------- Additional Comments From sebb@apache.org 2006-03-20 18:35 -------
I can't reproduce this with 200 threads using the Java Sampler (the sampler
type should not affect the listeners).
What type of system are you using? OS/Java?
Please can you attach a test case and jmeter.log output (obliterate any
sensitive data first)
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 39036] - Thread Deadlock using Graph Results
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39036>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39036
------- Additional Comments From eric.dalquist@doit.wisc.edu 2006-03-21 18:45 -------
Of course now I'm having problems reproducing the deadlock. I have made some
modifications to the test script I'm using. I'll see if I can find the one that
was causing the problem and reproduce it. As soon as I can I will also try to
reproduce the problem on JDK1.4.
After doing a bit more research I'm wondering if this is a JMeter issue or JDK
issue. According to the JavaDocs the setText() method of JTextComponent is ok to
call from a worker thread and in the thread dump that is all that appears to be
happening.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
DO NOT REPLY [Bug 39036] - Thread Deadlock using Graph Results
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=39036>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39036
------- Additional Comments From eric.dalquist@doit.wisc.edu 2006-03-20 19:03 -------
I just realized I could be seeing this more regularly since we are running
JMeter on dual CPU or dual core CPU machines. All running Windows XP and JDK1.5
I'll work on getting a test case & log up today.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org