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) {
   } else {
    final long elapsed = (System.currentTimeMillis() - starttime);
    final long waitTime = _maxWait - elapsed;
    if (waitTime > 0) {
  } catch (InterruptedException e) {
   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
           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

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>