db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Korneliussen <Andreas.Kornelius...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-550) BLOB : java.lang.OutOfMemoryError with network JDBC driver (org.apache.derby.jdbc.ClientDriver)
Date Mon, 10 Jul 2006 13:19:18 GMT
TomohitoNakayama wrote:
> Hello Andreas.
> 
> I have some question for your comment....
> 
> Reading beggining part, I take your reported phenomena as problem when 
> scrollable resultset is used.
> However,reading last part, I found  your report tells that problem was 
> found also when forward-only resultset was used.
> 
> I feel some inconsistency and cannot be sure I understand your comment ....
> 
> My question is whether your report is limited to scrollable resultset, 
> or not
> Please give me your answer..
> 
> Best regards.
> 
Hi, Tomohito

To answer your question: the problem applies to both scrollable and 
forward-only result sets.

When I first tested, I used scrollable resultsets. The second time I 
used forward-only resultsets, and got another problem when doing 
connect. I then restarted the network-server, and retried with 
forward-only resultset, and then I got the exactly same problem.

Below is the stack trace:

Exception in thread "main" 
org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED 
Number of parameters expected for message id 58009.C.6 (0) does not 
match number of arguments received (1)
         at 
org.apache.derby.shared.common.sanity.SanityManager.ASSERT(SanityManager.java:119)
         at 
org.apache.derby.shared.common.i18n.MessageUtil.formatMessage(MessageUtil.java:233)
         at 
org.apache.derby.shared.common.i18n.MessageUtil.getCompleteMessage(MessageUtil.java:142)
         at 
org.apache.derby.shared.common.i18n.MessageUtil.getCompleteMessage(MessageUtil.java:182)
         at 
org.apache.derby.shared.common.i18n.MessageUtil.getCompleteMessage(MessageUtil.java:98)
         at 
org.apache.derby.client.am.SqlException.<init>(SqlException.java:168)
         at 
org.apache.derby.client.am.SqlException.<init>(SqlException.java:182)
         at 
org.apache.derby.client.am.DisconnectException.<init>(DisconnectException.java:28)
         at 
org.apache.derby.client.am.DisconnectException.<init>(DisconnectException.java:39)
         at 
org.apache.derby.client.am.DisconnectException.<init>(DisconnectException.java:49)
         at 
org.apache.derby.client.am.DisconnectException.<init>(DisconnectException.java:67)
         at 
org.apache.derby.client.net.NetStatementReply.copyEXTDTA(NetStatementReply.java:1486)
         at 
org.apache.derby.client.net.NetResultSetReply.parseCNTQRYreply(NetResultSetReply.java:139)
         at 
org.apache.derby.client.net.NetResultSetReply.readFetch(NetResultSetReply.java:41)
         at 
org.apache.derby.client.net.ResultSetReply.readFetch(ResultSetReply.java:40)
         at 
org.apache.derby.client.net.NetResultSet.readFetch_(NetResultSet.java:205)
         at 
org.apache.derby.client.am.ResultSet.flowFetch(ResultSet.java:4160)
         at 
org.apache.derby.client.net.NetCursor.getMoreData_(NetCursor.java:1182)
         at org.apache.derby.client.am.Cursor.stepNext(Cursor.java:176)
         at org.apache.derby.client.am.Cursor.next(Cursor.java:195)
         at org.apache.derby.client.am.ResultSet.nextX(ResultSet.java:299)
         at org.apache.derby.client.am.ResultSet.next(ResultSet.java:269)
         at derbytest.BlobOutOfMem.main(BlobOutOfMem.java:95)

My application has a BLOB column of size 64 MB, which I inserted in 
embedded mode. If you like, I can upload it to the JIRA.

Regards

--Andreas

Mime
View raw message