JavaBlog.fr / Java.lu DEVELOPMENT,Java Java: Queue implementation ConcurrentLinkedQueue (Part4)

Java: Queue implementation ConcurrentLinkedQueue (Part4)

After my post concerning presentation of Queue/BlockingQueue, I would continue with a post about the Queue implementation: java.util.concurrent.ConcurrentLinkedQueue.

This implementation of Queue (NOT BlockingQueue) is thread-safe queue which stores and keeps the elements internally in an unbounded queue based on linked nodes and in FIFO (First In, First Out) order. A ConcurrentLinkedQueue is an appropriate choice when many threads will share access to a common collection. This queue does not permit null elements.

We will illustrate our writing by the example of pool/queue containing ‘no thread-safe’ business objects MyNoTheadSafeTask which will be accessed by a series of consumer/producer threads: each thread takes an instance from queue, calls an action on this instance and release (put) it again in the queue.

In our example, this business object is a simple POJO, however, this POJO could be a ‘no thread-safe’ bean Spring with the scope “prototype”:

<bean id="fileBean" class="com.ho.utils.businessobject.MyNoTheadSafeTask" scope="prototype">
        <property name="property1" value="value1" />
</bean>

So, our business object :

  • has the attribut name instanceName and random sleep time between 0 and 5 seconds:
  • private int sleepTime; // random sleep time for instance   
    private String instanceName; // name of instance   
    private static Random generator = new Random();
    	
    public MyNoTheadSafeTask(String name){
    	// set name of instance
    	this.instanceName = name;
    	// random sleep time between 0 and 5 seconds
    	this.sleepTime = generator.nextInt( 5000 ); 
    }
    
  • provides a method action corresponding to a System.out output and a random sleep time:
  • public boolean action(String paramValue1, int paramValue2) throws Throwable{
    	try{ 
    		// put instance to sleep for sleepTime amount of time
    		System.out.printf("--> '%s' starting 'action' and going to sleep for %d milliseconds.\n", this.instanceName, this.sleepTime);
    		// put instance to sleep
    		Thread.sleep( this.sleepTime );   
    	} catch ( InterruptedException exception )  {  
    		exception.printStackTrace(); 
    	}
    	return true;
    }
    

Then, the MySingletonDelegate singleton:

  • contains the pool/queue component ConcurrentLinkedQueue:
  • private ConcurrentLinkedQueue <MyNoTheadSafeTask> noTheadSafeTaskQueue = new ConcurrentLinkedQueue<MyNoTheadSafeTask>();
    
  • create several instances of “NoTheadSafeTask” in this pool component:
  • private MySingletonDelegate() {
    	for (int i=0; i < 5; i++) {
    		String instanceName = "instanceName_"+i;
    		System.out.println("NoTheadSafeTask.createInstance("+instanceName+");");
    		MyNoTheadSafeTask noTheadSafeTask = new MyNoTheadSafeTask(instanceName);
    		noTheadSafeTaskQueue.add(noTheadSafeTask);
    	} // end-if
    }
    
  • provides a private method ‘getNoTheadSafeTaskFromPool’ to take an instance of “NoTheadSafeTask” in queue/pool. This method needn’t be synchronized because the pool ConcurrentLinkedQueue is a thread-safe queue.
  • private MyNoTheadSafeTask getNoTheadSafeTaskFromPool() {
    	try {
    		MyNoTheadSafeTask noTheadSafeTask = noTheadSafeTaskQueue.poll();
    		System.out.printf("--> '%s' instance has been taken from the queue (new size: %d) \n", noTheadSafeTask.getInstanceName(), noTheadSafeTaskQueue.size());
    		return noTheadSafeTask;
    	} catch (Throwable e) {
    		System.out.println("getNoTheadSafeTaskFromPool : an InterruptedException occured:"+e.getMessage());
    	} // end-try
    	return null;
    }
    
  • provides a private method ‘releaseNoTheadSafeTaskToPool’ to release an instance of “NoTheadSafeTask” in queue/pool:
  • private final void releaseNoTheadSafeTaskToPool(MyNoTheadSafeTask noTheadSafeTask) {
    	try {
    		noTheadSafeTaskQueue.add(noTheadSafeTask);
    		System.out.printf("--> '%s' instance has been released from the queue (new size: %d) \n", noTheadSafeTask.getInstanceName(), noTheadSafeTaskQueue.size());
    	} catch (Throwable e) {
    		System.out.println("releaseNoTheadSafeTaskToPool : an InterruptedException occured:"+e.getMessage());
    	} // end-try
    }
    
  • provides a public method ‘completeAction’ allowing a complete action with the retrieve of a instance of “NoTheadSafeTask” from the pool, the execution of action on this retrieved instance and the release of this retrieved instance of “NoTheadSafeTask” to the pool:
  • public boolean completeAction(String paramValue1, int paramValue2) throws Throwable {
    	MyNoTheadSafeTask noTheadSafeTask = getNoTheadSafeTaskFromPool();
    	try {
    		return noTheadSafeTask.action(paramValue1, paramValue2);
    	} finally {
    		releaseNoTheadSafeTaskToPool(noTheadSafeTask);
    	}
    }
    

