[DERBY-6496] Optional tool registration may fail because the CompilerContext is not always available at execution time.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.11.1.1
• Fix Version/s: 10.10.2.1, 10.11.1.1
• Component/s: SQL
• Urgency: Normal
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 05/Mar/14 19:24
• Updated: 22/Oct/14 18:15
• Resolved: 22/Oct/14 18:15

Description

For reasons which elude me, the CompilerContext is sometimes available at execution time and sometimes not. When the CompilerContext is not available at execution time, optional tool loading fails on an NPE:

Caused by: java.lang.NullPointerException
at org.apache.derby.catalog.Java5SystemProcedures.SYSCS_REGISTER_TOOL(Java5SystemProcedures.java:104)
at org.apache.derby.exe.ac4d3680a5x0144x93adx0136xffffe1d7aa3e0.g0(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.apache.derby.impl.services.reflect.ReflectMethod.invoke(ReflectMethod.java:46)
at org.apache.derby.impl.sql.execute.CallStatementResultSet.open(CallStatementResultSet.java:75)
at org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(GenericPreparedStatement.java:470)
at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:349)
at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1338)

Issue Links

• duplicates: DERBY-6442 NPE when loading optional tools from multiple threads
• is related to: DERBY-6492 ASSERT FAILED: LanguageConnectionContext is null
• is related to: DERBY-6442 NPE when loading optional tools from multiple threads
• relates to: DERBY-6759 Derby 10.10 backport issue (fall 2014)