Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <33012204.1186153493201.JavaMail.jira@brutus>
Date: Fri, 3 Aug 2007 08:04:53 -0700 (PDT)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Issue Comment Edited: (DERBY-2892) Closing a resultset after
 retrieving a large > 32665 bytes value with Network Server does not release
 locks
In-Reply-To: <28283072.1183475946233.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DERBY-2892?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517553 ]=20

Kathey Marsden edited comment on DERBY-2892 at 8/3/07 8:03 AM:
---------------------------------------------------------------

V. Narayanan said
>Features of locator are not present for the ResultSet
>and the PreparedStatement methods.=20

I am a little confused by this. Are you saying that a ResultSet.getBinarySt=
ream() on the client should not be translating into a getBlob() on the serv=
er.  That does not seem to be the case in the trunk/10.3.  Can you try runn=
ing jdbcapi/LargeDataLocks.java and see if perhaps this can be resolved eas=
ily.


 was:
V. Narayanan said
>Features of locator are not present for the ResultSet
>and the PreparedStatement methods.=20

I am a little confused by this. Are you saying that a ResultSet.getBinarySt=
ream() on the client should not be translating into a getBlob() on the clie=
nt.  That does not seem to be the case in the trunk/10.3.  Can you try runn=
ing jdbcapi/LargeDataLocks.java and see if perhaps this can be resolved eas=
ily.


> Closing a resultset after retrieving a large > 32665 bytes value with Net=
work Server does not release locks
> -------------------------------------------------------------------------=
----------------------------------
>
>                 Key: DERBY-2892
>                 URL: https://issues.apache.org/jira/browse/DERBY-2892
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.2.2.0, 10.3.1.1
>         Environment: JDK: build 1.6.0_01-b06 (WinXP & Gentoo/SuSE)
> Hardware: Intel x86
> Client/Server environment
>            Reporter: Thomas Niessen
>            Priority: Critical
>         Attachments: DERBY-2892_07_10_07_try1_diff.txt, DERBY-2892_07_10_=
07_try1_stat.txt, DERBY-2892_07_13_07_try2_diff.txt, DERBY-2892_07_13_07_tr=
y2_stat.txt, protocolErrorRepro.zip
>
>
> This is the same issue as DERBY-255 (https://issues.apache.org/jira/brows=
e/DERBY-255). The test attached to DERBY-255 shows the locks being not rele=
ased. Everything is fine when using Derby 10.1.3.1 .
> I would think it's a regression bug.
> Output from sysinfo:
> ------------------ Java-Informationen ------------------
> Java-Version: 1.6.0_01
> Java-Anbieter: Sun Microsystems Inc.
> Java-Home: C:\work\applications\development\java\jdk1.6u1-SE\jre
> Java-Klassenpfad: C:\work\applications\development\derby-10.2.2.0/lib/der=
by.jar;C:\work\applications\development\derby-
> 0.2.2.0/lib/derbynet.jar;C:\work\applications\development\derby-10.2.2.0/=
lib/derbyclient.jar;C:\work\applications\devel
> pment\derby-10.2.2.0/lib/derbytools.jar
> Name des Betriebssystems: Windows XP
> Architektur des Betriebssystems: x86
> Betriebssystemversion: 5.1
> Java-Benutzername: thomas.niessen
> Java-Benutzerausgangsverzeichnis: C:\Dokumente und Einstellungen\thomas.n=
iessen
> Java-Benutzerverzeichnis: C:\work\applications\development\derby-10.2.2.0
> java.specification.name: Java Platform API Specification
> java.specification.version: 1.6
> --------- Derby-Informationen --------
> JRE - JDBC: Java SE 6 - JDBC 4.0
> [C:\work\applications\development\derby-10.2.2.0\lib\derby.jar] 10.2.2.0 =
- (485682)
> [C:\work\applications\development\derby-10.2.2.0\lib\derbytools.jar] 10.2=
.2.0 - (485682)
> [C:\work\applications\development\derby-10.2.2.0\lib\derbynet.jar] 10.2.2=
.0 - (485682)
> [C:\work\applications\development\derby-10.2.2.0\lib\derbyclient.jar] 10.=
2.2.0 - (485682)
> ------------------------------------------------------
> ----------------- Informationen zur L=C3=B5ndereinstellung --------------=
---
> Aktuelle L=C3=B5ndereinstellung:  [Deutsch/Deutschland [de_DE]]
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [cs]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [de_DE]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [es]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [fr]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [hu]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [it]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [ja_JP]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [ko_KR]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [pl]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [pt_BR]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [ru]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [zh_CN]
>          Version: 10.2.2.0 - (485682)
> Es wurde Unterst=C2=B3tzung f=C2=B3r die folgende L=C3=B5ndereinstellung =
gefunden: [zh_TW]
>          Version: 10.2.2.0 - (485682)

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.