JVM is hang and throughing HTTP 500 Error [Locking]

My java class is going to call store procedure. In side store procedure there is one table.

Situation is like that EOD runing time my applicaion is going to use the same table ..

then my application is hanged till EOD completion...

and same time i sended some other requests some of them processed but some of them going hang

what is happening inside the application

Situation is like that EOD runing time my applicaion is going to use the same table ..

Can you elaborate this a little more?

what is happening inside the application

You may need to provide more helpful details (TellTheDetails).

Do you have any kind of logging set up for this?

Vijitha ,

Steps like this

1) I am using Oracle 10g Application server
2) My application have 4jvm and using with connection pooling.(Each JVM min 10 to 30 Conn)
3) I am inserting data into table, but that table using some other[was already inserting other] activity(EOD)

4) So My application is going to use that table then my connection gone for waing stage.[if example my application using 1 JVM, One connection]

5) So that my applications remaing 3 JVMs is serving some other requests.

6) after 3 JVMs connection are full busy then my request goes to 1'st JVM right.
7) Here i am getting HTTP 500 Error then no response (that mean this also going hang.)

8) I am not understanding why JVM Going to hang that stage,
9) In my case after 1i/2 hour that connection was released [that EOD is completed].
10) If that table is busy why connection was broken after 5 or 10 min.
11) Why JVM using all the connection for that single request

Looks like a database related problem. Off to JDBC we go!

And my #1 guess - the EOD is locking the entire table, which causes the stored procedures to wait until that lock is released. The client code has set a timeout that causes the abort before the lock is released and the stored procedure is finished.

I am not understand am using connection pooling,have min 10 connections
if connection is going for lock why remaing connections also behavior as hang bode. and throughing HTTP 500 in appache server.
If table isusing some other resource, why it was waited that much time. why my connection broken after 1 and half hour released and thorughing exception as l connection closed.
why it was not timeout..

RaghavaRao oura wrote:...if connection is going for lock why remaing connections also behavior as hang bode...

If the table is locked no other connection is able to access it no matter how many connections you have in the pool.

Yes , I am using connection pool, each JVM having 10 to 30 connections with 4 JVMs, I have checked the sessions at the situation also.