When I start commitment control in stored procedure it says commitment control is already active. Whereas I have disabled autocommit and transaction isolation from Java end.
I am looking for a solution to make commitment control work inside stored procedure.
Sorry, I don't know how to start a transaction inside your stored procedure.
If you want a transaction inside your stored procedure, then turning off commitment control isn't the way to do that. Commitment control is simply the background process which manages transactions. So don't turn it off. (And don't turn it on, either, it should already be on for files which you are updating with that driver.)
This means we can not turn off the autoCommit inside stored procedure.
Is this restriction is for stored procedure only ?