Par application - Trace level=all after j2ee restart

[Former Member]

Hello,

I'm not sure that is the right place to post this question so, don't hesitate to root me to another thread.

We use the SAP Enterprise Portal EP6 base on NW2004 SPS16.

We have developped some Portal Application. (par). Those applications contain a logger.xml file to describe the trace settings.

In visual Admin\Log configurator, we define the trace level to "Error" for those applications nodes. But, after application deployment, or after j2ee engine restart, the trace level level is automaticaly set to "All". It only appens to our applications and not to other WAS traces.

I think problem is due to the logger.xml but, after lookup on a lot of thread, it seems we use it in the good way.

<u>eg:</u>

<Server>
<Logger       name="corp.mycompany.application.myApplicationName.logger"
              loggerInterface="com.sapportals.portal.prt.logger.ILogger"
              locationName="corp.mycompany.application.myApplicationName"
              pattern="%d # %20t %15s %m #"
	       	  isActive="true">
     <LoggerClass className="com.sapportals.portal.prt.logger.SimpleFileLogger" level="Error">
     </LoggerClass>
</Logger>
</Server>

Did we miss something ? Do we manage our traces in thge good way ?

Please advice.

Thanks for your support

Laurent

[Former Member · Accepted solution]

Laurent,

Do have a look at this<a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1794">weblog</a>

check this

<a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5f04b290-0201-0010-1387-d2df53065422">pdf</a>

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/e2/75a74046033913e10000000a155106/frameset.htm">Active Tracing</a>

Are all the configurations nd settings done are accordingly?

Thanks,

Swathi

[Former Member]

I have found the solution.

The answer was in the pdf in the post of Swathi. Thanks Swathi.

level="ERROR" seems to be unknowed by the systelm so the level is set to ALL

level="SEVERE" => level="ERROR"

It seems there is a bug in SPS16 (may be earlier) : SEVERE means ERROR where as ERROR means nothing.

Thanks all for your support

Have a nice day. Mine will be good for sure 😛

[praveenkumar_gudapati]

Hi Laurent,

At a first glance I would correct the logger.xml by setting the level="<b>ERROR</b>". No sure but it could be case sensitive.

It is true that what ever log level you configure through log configurator gets lost when you redeploy the application or restart the server. So this behavior is common.

So at the end it is important what level you set in your logger.xml

So set level to ERROR all capitals and redeploy your application.

Greetings,

Praveen Gudapati

p.s. Points are always welcome for helpful answers

[Former Member]

Hi Praveen,

Thanks for your advice.

The behavior is the same with level ="ERROR". I have already tested with "error", "Error" and "ERROR"

I have received an answer to our customer message to sap.

They explain that it is a known issue which is solved in NW2004 SPS19.

To be honest I'm surprised by this answer...

I'm still looking for a solution.

Have a nice day