[
https://issues.apache.org/jira/browse/SOLR-16167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527596#comment-17527596
]
Michael Gibney commented on SOLR-16167:
---------------------------------------
Thanks, Dawid. If there's no straightforward immediate solution, maybe the best
way forward is to fix existing cases, and be vigilant for now, pending a
possible upstream fix:
[google/error-prone#2062|https://github.com/google/error-prone/issues/2062].
> Review static initializers that reference subclasses
> ----------------------------------------------------
>
> Key: SOLR-16167
> URL: https://issues.apache.org/jira/browse/SOLR-16167
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: main (10.0)
> Reporter: Michael Gibney
> Priority: Major
> Attachments: StaticInitializerReferencesSubClass.xml
>
>
> More general follow-up to SOLR-16165.
> There is the potential for classloading deadlock in the case where static
> initializers reference a subclass.
> This issue could cover 1 or 2 things:
> # Fix existing issues
> # Add a build check to prevent such issues from being introduced in the future
> Fixing existing issues should be relatively straightforward, once we're
> specifically looking for them. "in the wild" these are problematic enough
> that it's probably worth just fixing all such issues whether or not they
> manifest as deadlock in practice.
> It would be great if we could port/modify/leverage an existing implementation
> that already checks for this and have it apply automatically in the build,
> unless this approach proves impractical.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
