
- •Contents at a Glance
- •Contents
- •About the Authors
- •About the Technical Reviewer
- •Acknowledgments
- •Introduction
- •Oracle Java Certifications: Overview
- •FAQ 1. What are the different levels of Oracle Java certification exams?
- •FAQ 4. Is OCPJP 7 prerequisite for other Oracle certification exams?
- •FAQ 5. Should I take the OCPJP 7 or OCPJP 6 exam?
- •The OCPJP 7 Exam
- •FAQ 7. How many questions are there in the OCPJP 7 exam?
- •FAQ 8. What is the duration of the OCPJP 7 exam?
- •FAQ 9. What is the cost of the OCPJP 7 exam?
- •FAQ 10. What are the passing scores for the OCPJP 7 exam?
- •FAQ 11. What kinds of questions are asked in the OCPJP 7 exam?
- •FAQ 12. What does the OCPJP 7 exam test for?
- •FAQ 13. I’ve been a Java programmer for last five years. Do I have to prepare for the OCPJP 7 exam?
- •FAQ 14. How do I prepare for the OCPJP 7 exam?
- •FAQ 15. How do I know when I’m ready to take the OCPJP 7 exam?
- •Taking the OCPJP 7 Exam
- •FAQ 16. What are my options to register for the exam?
- •FAQ 17. How do I register for the exam, schedule a day and time for taking the exam, and appear for the exam?
- •The OCPJP 7 Exam: Pretest
- •Answers with Explanations
- •Post-Pretest Evaluation
- •Essentials of OOP
- •FunPaint Application: An Example
- •Foundations of OOP
- •Abstraction
- •Encapsulation
- •Inheritance
- •Polymorphism
- •Class Fundamentals
- •Object Creation
- •Constructors
- •Access Modifiers
- •Public Access Modifier
- •Private Access Modifier
- •Protected and Default Access Modifier
- •Overloading
- •Method Overloading
- •Constructor Overloading
- •Overload resolution
- •Points to Remember
- •Inheritance
- •Runtime Polymorphism
- •An Example
- •Overriding Issues
- •Overriding: Deeper Dive
- •Invoking Superclass Methods
- •Type Conversions
- •Upcasts and Downcasts
- •Casting Between Inconvertible Types
- •Using “instanceof” for Safe Downcasts
- •Java Packages
- •Working with Packages
- •Static Import
- •Summary
- •Abstract Classes
- •Points to Remember
- •Using the “final” Keyword
- •Final Classes
- •Final Methods and Variables
- •Points to Remember
- •Using the “static” Keyword
- •Static Block
- •Points to Remember
- •Flavors of Nested Classes
- •Static Nested Classes (or Interfaces)
- •Points to Remember
- •Inner Classes
- •Points to Remember
- •Local Inner Classes
- •Points to Remember
- •Anonymous Inner Classes
- •Points to Remember
- •Enum Data Types
- •Points to Remember
- •Summary
- •Interfaces
- •Declaring and Using Interfaces
- •Points to Remember
- •Abstract Classes vs. Interfaces
- •Choosing Between an Abstract Class and an Interface
- •Object Composition
- •Composition vs. Inheritance
- •Points to Remember
- •Design Patterns
- •The Singleton Design Pattern
- •Ensuring That Your Singleton Is Indeed a Singleton
- •The Factory Design Pattern
- •Differences Between Factory and Abstract Factory Design Patterns
- •The Data Access Object (DAO) Design Pattern
- •Points to Remember
- •Summary
- •Generics
- •Using Object Type and Type Safety
- •Using the Object Class vs. Generics
- •Container Implementation Using the Object Class
- •Container Implementation Using Generics
- •Creating Generic Classes
- •Diamond Syntax
- •Interoperability of Raw Types and Generic Types
- •Generic Methods
- •Generics and Subtyping
- •Wildcard Parameters
- •Limitations of Wildcards
- •Bounded Wildcards
- •Wildcards in the Collections Class
- •Points to Remember
- •The Collections Framework
- •Why Reusable Classes?
- •Basic Components of the Collections Framework
- •Abstract Classes and Interfaces
- •Concrete Classes
- •List Classes
- •ArrayList Class
- •The ListIterator Interface
- •The LinkedList Class
- •The Set Interface
- •The HashSet Class
- •The TreeSet Class
- •The Map Interface
- •The HashMap Class
- •Overriding the hashCode() Method
- •The NavigableMap Interface
- •The Queue Interface
- •The Deque Interface
- •Comparable and Comparator Interfaces
- •Algorithms (Collections Class)
- •The Arrays Class
- •Methods in the Arrays Class
- •Array as a List
- •Points to Remember
- •Summary
- •Generics
- •Collections Framework
- •Processing Strings
- •String Searching
- •The IndexOf() Method
- •The regionMatches() Method
- •String Parsing
- •String Conversions
- •The Split() Method
- •Regular Expressions
- •Understanding regex Symbols
- •Regex Support in Java
- •Searching and Parsing with regex
- •Replacing Strings with regex
- •String Formatting
- •Format Specifiers
- •Points to Remember
- •Summary
- •Reading and Writing from Console
- •Understanding the Console Class
- •Formatted I/O with the Console Class
- •Special Character Handling in the Console Class
- •Using Streams to Read and Write Files
- •Character Streams and Byte Streams
- •Character Streams
- •Reading Text Files
- •Reading and Writing Text Files
- •“Tokenizing” Text
- •Byte Streams
- •Reading a Byte Stream
- •Data Streams
- •Writing to and Reading from Object Streams: Serialization
- •Serialization: Some More Details
- •Points to Remember
- •Summary
- •A Quick History of I/O APIs
- •Using the Path Interface
- •Getting Path Information
- •Comparing Two Paths
- •Using the Files Class
- •Checking File Properties and Metadata
- •Copying a File
- •Moving a File
- •Deleting a File
- •Walking a File Tree
- •Revisiting File Copy
- •Finding a File
- •Watching a Directory for Changes
- •Points to Remember
- •Summary
- •Introduction to JDBC
- •The Architecture of JDBC
- •Two-Tier and Three-Tier JDBC Architecture
- •Types of JDBC Drivers
- •Setting Up the Database
- •Connecting to a Database Using a JDBC Driver
- •The Connection Interface
- •Connecting to the Database
- •Statement
- •ResultSet
- •Querying the Database
- •Updating the Database
- •Getting the Database Metadata
- •Points to Remember
- •Querying and Updating the Database
- •Performing Transactions
- •Rolling Back Database Operations
- •The RowSet Interface
- •Points to Remember
- •Summary
- •Define the Layout of the JDBC API
- •Connect to a Database by Using a JDBC driver
- •Update and Query a Database
- •Customize the Transaction Behavior of JDBC and Commit Transactions
- •Use the JDBC 4.1 RowSetProvider, RowSetFactory, and RowSet Interfaces
- •Introduction to Exception Handling
- •Throwing Exceptions
- •Unhandled Exceptions
- •Try and Catch Statements
- •Programmatically Accessing the Stack Trace
- •Multiple Catch Blocks
- •Multi-Catch Blocks
- •General Catch Handlers
- •Finally Blocks
- •Points to Remember
- •Try-with-Resources
- •Closing Multiple Resources
- •Points to Remember
- •Exception Types
- •The Exception Class
- •The RuntimeException Class
- •The Error Class
- •The Throws Clause
- •Method Overriding and the Throws Clause
- •Points to Remember
- •Custom Exceptions
- •Assertions
- •Assert Statement
- •How Not to Use Asserts
- •Summary
- •Introduction
- •Locales
- •The Locale Class
- •Getting Locale Details
- •Resource Bundles
- •Using PropertyResourceBundle
- •Using ListResourceBundle
- •Loading a Resource Bundle
- •Naming Convention for Resource Bundles
- •Formatting for Local Culture
- •The NumberFormat Class
- •The Currency Class
- •The DateFormat Class
- •The SimpleDateFormat Class
- •Points to Remember
- •Summary
- •Introduction to Concurrent Programming
- •Important Threading-Related Methods
- •Creating Threads
- •Extending the Thread Class
- •Implementing the Runnable Interface
- •The Start( ) and Run( ) Methods
- •Thread Name, Priority, and Group
- •Using the Thread.sleep() Method
- •Using Thread’s Join Method
- •Asynchronous Execution
- •The States of a Thread
- •Two States in “Runnable” State
- •Concurrent Access Problems
- •Data Races
- •Thread Synchronization
- •Synchronized Blocks
- •Synchronized Methods
- •Synchronized Blocks vs. Synchronized Methods
- •Deadlocks
- •Other Threading Problems
- •Livelocks
- •Lock Starvation
- •The Wait/Notify Mechanism
- •Let’s Solve a Problem
- •More Thread States
- •timed_waiting and blocked States
- •waiting State
- •Using Thread.State enum
- •Understanding IllegalThreadStateException
- •Summary
- •Using java.util.concurrent Collections
- •Semaphore
- •CountDownLatch
- •Exchanger
- •CyclicBarrier
- •Phaser
- •Concurrent Collections
- •Apply Atomic Variables and Locks
- •Atomic Variables
- •Locks
- •Conditions
- •Multiple Conditions on a Lock
- •Use Executors and ThreadPools
- •Executor
- •Callable, Executors, ExecutorService, ThreadPool, and Future
- •ThreadFactory
- •The ThreadLocalRandom Class
- •TimeUnit Enumeration
- •Use the Parallel Fork/Join Framework
- •Useful Classes of the Fork/Join Framework
- •Using the Fork/Join Framework
- •Points to Remember
- •Summary
- •Using java.util.concurrent Collections
- •Applying Atomic Variables and Locks
- •Using Executors and ThreadPools
- •Using the Parallel Fork/Join Framework
- •Chapter 3: Java Class Design
- •Chapter 4: Advanced Class Design
- •Chapter 5: Object-Oriented Design Principles
- •Chapter 6: Generics and Collections
- •Chapter 7: String Processing
- •Chapter 8: Java I/O Fundamentals
- •Chapter 9: Java File I/O (NIO.2)
- •Chapter 10: Building Database Applications with JDBC
- •Chapter 11: Exceptions and Assertions
- •Chapter 12: Localization
- •Chapter 13: Threads
- •Chapter 14: Concurrency
- •OCPJP7 Exam (1Z0-804 a.k.a. Java SE 7 Programmer II) Topics
- •OCPJP 7 Exam (1Z0-805, a.k.a. Upgrade to Java SE 7 Programmer) Topics
- •Answers and Explanations
- •Answer Sheet
- •Answers and Explanations
- •Index
Chapter 14 ■ ConCurrenCy
public void run() { try {
// wait for the timer count down to reach 0 timer.await();
} catch (InterruptedException ie) {
System.err.println("interrupted -- can't start running the race");
}
System.out.println(this.getName() + " started running");
}
}
This program prints the following:
Carl ready and waiting for the count down to start Joe ready and waiting for the count down to start Jack ready and waiting for the count down to start Starting the countdown
5
4
3
2
1 Start
Joe started running Carl started running Jack started running
Let’s consider how the program works. The class Runner simulates a runner in a running race waiting to start running. It waits for the race to start by calling the await() method on the CountDownLatch object passed through the constructor.
The RunningRaceStarter class creates a CountDownLatch object. This counter object is initialized with the count value 5, which means the countdown is from 5 to 0. In the main() method, you create Runner objects; these three threads wait on the counter object. For each second, you call the countDown() method, which decrements count by 1. Once the count reaches zero, all three waiting threads are released and they automatically continue execution.
Note: In this program, the sequence in which Joe, Carl, or Jack is printed cannot be predicted since it depends on thread scheduling. So, if you run this program, you may get these three names printed in some other order.
Exchanger
The Exchanger class is meant for exchanging data between two threads. What Exchanger does is something very simple: it waits until both the threads have called the exchange() method. When both threads have called the exchange() method, the Exchanger object actually exchanges the data shared by the threads with each other. This class is useful when two threads need to synchronize between them and continuously exchange data.
This class is a tiny class with only one method: exchange(). Note that this exchange() method has an overloaded form where it takes a time-out period as an argument.
Listing 14-3 shows an example simulating silly talk between the Java Duke mascot and the coffee shop. The two threads DukeThread and CoffeeShop threads run independently. However, for a chat to happen, they need to listen when the other is talking. An Exchange object provides a means for them to talk to each other.
440
Chapter 14 ■ Concurrency
Listing 14-3. KnockKnock.java
import java.util.concurrent.Exchanger;
//The DukeThread class runs as an independent thread. It talks to the CoffeeShopThread that
//also runs independently. The chat is achieved by exchanging messages through a common
//Exchanger<String> object that synchronizes the chat between them.
//Note that the message printed are the "responses" received from CoffeeShopThread
class DukeThread extends Thread {
private Exchanger<String> sillyTalk;
public DukeThread(Exchanger<String> args) { sillyTalk = args;
}
public void run() {
String reply = null; try {
//start the conversation with CoffeeShopThread reply = sillyTalk.exchange("Knock knock!");
//Now, print the response received from CoffeeShopThread System.out.println("CoffeeShop: " + reply);
//exchange another set of messages reply = sillyTalk.exchange("Duke");
//Now, print the response received from CoffeeShopThread System.out.println("CoffeeShop: " + reply);
//an exchange could happen only when both send and receive happens
//since this is the last sentence to speak, we close the chat by
//ignoring the "dummy" reply
reply = sillyTalk.exchange("The one who was born in this coffee shop!");
//talk over, so ignore the reply!
}catch(InterruptedException ie) {
System.err.println("Got interrupted during my silly talk");
}
}
}
class CoffeeShopThread extends Thread { private Exchanger<String> sillyTalk;
public CoffeeShopThread(Exchanger<String> args) { sillyTalk = args;
}
public void run() {
String reply = null; try {
// exchange the first messages
reply = sillyTalk.exchange("Who's there?"); // print what Duke said System.out.println("Duke: " + reply);
441
Chapter 14 ■ Concurrency
// exchange second message
reply = sillyTalk.exchange("Duke who?"); // print what Duke said System.out.println("Duke: " + reply);
//there is no message to send, but to get a message from Duke thread,
//both ends should send a message; so send a "dummy" string
reply = sillyTalk.exchange(""); System.out.println("Duke: " + reply);
} catch(InterruptedException ie) {
System.err.println("Got interrupted during my silly talk");
}
}
}
//Coordinate the silly talk between Duke and CoffeeShop by instantitaing the Exchanger object
//and the CoffeeShop and Duke threads
class KnockKnock {
public static void main(String []args) {
Exchanger<String> sillyTalk = new Exchanger<String>(); new CoffeeShopThread(sillyTalk).start();
new DukeThread(sillyTalk).start();
}
}
The program prints the following:
Duke: Knock knock! CoffeeShop: Who's there? Duke: Duke
CoffeeShop: Duke who?
Duke: The one who was born in this coffee shop!
The comments inside the program explain how the program works. The main concept to understand with this example is that Exchanger helps coordinate (i.e., synchronize) exchanging messages between two threads. Both the threads wait for each other and use the exchange() method to exchange messages.
CyclicBarrier
There are many situations in concurrent programming where threads may need to wait at a predefined execution point until all other threads reach that point. CyclicBarrier helps provide such a synchronization point; see Table 14-3 for the important methods in this class.
442
|
Chapter 14 ■ Concurrency |
Table 14-3. Important Methods in the CyclicBarrier Class |
|
|
|
Method |
Description |
CyclicBarrier(int numThreads) |
Creates a CyclicBarrier object with the number of threads waiting |
|
on it specified. Throws IllegalArgumentException if numThreads is |
|
negative or zero. |
CyclicBarrier(int parties, |
Same as the previous constructor; this constructor additionally takes |
Runnable barrierAction) |
the thread to call when the barrier is reached. |
int await() |
Blocks until the specified number of threads have called await() |
int await(long timeout, |
on this barrier. The method returns the arrival index of this |
TimeUnit unit) |
thread. This method can throw an InterruptedException if |
|
the thread is interrupted while waiting for other threads or a |
|
BrokenBarrierException if the barrier was broken for some reason |
|
(for example, another thread was timed-out or interrupted). The |
|
overloaded method takes a time-out period as an additional option; |
|
this overloaded version throws a TimeoutException if all other |
|
threads aren’t reached within the time-out period. |
boolean isBroken() |
Returns true if the barrier is broken. A barrier is broken if at least one |
|
thread in that barrier was interrupted or timed-out, or if a barrier |
|
action failed throwing an exception. |
void reset() |
Resets the barrier to the initial state. If there are any threads waiting |
|
on that barrier, they will throw the BrokenBarrier exception. |
|
|
Listing 14-4 is an example that makes use of CyclicBarrier class.
Listing 14-4. CyclicBarrierTest.java
import java.util.concurrent.*;
//The run() method in this thread should be called only when four players are ready to start the game class MixedDoubleTennisGame extends Thread {
public void run() {
System.out.println("All four players ready, game starts \n Love all...");
}
}
//This thread simulates arrival of a player.
//Once a player arrives, he/she should wait for other players to arrive
class Player extends Thread { CyclicBarrier waitPoint;
public Player(CyclicBarrier barrier, String name) { this.setName(name);
waitPoint = barrier; this.start();
}
public void run() {
System.out.println("Player " + getName() + " is ready ");
443