Application Module holds the DB Connection till we commit?

Question

Hi All,
Jdeveloper :- 11.1.1.5
As in my business scenario ,i have an EO and VO and there AM.In VO we have a bind variable which is nothing but the task Id.On Page Load i pass the bind variable to the VO and fetch the data onto the page.As user update the data onto the page and then when he press submit, we actually calls the stored procedure which finally updates the data in the table for the same task id.
But the problem is , when i am fetching the data from the table using AM,it actually creates a connection with the database but it doesn't release the connection.
Is there any way where we fetch the data from the table using AM and then close or release the connection so that while submitting tha data to the table using stored proc will not get the locked row.
Please suggest!!!

Answer 1

Have you set up the application module to use optimistic locking?
This mode should hole the lock only during update of the row.
I don't think the problem is tied to the connection pool. An application module holds on to the jdbc connection until it gets released from the application module pool. This only happens is a application module is not used for a configurable idle time (one of the pooling parameters). If you app releases an application module the module is put back into the application module pool for resuse and holds the connection.
Timo