db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-3823) NullPointerException in stress.multi test
Date Wed, 12 Oct 2011 23:49:11 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126252#comment-13126252
] 

Dag H. Wanvik commented on DERBY-3823:
--------------------------------------

Thanks for helping me understand this, Mamta! From you test program it appears that the metadata
returned even in the client case is still correct (i.e. c12's size is still 5) . Since that's
the result set we are processing (still), I think that is correct even though the underlying
table now has length 8. I was worried we might somehow be able to retrieve the new values,
8, while still reading the "old" style result set on the client. Isn't metadata cached on
the client also? If so the second call to "rsmd = rs.getMetaData();" may not even visit the
server, unless you trace it to determine that it did.. I will try to tweak your program and
debug to see if I can provoke it to return "8" while we are still reading the result set that
has 5 as max lenght for c12... If that were possible it would be an error, I think. That fact
that we are able to *insert* longer data than 5 is not wrong, since the underlying database
has changed. I believe *database* metadata would correctly reflect that? But the *result set*
metadata should stick to the actual data in the (old) result set I believe.
                
> NullPointerException in stress.multi test
> -----------------------------------------
>
>                 Key: DERBY-3823
>                 URL: https://issues.apache.org/jira/browse/DERBY-3823
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.3.3.1, 10.7.1.1, 10.8.1.2
>            Reporter: Kathey Marsden
>              Labels: derby_triage10_5_2
>         Attachments: d3823-1.diff, derby.log
>
>
> I saw the following NPE in stress.multi running on 10.3 with derbyclient.
> java.lang.NullPointerException
>         at org.apache.derby.impl.jdbc.EmbedPreparedStatement.getMetaData(Unknown
>  Source)
>         at org.apache.derby.impl.drda.DRDAConnThread.writeSQLDARD(Unknown Source
> )
>         at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Sou
> rce)
>         at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
> Cleanup action completed

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message