This content has been marked as final. Show 1 reply
In an oracle session (when tomcat establishes connection with oracle) if an existing procedure is compiled which is being used by java currently, for the next run u will be getting the error (session persistence), and in the same session if u try to re-execute (i mean if u call [CALLABLE STMT] the procedure again) the error will not come.
This is not the issue with connection pool, its default behavior of oracle. So, the CALLABLE STMT can be re-executed when exception occurs, that would resolve the issue.