On 3/7/06, Byrne, Ailish M <[EMAIL PROTECTED]> wrote:
> This issue was related to the fact that we are using XAPool. Here is
> the explanation from the experts. I've cc'd them in case you have any
> questions. They patched our OJB 1.0.4 jar as a temporary solution.
>
> _________________________________________________
>
> The problem here is the unwrapStatement method in the
> PlatformOracle9iImpl. Basically what this method is trying to do is
> unwrap the actual OraclePreparedStatement from the connections Statement
> (which will be different depending on the pooling technology). Here is
> the configuration of how it searches (found in the PlatformOracle9iImpl
> class):
>
> /** Method names used by [EMAIL PROTECTED] #unwrapStatement}. */
> protected static final String UNWRAP_PS_METHOD_NAMES[] =
> {
> "getInnermostDelegate" /* Commons DBCP */,
> "getUnderlyingStatement" /* JBoss */,
> "getJDBC" /* P6Spy */
> };
>
> As you can see, XAPool (which is the connection pooling used by workflow
> for JTA purposes) is not represented in this list. Therefore, it can't
> unwrap the statement and ends up deferring to the PlatformOracleImpl.
>
> We'll take a look into the best method for fixing this tomorrow but
> preliminary examination makes me think we may need to patch the ojb jar
> or subclass the PlatformOracle9iImpl and add support for XAPool.
It would be nice if you could add an enhancement issue in JIRA for
this with the changes attached, so that other can benefit from your
findings.
cheers,
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
