Subject Re: XA driver pooling issue
Author Ludovic Orban

The advanced option "Test Reserved Connections" with "Test Table Name"
equals to "SQL select 1 from rdb$database" seems to be causing the NPE.

It happens when my code gets an XAConnection from the XADataSource or
when WLS tries to get a connection to recover a failed XA transaction
short after server's startup.

I tried creating a connection pool + datasource with the
org.firebirdsql.jdbc.FBDriver class and tried getting a Connection
from DataSource but this error does not happen it this case.

I Hope that helps.


--- In, "Roman Rokytskyy"
<rrokytskyy@a...> wrote:
> > java version "1.4.2_08"
> > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
> > Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
> Ok, I will check which one was picked by WLS in my case.
> > It's pretty weird that you cannot reproduce it. I checked for some
> > subtle difference somewhere and I think I found the cause of the
> >
> > Under Connection Pool > Connections > Show Advanced Options there is
> > an option called "Remove Infected Connections Enabled" that I checked
> > by mistake. When unchecked, everything works fine again.
> Ok, I did not touch advanced options.
> > Not sure why such an option exists. It seems to force physical
> > connection to close when the pooled connection is closed.
> Ok, I will check this option. Having an NPE in our code is not good
> anyway.
> Roman