[
https://issues.apache.org/jira/browse/DERBY-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119795#comment-13119795
]
Dag H. Wanvik commented on DERBY-3823:
--------------------------------------
As for activation class, while preparing a statement, the activation class can
be null for a while, cf. code in GenericStatement#prepMinion, ca line 207: and
then set again line 502. If the above code tries to access the prepared
statement's metadata while the statement is being recompiled (many threads,
cached ps), getActivationClass could return null. I am not sure that's what's
happening, though, since I can't see why the statement should become
invalidated in the test (update of main/main2).
> 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
> Reporter: Kathey Marsden
> Labels: derby_triage10_5_2
> Attachments: 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
