[
https://issues.apache.org/jira/browse/DERBY-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921289#comment-13921289
]
Rick Hillegas commented on DERBY-6492:
--------------------------------------
Linking this issue to DERBY-6496. It may be a red herring. However, that bug
involves another context which sometimes is present and sometimes isn't.
DERBY-6496 has a test case which reliably fails without the corresponding fix.
Maybe that reliable failure can help track down the problem on this issue.
> ASSERT FAILED: LanguageConnectionContext is null
> ------------------------------------------------
>
> Key: DERBY-6492
> URL: https://issues.apache.org/jira/browse/DERBY-6492
> Project: Derby
> Issue Type: Bug
> Components: Services
> Affects Versions: 10.10.1.1
> Reporter: Florian Rapp
>
> The LanguageConnectionContext is sometimes null when the system is under
> heavy load. This seems to be a problem of multithreaded access.
> Our production test got NPE and ArrayIndexOutOfBounds exceptions, we then
> enabled more logging. We suspect the problem is
> BaseActivation.initFromContext. The context seems to not be properly
> initialized, probably due to multithreaded access. The NPE we got could stem
> from "context.getContextManager()".
> An exception ('ASSERT FAILED lcc is null in activation type class
> org.apache.derby.exe.aca90748aax0144x7731x56b2x0000131d61d046') occurred in
> Derby and will be wrapped:
> org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED lcc is
> null in activation type class
> org.apache.derby.exe.aca90748aax0144x7731x56b2x0000131d61d046
> at
> org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:162)
> at
> org.apache.derby.shared.common.sanity.SanityManager.THROWASSERT(SanityManager.java:147)
> at
> org.apache.derby.impl.sql.execute.BaseActivation.initFromContext(BaseActivation.java:236)
> at
> org.apache.derby.impl.services.reflect.LoadedGeneratedClass.newInstance(LoadedGeneratedClass.java:69)
> at
> org.apache.derby.impl.sql.GenericActivationHolder.<init>(GenericActivationHolder.java:129)
> at
> org.apache.derby.impl.sql.GenericPreparedStatement.getActivation(GenericPreparedStatement.java:270)
> at
> org.apache.derby.impl.jdbc.EmbedPreparedStatement.<init>(EmbedPreparedStatement.java:140)
> at
> org.apache.derby.impl.jdbc.EmbedPreparedStatement20.<init>(EmbedPreparedStatement20.java:83)
> at
> org.apache.derby.impl.jdbc.EmbedPreparedStatement30.<init>(EmbedPreparedStatement30.java:63)
> at
> org.apache.derby.impl.jdbc.EmbedPreparedStatement40.<init>(EmbedPreparedStatement40.java:40)
> at
> org.apache.derby.jdbc.Driver40.newEmbedPreparedStatement(Driver40.java:102)
> at
> org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConnection.java:1725)
> at
> org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConnection.java:1553)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
