You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Aleksander Adamowski (JIRA)" <ji...@apache.org> on 2009/04/20 12:18:47 UTC

[jira] Created: (DIRSERVER-1350) Support changing log4j configuration for SiRunner-launched ApacheDS instances

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/dev@directory.apache.org/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.

[jira] Updated: (DIRSERVER-1350) Support changing log4j configuration for SiRunner-launched ApacheDS instances

Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kiran Ayyagari updated DIRSERVER-1350:
--------------------------------------

    Fix Version/s: 2.0.0
                       (was: 2.0.0-RC1)

Liked the idea too, will see if it is feasible to add this in the new test famework, however postponing this issue for a future versio cause after a quick evaluation looks like it needs significant amount of time to implement(a new annotation with atleast two options for setting logger config and applying the config on underlying logging provider) hence postponing.

> 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
>            Assignee: Kiran Ayyagari
>             Fix For: 2.0.0
>
>
> See the discussion at http://www.mail-archive.com/dev@directory.apache.org/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.

[jira] Assigned: (DIRSERVER-1350) Support changing log4j configuration for SiRunner-launched ApacheDS instances

Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kiran Ayyagari reassigned DIRSERVER-1350:
-----------------------------------------

    Assignee: Kiran Ayyagari

> 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
>            Assignee: Kiran Ayyagari
>             Fix For: 2.0.0-RC1
>
>
> See the discussion at http://www.mail-archive.com/dev@directory.apache.org/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.

[jira] Commented: (DIRSERVER-1350) Support changing log4j configuration for SiRunner-launched ApacheDS instances

Posted by "Aleksander Adamowski (JIRA)" <ji...@apache.org>.
    [ 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/dev@directory.apache.org/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.

[jira] Updated: (DIRSERVER-1350) Support changing log4j configuration for SiRunner-launched ApacheDS instances

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-1350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-1350:
-----------------------------------------

    Fix Version/s: 2.0.0-RC1

Interesting suggestion, but we won't have time to fix it for 1.5.5

> 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
>             Fix For: 2.0.0-RC1
>
>
> See the discussion at http://www.mail-archive.com/dev@directory.apache.org/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.