Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Date: Tue, 04 Mar 2008 17:06:17 +0530
From: Narayanan <V.Narayanan@Sun.COM>
Subject: Re: NPE getting length of Blob
In-reply-to: <200803041607.55832.daniel@nuix.com>
Sender: V.Narayanan@Sun.COM
To: Derby Discussion <derby-user@db.apache.org>
Message-id: <47CD3431.5020205@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <200803041607.55832.daniel@nuix.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071022)

Daniel Noll wrote:
> Hi all.
>
> I have someone seeing the following error under both 10.3.1.4 and 10.3.2.1:
>
> java.lang.NullPointerException
> 	at org.apache.derby.client.am.PreparedStatement.setIntX(Unknown Source)
> 	at org.apache.derby.client.am.CallableLocatorProcedures.blobGetLength(Unknown 
> Source)
> 	at org.apache.derby.client.am.Blob.getLocatorLength(Unknown Source)
> 	at org.apache.derby.client.am.Lob.sqlLength(Unknown Source)
> 	at org.apache.derby.client.am.Blob.length(Unknown Source)
>
> Has anyone seen something like this before?  What is the cause of the problem?  
> The exact same code on the exact same version of Derby doesn't cause the same 
> problem over here; could it be something which only happens when unusual 
> network conditions are happening, or something which only happens when the 
> database meets a certain condition?
>
> Daniel
>   
I have tried getting a blob from a result set and tried the length() 
method on it after the following
Scenarios

1) Closing the connection
2) committing the transaction
3) Rolling back the transaction

In the above three I got the expected SQLState.

4) Tried shutting down the network server just before blob.length I get 
the following

Exception in thread "main" java.sql.SQLNonTransientConnectionException: 
Insufficient data while reading from the network - expected a minimum of 
6 bytes and received only -1 bytes. The connection has been terminated.
at 
org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70)
at 
org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362)
at org.apache.derby.client.am.Blob.length(Blob.java:141)
at javaapplication2.Main.main(Main.java:31)

None of the above scenarios seem to be giving the exception pointed out.

Narayanan