remove log4j appender from an API

[Markus Andersson]

Hi!
I hope the post is in the correct forum area.

I have a quite annoying problem, I have written an integration between two systems and after all I realize that log4j would be really good for logging.
And I just switched out my regular logger and appended log4j, but there is a problem with the API that I'm using, it has a log4j appender in the precompiled source. Is there a way to just remove that logger? I tried to remove is but with no luck, it still log in the wrong file with the wrong settings when the API has been used.

Any good ideas of how I can disable the API log4j appender?

Best Regards
Markus

[Ulf Dittmer]

Welcome to JavaRanch.

In most cases, log4j takes all its configuration from an external file (often called "log4j.properties"). If that's the case here, then you should be able to replace the configuration that comes with the library with your own configuration.

[Markus Andersson]

Hi!

I have already made a log4j configuration, and added the set the log4j in debug mode here is the output from the console when I run the application.

 run:
log4j: Trying to find [log4j.xml] using context classloader sun.misc.Launcher$AppClassLoader@a39137.
log4j: Trying to find [log4j.xml] using sun.misc.Launcher$AppClassLoader@a39137 class loader.
log4j: Trying to find [log4j.xml] using ClassLoader.getSystemResource().
log4j: Trying to find [log4j.properties] using context classloader sun.misc.Launcher$AppClassLoader@a39137.
log4j: Using URL [file:/C:/PM/ScalaPMActual/conf/log4j.properties] for automatic log4j configuration.
log4j: Reading configuration from URL file:/C:/Ansaldo/ScalaPMActual/conf/log4j.properties
log4j: Could not find root logger information. Is this OK?
log4j: Parsing for [org.springframework] with value=[DEBUG, appender].
log4j: Level token is [DEBUG].
log4j: Category org.springframework set to DEBUG
log4j: Parsing appender named "appender".
log4j: Parsing layout options for "appender".
log4j: Setting property [conversionPattern] to [%d{dd MMM yyyy HH:mm:ss, SSS} [%t] %-5p %c - %m%n].
log4j: End of parsing for "appender".
log4j: Parsed "appender" options.
log4j:WARN File option not set for appender [appender].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?
log4j: Handling log4j.additivity.org.springframework=[null]
log4j: Finished configuring.
log4j: setFile called: C:\PM\ScalaPMActual\log\lo.html, true
log4j: setFile ended
log4j: setFile called: C:\P6API/PM\my_PM.html, true
log4j: setFile ended
BUILD SUCCESSFUL (total time: 5 seconds)

lo.html is "my log file" and my_PM.html is "API log file" which I don't mind if it's created or not but it's steeling my log entries.
The problem is that the API I'm forced to use is creating a new log4j appender and all logs are after that handled by that appender.
The API don't have a log4j.properties or log4j.XML files. I guess it's compiled into the code.

I have realized that the new Appender from the API is called A, then I tried to remove that appender

    
logger.removeAppender("A");   //Removing API appender
logger.addAppender(appender); //Readding Standard appender

But it stills uses the A appender. I can't access the A appender from the API it's automatically used by the API.

Any good suggestions?
//
Markus

[Martijn Verburg]

Hi there,

Have you tried setting the root configuration, e.g. (From a sample log4j.xml)

  <root>
    <!-- set default logging level for all -->
    <priority value="INFO"/>
    <appender-ref ref="dias-assetTgt"/>
    <appender-ref ref="jvbridge-staticSrc"/>
    <!-- <appender-ref ref="A"/> -->
    <appender-ref ref="msgBroker-static"/>
    <appender-ref ref="msgBroker-risk"/>
  </root>