The test gets overloaded with MethodExitEvents, causing them to queue up (in 
the JDI queue) and continue to be processed by the test after the debuggee 
exits. This results in a VMDisconnectedException when the test tries to do the 
following after getting an event:

`    String str = ((MethodExitEvent)event).location().declaringType().name(); `

The test is suppose to add filters to execlude events for all non-test classes, 
but it is only filtering `java.*` and `sun.*`. There are also a very large 
number of `jdk.*` events coming in, and this is what is causing the event 
backlog and the processing of events after disconnect. Filtering out `jdk.*` 
events reduces the total number of events to a few dozen, and the test passes.

More details can be found in the CR.

Testing in progress: tier5 svc testing, and also running the failing test on 
all platforms (both debug and product).

-------------

Commit messages:
 - filter jdk.* clases

Changes: https://git.openjdk.org/jdk/pull/14480/files
 Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=14480&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8308499
  Stats: 7 lines in 1 file changed: 5 ins; 0 del; 2 mod
  Patch: https://git.openjdk.org/jdk/pull/14480.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/14480/head:pull/14480

PR: https://git.openjdk.org/jdk/pull/14480

Reply via email to