My Oracle Support Banner

Erroneous Logging of "Invalid path /logout was requested" in appserverlog.xml File (Doc ID 2146386.1)

Last updated on MAY 14, 2018

Applies to:

Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.

Symptoms

MetaSolv Solution 6.2.1

An "Invalid path /logout was requested" error is erroneously logged in the appserverlog.xml file when a user closes the application. User login and logout messages should only be logged to the appserver_auditlog.xml file.

Error in appserverlog.xml

<log4j:event logger="org.apache.struts.action.RequestProcessor" timestamp="1464920329826" level="ERROR" thread="[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'">
<log4j:message><![CDATA[Invalid path /logout was requested]]></log4j:message>


Recreation Steps

The issue can be reproduced at will with the following steps:

1. Open two PuTTY sessions and "tail" the log files listed below

  - appserverlog.xml
  - appserver_auditlog.xml

2. Logon to the MetaSolv Solution client (tbs.exe)

3. Note the logged message below in the appserver_auditlog.xml file indicating a login was detected for a user that has signed on.

<log4j:event logger="cmm.Security" timestamp="1464920338917" level="INFO" thread="[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'">
<log4j:message><![CDATA[[machineName :: servername.company.com][appServerName :: DEF_APPSERVER][userName :: SGETTS][productName :: nur][messageID :: 0001][moduleName :: cmm.Security][className :: DEF_CLASS][debugCode :: 0]::Login detected for SGETTS.::User has signed on.::None.::]]></log4j:message>
</log4j:event> 


4. Close the MetaSolv Solution client and note the behavior between the two log files:

(a) The message below is logged to the appserver_auditlog.xml file indicating a logout was detected for a user or their client has disconnected. This is correct behavior.

<log4j:event logger="cmm.Security" timestamp="1464920338940" level="INFO" thread="[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'">
<log4j:message><![CDATA[[machineName :: servername.company.com][appServerName :: DEF_APPSERVER][userName :: SGETTS][productName :: nur][messageID :: 0002][moduleName :: cmm.Security][className :: DEF_CLASS][debugCode :: 0]::Logout detected for SGETTS.::Logout by user or Client disconnected.::None.::]]></log4j:message>
</log4j:event>

(b) The message below is logged to the appserverlog.xml file. This is incorrect behavior.

<log4j:event logger="org.apache.struts.action.RequestProcessor" timestamp="1464920329826" level="ERROR" thread="[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'">
<log4j:message><![CDATA[Invalid path /logout was requested]]></log4j:message>
</log4j:event>

 

Business Impact

Erroneous logging causes unnecessary log file growth and makes it more difficult to troubleshoot problems due to the "additional noise" in the log file.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.