surabhi.ahuja wrote:
> Is the above peice of code fine, does the problem lie in the code which
> calls the executeQuery of QueryExecutor?
Really, this sounds like a threading problem in your code that you need
to solve yourself.
If you can show a testcase showing the driver doing something wrong ..
or a thread dump where a thread is stuck in the driver .. now that is
more interesting.
Otherwise it is just-another-threading-problem; I looked at your code
briefly but it is not particularly clear what its behaviour is meant to
be (i.e. it has "no obvious bugs" rather than "obviously no bugs" ;-)
-O