-
Bug
-
Resolution: Other
-
P4
-
7, 8, 9, 10
-
generic
-
generic
JDB tests fails sometimes with:
"Caught unexpected exception while executing the test: nsk.share.Failure: Debuggee did not exit after 1 <cont> commands"
OR
Caught unexpected exception while executing the test: nsk.share.Failure: Debuggee did not exit after 2 <cont> commands
etc.. (see for example http://vmsqe-app.russia.sun.com/surl/IN)
Problem can be reproduced with high probability if host is overloaded (e.g. concurrent test execution). It seems like problem in problem in jdb test framework (package nsk.share.jdb).
"Caught unexpected exception while executing the test: nsk.share.Failure: Debuggee did not exit after 1 <cont> commands"
OR
Caught unexpected exception while executing the test: nsk.share.Failure: Debuggee did not exit after 2 <cont> commands
etc.. (see for example http://vmsqe-app.russia.sun.com/surl/IN)
Problem can be reproduced with high probability if host is overloaded (e.g. concurrent test execution). It seems like problem in problem in jdb test framework (package nsk.share.jdb).
- duplicates
-
JDK-6815172 intermittent caught_exception002 failure
- Closed
-
JDK-6948626 JDB stop_at003 test fails intermittently
- Closed
-
JDK-6754524 TTY: jdb 'monitor' command needs better user feedback when its actions occur
- Closed