[
https://issues.apache.org/jira/browse/SOLR-13268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775737#comment-16775737
]
Kevin Risden commented on SOLR-13268:
-------------------------------------
Some other info about log4j2 and LMAX releases.
We are on LMAX 3.4.0 and there is a 3.4.2 with changes related to
`BatchEventProcessor` which was in the stack trace
* 3.4.1 - Fix race between run() and halt() on BatchEventProcessor.
* 3.4.2 - Fix for race condition on restart of BatchEventProcessor with 3 or
more threads.
* https://github.com/LMAX-Exchange/disruptor/releases
Upgrading LMAX disrupter to 3.4.2 was in the log4j 2.11.1 release notes. We
could also upgrade log4j2 2.11.0 -> 2.11.2.
Not sure if these would help but probably wouldn't hurt either.
> Clean up any test failures resulting from SOLR-12055 (async logging)
> --------------------------------------------------------------------
>
> Key: SOLR-13268
> URL: https://issues.apache.org/jira/browse/SOLR-13268
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Major
>
> This is a catch-all for test failures due to the async logging changes. So
> far, the I see a couple failures on JDK13 only. I'll collect a "starter set"
> here, these are likely systemic, once the root cause is found/fixed, then
> others are likely fixed as well.
> JDK13:
> ant test -Dtestcase=TestJmxIntegration -Dtests.seed=54B30AC62A2D71E
> -Dtests.multiplier=3 -Dtests.slow=true -Dtests.locale=lv-LV
> -Dtests.timezone=Asia/Riyadh -Dtests.asserts=true -Dtests.file.encoding=UTF-8
> ant test -Dtestcase=TestDynamicURP -Dtests.seed=54B30AC62A2D71E
> -Dtests.multiplier=3 -Dtests.slow=true -Dtests.locale=rwk
> -Dtests.timezone=Australia/Brisbane -Dtests.asserts=true
> -Dtests.file.encoding=UTF-8
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
