1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
/*
* Copyright (c) 2018, 2020, Oracle and/or its affiliates. All rights reserved.
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
*
* This code is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License version 2 only, as
* published by the Free Software Foundation.
*
* This code is distributed in the hope that it will be useful, but WITHOUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
* version 2 for more details (a copy is included in the LICENSE file that
* accompanied this code).
*
* You should have received a copy of the GNU General Public License version
* 2 along with this work; if not, write to the Free Software Foundation,
* Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
*
* Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
* or visit www.oracle.com if you need additional information or have any
* questions.
*/
/*
* @test
* @modules jdk.jdi/com.sun.tools.jdi:+open java.base/jdk.internal.misc:+open
*
* @summary converted from VM Testbase nsk/jdi/MonitorContendedEnterRequest/MonitorContendedEnterRequest002.
* VM Testbase keywords: [jpda, jdi, feature_jdk6_jpda, vm6]
* VM Testbase readme:
* DESCRIPTION
* This is stress test for MonitorContendedEnterRequest and MonitorContendedEnterEvent, debugger force
* debuggee start several threads which simultaneously generate MonitorContendedEnteredEvents and checks that
* all events was received and contain correct information.
* Test executes class nsk.share.jdi.StressTestTemplate which uses JDI events testing
* framework based on classes from package nsk.share.jdi.*.
* This framework uses following scenario:
* - debugger VM forces debuggee VM to create number of objects which should generate events during test
* - debuggee performs event generation and stop at breakpoint
* - debugger reads data saved by debuggee's event generators and checks is only expected events was generated
* Stress test template allows to specify number of events which should be generated during test execution(parameter -eventsNumber)
* and number of threads which simultaneously generate events (parameter -threadsNumber).
* This test set eventsNumber to 25 and threadsNumber to 3, but because of framework design each requested event should
* be generated in 3 different way(through synchronized block, synchronized method and JNI MonitorEnter) and
* by 3 different threads, so actual number of generated events is (eventsNumber * 9), and actual number of threads generating
* events is (threadsNumber * 3).
*
* @library /vmTestbase
* /test/lib
* @build nsk.share.jdi.StressTestTemplate
* nsk.share.jdi.JDIEventsDebuggee
* nsk.share.jdi.MonitorEventsDebuggee
* @run main/othervm/native
* nsk.share.jdi.StressTestTemplate
* -verbose
* -arch=${os.family}-${os.simpleArch}
* -waittime=5
* -debugee.vmkind=java
* -transport.address=dynamic
* -debugee.vmkeys="${test.vm.opts} ${test.java.opts}"
* -allowMissedEvents MONITOR_CONTENTED_ENTER
* -eventTypes MONITOR_CONTENTED_ENTER
* -debuggeeClassName nsk.share.jdi.MonitorEventsDebuggee
* -eventsNumber 10
* -threadsNumber 2
*/
|
