100 * does not return until the invoked method returns in the target VM.
101 * If the invoked method throws an exception, this method will throw
102 * an {@link InvocationException} which contains a mirror to the exception
103 * object thrown.
104 * <p>
105 * Object arguments must be assignment compatible with the argument type
106 * (This implies that the argument type must be loaded through the
107 * enclosing class' class loader). Primitive arguments must be
108 * either assignment compatible with the argument type or must be
109 * convertible to the argument type without loss of information.
110 * If the method being called accepts a variable number of arguments,
111 * then the last argument type is an array of some component type.
112 * The argument in the matching position can be omitted, or can be null,
113 * an array of the same component type, or an argument of the
114 * component type followed by any number of other arguments of the same
115 * type. If the argument is omitted, then a 0 length array of the
116 * component type is passed. The component type can be a primitive type.
117 * Autoboxing is not supported.
118 *
119 * See Section 5.2 of
120 * <cite>The Java™ Language Specification</cite>
121 * for more information on assignment compatibility.
122 * <p>
123 * By default, all threads in the target VM are resumed while
124 * the method is being invoked if they were previously
125 * suspended by an event or by {@link VirtualMachine#suspend} or
126 * {@link ThreadReference#suspend}. This is done to prevent the deadlocks
127 * that will occur if any of the threads own monitors
128 * that will be needed by the invoked method.
129 * Note, however, that this implicit resume acts exactly like
130 * {@link ThreadReference#resume}, so if the thread's suspend
131 * count is greater than 1, it will remain in a suspended state
132 * during the invocation and thus a deadlock could still occur.
133 * By default, when the invocation completes,
134 * all threads in the target VM are suspended, regardless their state
135 * before the invocation.
136 * It is possible that
137 * breakpoints or other events might occur during the invocation.
138 * This can cause deadlocks as described above. It can also cause a deadlock
139 * if invokeMethod is called from the client's event handler thread. In this
140 * case, this thread will be waiting for the invokeMethod to complete and
|
100 * does not return until the invoked method returns in the target VM.
101 * If the invoked method throws an exception, this method will throw
102 * an {@link InvocationException} which contains a mirror to the exception
103 * object thrown.
104 * <p>
105 * Object arguments must be assignment compatible with the argument type
106 * (This implies that the argument type must be loaded through the
107 * enclosing class' class loader). Primitive arguments must be
108 * either assignment compatible with the argument type or must be
109 * convertible to the argument type without loss of information.
110 * If the method being called accepts a variable number of arguments,
111 * then the last argument type is an array of some component type.
112 * The argument in the matching position can be omitted, or can be null,
113 * an array of the same component type, or an argument of the
114 * component type followed by any number of other arguments of the same
115 * type. If the argument is omitted, then a 0 length array of the
116 * component type is passed. The component type can be a primitive type.
117 * Autoboxing is not supported.
118 *
119 * See Section 5.2 of
120 * <cite>The Java Language Specification</cite>
121 * for more information on assignment compatibility.
122 * <p>
123 * By default, all threads in the target VM are resumed while
124 * the method is being invoked if they were previously
125 * suspended by an event or by {@link VirtualMachine#suspend} or
126 * {@link ThreadReference#suspend}. This is done to prevent the deadlocks
127 * that will occur if any of the threads own monitors
128 * that will be needed by the invoked method.
129 * Note, however, that this implicit resume acts exactly like
130 * {@link ThreadReference#resume}, so if the thread's suspend
131 * count is greater than 1, it will remain in a suspended state
132 * during the invocation and thus a deadlock could still occur.
133 * By default, when the invocation completes,
134 * all threads in the target VM are suspended, regardless their state
135 * before the invocation.
136 * It is possible that
137 * breakpoints or other events might occur during the invocation.
138 * This can cause deadlocks as described above. It can also cause a deadlock
139 * if invokeMethod is called from the client's event handler thread. In this
140 * case, this thread will be waiting for the invokeMethod to complete and
|