At last, the main method which will:
– create the singleton MySingletonDelegate which will create QUEUE,
– create 5 threads which will each call the business method completeAction provided by the above singleton MySingletonDelegate,
– execute these 5 threads due to an ExecutorService;

public static void main(String[] args) {
		
	try {
		// create singleton which will create QUEUE
		MySingletonDelegate.getInstance();
			
		// Client classes of the  ClientDelegate
		ExecutorService es = Executors.newFixedThreadPool(5);
		//
		for (int i=0; i < 5; i++) {
				
			//Thread
			es.submit(new Runnable() { 
				public void run() { 
					try {
						MySingletonDelegate.getInstance().completeAction(null, 1);
					} catch (Throwable e) {
						e.printStackTrace();
					}
				} 
			});

			// Wait 1s between the threads' launching
			Thread.sleep( 1000 );   
				
		} // end-for
			
		es.shutdown(); 

	} catch (Throwable e) {
		e.printStackTrace();
	}
}

… and the outputs would be:

NoTheadSafeTask.createInstance(instanceName_0);
NoTheadSafeTask.createInstance(instanceName_1);
NoTheadSafeTask.createInstance(instanceName_2);
NoTheadSafeTask.createInstance(instanceName_3);
NoTheadSafeTask.createInstance(instanceName_4);
--> 'instanceName_0' instance has been taken from the queue (new size: 4) 
--> 'instanceName_0' starting 'action' and going to sleep for 4531 milliseconds.
--> 'instanceName_1' instance has been taken from the queue (new size: 3) 
--> 'instanceName_1' starting 'action' and going to sleep for 3548 milliseconds.
--> 'instanceName_2' instance has been taken from the queue (new size: 2) 
--> 'instanceName_2' starting 'action' and going to sleep for 3968 milliseconds.
--> 'instanceName_3' instance has been taken from the queue (new size: 1) 
--> 'instanceName_3' starting 'action' and going to sleep for 4853 milliseconds.
--> 'instanceName_4' instance has been taken from the queue (new size: 0) 
--> 'instanceName_4' starting 'action' and going to sleep for 1787 milliseconds.
--> 'instanceName_1' instance has been released from the queue (new size: 1) 
--> 'instanceName_0' instance has been released from the queue (new size: 2) 
--> 'instanceName_4' instance has been released from the queue (new size: 3) 
--> 'instanceName_2' instance has been released from the queue (new size: 4) 
--> 'instanceName_3' instance has been released from the queue (new size: 5) 

Conclusion
In this example, we could analyze that the FIFO order is kept because the instances taken by the consumer threads are in the same order than the adding’s order in the queue/pool.

NoTheadSafeTask.createInstance(instanceName_0);
NoTheadSafeTask.createInstance(instanceName_1);
NoTheadSafeTask.createInstance(instanceName_2);
NoTheadSafeTask.createInstance(instanceName_3);
NoTheadSafeTask.createInstance(instanceName_4);
...
--> 'instanceName_0' instance has been taken from the queue (new size: 4) 
--> 'instanceName_1' instance has been taken from the queue (new size: 3) 
--> 'instanceName_2' instance has been taken from the queue (new size: 2) 
--> 'instanceName_3' instance has been taken from the queue (new size: 1) 
--> 'instanceName_4' instance has been taken from the queue (new size: 0) 

The source code of this article and the a test cases are in the ZIP file attachement.

Download: java_queue.zip

Best regards,

Leave a Reply

Your email address will not be published.

Time limit is exhausted. Please reload CAPTCHA.

Related Post

Backup your projectsBackup your projects

Hello again, Here, I expose a simple solution to backup your developments in the remote directory \\YOUR_SERVER_or_EXTERNALDISK\backupWorkspaces\. To do this: – Create file “backup.dat” in your Eclipse workspace ie “R:\java\dev\eclipse_workspaces\default-3.3”: –

Documentum : Audit trail entries dm_audittrail / SessionConfig / application_codeDocumentum : Audit trail entries dm_audittrail / SessionConfig / application_code

Hi, After my previous posts concerning the Documentum audit trail entries (dm_audittrail) http://www.javablog.fr/documentum-creation-of-audit-trail-entries-dm_audittrail.html and http://www.javablog.fr/deleting-of-audit-trail-entries-dm_audittrail.html, here, I would like to expose a solution in order to force content server to