> Actually I am giving the thread dump of driver,
>
> while doing an executeUpdate the following trace locks up some
> statement
> ...
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(Unknown Source)
> ...
>
> For this statement other thread waits, but the above threads doesn't
> return and stays there itself.
> ...
> Is there anything like we have to with the DB handle or something
> like that, or how we can we solve this problem

If the first thread is blocked forever in socket read, then this is a
bug in the wire protocol implementation in the driver and I would like
to have a reproducable test case.

If it is blocked only because query/update execution takes a lot of
time, there's nothing you can do about it. Server will not accept any
other statement until this one is finished.

If you need to execute some statement, while another is running, you
need to use another connection.

Can you provide some code that reproduces your problem?

Thanks!
Roman