db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepa Remesh <drem...@gmail.com>
Subject Re: [jira] Commented: (DERBY-498) Result set holdability defined inside stored procedures is ignored by server/client
Date Thu, 20 Oct 2005 21:22:33 GMT
On 10/20/05, Kathey Marsden <kmarsdenderby@sbcglobal.net> wrote:
> Deepa Remesh (JIRA) wrote:
> >
> >
> >I merged this patch to my 10.1 codeline and ran derbyall with Sun jdk 1.4.2 on Windows
XP. 2 tests failed. Failures are not related to this change.
> >
> >
> >
> I applied the merge command for   10.1 and ran  lang/holdCursorJava.java
> and see this exception at the bottom of the output for both derbynet and
> derbynetclient frameworks.    The output up to that point is ok.  Does
> this look familar at all?

The test lang/holdCursorJava.java is in jdk14 suite and so it does not
get run with derbynet and client in 10.1. To run this test, DERBY-593
will have to be merged to 10.1.

In DERBY-593, I had added jdk14 suite to network server tests. For
holdCursorJava.java, I had to add a rollback before calling close on
the connection. Otherwise, I was getting the same exception you are
seeing now. Looking at this again, I think it could be a possible bug
in client side that it leaves some open resources after setting
transaction isolation level. This is independent of this patch. I'll
look at this some more.

I will send the merge for DERBY-593.


View raw message