Re: "java.sql.SQLException: Result set already

Andy Bowes wrote:

> Hi Joe
> 
> Sorry for the delay, I have been doing some further investigation.
> 
> I have simplified our TestCase to ensure that we are only running a single
thread in our external client but I am still getting the same error.
> 
> The exception only occurs if I perform the query within an XA Transaction
which is being handled by the Weblogic Transaction Manager.  I can perform the
query outside the XA Transaction and it will retreive all of the information
without closing the Result Sets.
> 
> It appears that the ResultSet is being closed by the WebLogic Transaction
Manager even though the encompassing XA Transaction has not been ended by the
external client.


Set the keep-xa-connection-till-tx-complete to true for the pool.
If that doesn't fix it, open an official support case. I bet that
if the tx code is run in a JSP (all in one invoke) it'll be faster