Java Programming and Web Technologies Quiz

When multiple threads are waiting on a monitor with the same priority, Java's notify() method wakes up one thread but does not specify which one. The thread scheduler determines which thread actually gets notified.

The Thread.halt() method was added in Java 9 and causes the thread to stop executing immediately, unlike other methods that might be deprecated or less direct ways to stop a thread.

Java's notify() and notifyAll() methods do not allow specifying which thread to wake up. When notify() is called on a monitor, it arbitrarily selects one thread from the waiting pool (if any are waiting). You have no control over which specific thread gets notified. This is intentional - it prevents thread starvation and encourages correct wait/notify usage patterns.

Options A, B, and C all cause threads to stop: System.exit() terminates the JVM, higher priority threads can preempt lower priority ones, and the stop() method (deprecated) stops threads. However, option D refers to 'halt method' - the Thread class has no such method. The correct method is interrupt() for cooperative cancellation, or stop() (deprecated), but halt() does not exist.

The HashSet contains Short objects. In line 3, s.add(i) adds short values 0-99 (autoboxed to Short). In line 4, s.remove(i-1) fails because i-1 is an int expression, and remove(int) treats it as an index (which doesn't apply to Set) or fails to find a matching object. The remove(Object) method would be needed, but the int type prevents that. So all 100 Short objects remain, and size() returns 100.

When System.exit(1) is called in the else block, the JVM terminates immediately. The finally block is NOT executed because System.exit() bypasses all normal termination logic. This is a key exception to the rule that finally blocks always execute - System.exit() is one of the rare cases where finally is skipped.