[
https://issues.apache.org/jira/browse/DIRSERVER-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700756#action_12700756
]
Aleksander Adamowski commented on DIRSERVER-1350:
-------------------------------------------------
BTW, an example problem to rationalize the need:
I have several Surefire tests that use ApacheDS (using SiRunner) in a number of
Maven artifacts. All tests have a class-level cleanup.
In one artifact, all tests run fine and ApacheDS instance is started ans
stopped before/after each test class.
In another artifact, seemingly analogous, I have a problem where the JVM simply
exists (with code 0) when launching ApacheDS for the second test that requires
Apache DS.
Without logging it's extremely hard to debug why is JVM shutting down
(presumably some critical Apache DS error, but it leaves no traces).
> Support changing log4j configuration for SiRunner-launched ApacheDS instances
> -----------------------------------------------------------------------------
>
> Key: DIRSERVER-1350
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1350
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 1.5.4
> Reporter: Aleksander Adamowski
>
> See the discussion at
> http://www.mail-archive.com/[email protected]/msg23067.html for
> initial details.
> It seems that currently the log4j configuration is forcibly hardcoded inside
> the ApacheDS JARs and a log4j configuration file placed on test classpath
> doesn't influence Apache DS components' logging.
> It makes it extremely hard to diagnose problems with launching and shutting
> down the embeddded Apache DS instance used for tests
> (http://cwiki.apache.org/DIRxSRVx11/42-using-apacheds-for-unit-tests.html).
> There should be a way to override the logging configuration of all ApacheDS
> components using a log4j configuration file placed on the unit test classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
