on 01-10-2013 3:35 PM
Hello Guys,
I am breaking my head on finding the root cause as to why the defualt trace file is being flooded with frequent messges.
We have this situation only on our devlopment portal.
Below is an excerpt from the default trace:
{0}#1#[Security Context : [Security Session (33376) for Administrator created at Thu Jan 10 08:39:45 EST 2013]]#
#1.#0019BBCCB98400280000DC20000013550004D2F0D866ED13#1357831771450#com.sap.engine.services.security.sessionmanagement##com.sap.engine.services.security.sessionmanagement#Administrator#33376##33088BB75B3911E2B97200000030F052#33088bb75b3911e2b97200000030f052-0#33088bb75b3911e2b97200000030f052#SAPEngine_Application_Thread[impl:3]_49##0#0#Path##Java###Entering SecurityContext.empty() on {0}#1#[Security Context : [Security Session (33376) for Administrator created at Thu Jan 10 08:39:45 EST 2013]]#
Can anyone pinpoint or suggest something to check upon?
Thanks and Regards,
Ankit Mishra
was able to reduce the trace entries by changing the severity level for tracing locations to "Error" in visual admin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.