Skip to main content

Java Object - wait - notify - a practical example

Object is the super class of anything in Java. But, Most people fear the wait and notify methods in Object. The common java practitioner might not need to use these for all practical purposes. However, the fear is not because they are hard to understand, but because of the assumption and false notion (generally pushed from the *experts* to the newbies) that these are for *super users*. The easiest way to understand this is by example. Most examples include Produce Consumer, But in practice where is this applied?

Some time back I wrote about Commons Pooling. Ever wonder how an Object pool Implemention, like this one, would time out on a blocking call without creating a new thread on its own? It uses a wait - notify[All] paradigm.

To understand that Look at the source code of the said GenericObjectPool.

The borrowObject method (line 911 - so apt??) which optionally waits for a maxWait long secs, is used like
for (;;) {
 synchronized (this) {
  // Some Logic
  try {
   if (_maxWait <= 0) {
    wait();
   } else {
    final long elapsed = (System.currentTimeMillis() - starttime);
    final long waitTime = _maxWait - elapsed;
    if (waitTime > 0) {
     wait(waitTime);
    }
   }
  } catch (InterruptedException e) {
   Thread.currentThread().interrupt();
   throw e;
  }
  if (_maxWait > 0
    && ((System.currentTimeMillis() - starttime) >= _maxWait)) {
   throw new NoSuchElementException(
     "Timeout waiting for idle object");
  } else {
   continue; // keep looping
  }

 }
}

And the addObjectToPool method does the notify
if (decrementNumActive) { //Some condition
       synchronized(this) { //Sync the same object
           _numActive--;
           notifyAll(); // wakeup all threads waiting on *this*
       }
   }

So one method will call wait, (optionally with a with a wait time) and the other will notify. Note that it is the same object used (*this*). Here the producer is the addObjectToPool method and consumer is the borrowObject. Generally wait(*no time out*) is in a loop, wait with time out is a single flow. Both these are demostrated by the above example.

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...

Faster webpages with fewer CSS and JS

Its easy, have lesser images, css and js files. I will cover reducing number of images in another post. But If you are like me, You always write js and css in a modular fashion. Grouping functions and classes into smaller files (and Following the DRY rule, Strictly!). But what happens is, when you start writing a page to have these css and js files, you are putting them in muliple link rel=style-sheet or script tags. Your server is being hit by (same) number of HTTP Requests for each page call. At this point, its not the size of files but the number server roundtrips on a page that slows your page down. Yslow shows how many server roundtrips happen for css and js. If you have more than one css call and one js call, You are not using your server well. How do you achieve this? By concatinating them and spitting out the content as one stream. So Lets say I have util.js, blog.js and so.js. If I have a blog template that depends on these three, I would call them in three script tags. Wh...