[DERBY-6724] NPE if insert statement needs recompilation after having fired a trigger

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.1.4, 10.4.1.3, 10.5.1.1, 10.6.1.0, 10.7.1.1, 10.8.1.2, 10.9.1.0, 10.10.1.1, 10.11.1.1
• Fix Version/s: 10.11.1.3, 10.12.1.1
• Component/s: SQL
• Issue & fix info: Repro attached
• Bug behavior facts: Regression
• Assignee: Knut Anders Hatlen
• Reporter: Knut Anders Hatlen
• Created: 02/Sep/14 12:23
• Updated: 09/Sep/16 09:52
• Resolved: 05/Sep/14 09:11

Description

If an insert statement that has fired a trigger, is needs recompilation during execution, it fails with a NullPointerException in InternalTriggerExecutionContext.cleanup():

java.lang.NullPointerException
	at org.apache.derby.impl.sql.execute.InternalTriggerExecutionContext.cleanup(InternalTriggerExecutionContext.java:236)
	at org.apache.derby.impl.sql.execute.TriggerEventActivator.cleanup(TriggerEventActivator.java:291)
	at org.apache.derby.impl.sql.execute.InsertResultSet.cleanUp(InsertResultSet.java:2199)
	at org.apache.derby.impl.sql.conn.GenericStatementContext.cleanupOnError(GenericStatementContext.java:543)
	at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(GenericPreparedStatement.java:476)
	at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:349)
	at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1337)
	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(EmbedPreparedStatement.java:1709)
	at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(EmbedPreparedStatement.java:1394)

Issue Links

• relates to: DERBY-6722 GenericStatementContext.cleanupOnError() needs protection from later errors during statement cleanup
• relates to: DERBY-827 Performance can be improved by re-using language ResultSets across Activation executions.