Different Severities for different Destinations/Logging/Tracing

[Former Member]

Hi experts,

I found myself confronted with a problem I'm not able to handle without help.

I'm working in the SAP Netweaver 6.40 SP 22 environment.

There I created an EAR- project including a log-configuration.xml.

In this document I configured my Log Controllers and Destinations. Everything works fine, except one thing:

I added 2 different destinations to one Log-Controller. So the traces/logs are written in both files. Till now it works without problems.

But I want to differ the output in both files.

Example:

In Trace-File1 every message with severity WARNING and higher should be stored.

In Trace-File2 every message with severity ERROR and higher should be stored.

My problem:

The tracing uses only the severity of the log-controller which contains both destinations.(referenced destinations)

The severity settings of the destinations are ignored.

Is this the normal behavior, and is there a possibility to change that, so that my example is possible?

Thank you for taking the time to answer my questions. I look forward to your responses.

(I'm away till tomorrow so please don't be disappointed if I don't tell you the results immediately. )

kind regards,

Martin

[snehal_kendre · Accepted solution]

Hi Martin,

Its a default behaviour.

We also face the same problem, we did with two diff log controller. to solve severity problem and it also helped to create two diff files one for log, and one for tracing

[Former Member · Accepted solution]

Thank you snehal.

I have suspected, that this is the only possibility...

It's just kind of circuitous to log every message twice.

loc1.errorT("foo");

loc2.errorT("foo");

And to do so in approximately 90 classes won't be fun.

But thank you anyway, we'll see whether this is worth it.

regards

Martin