Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
  Results
CMS-XML Common log entries are truncated in composer even when setting maxMessageSize = 128kb
<appender name=" SerenaCommonLogger " class="com.serena.commonlogger.Appender"> <errorHandler class="org.apache.log4j.helpers.OnlyOnceErrorHandler" />
CMS-XML Log orchestration category of logs to a file rather than the Common Log
... ref=" SerenaCommonLogger " /> ... ref=" SerenaCommonLogger " /> ... name=" SerenaCommonLogger ".. ... ... commented out " SerenaCommonLogger " appender. Rename the copied "SERVERLOG" appender to " SerenaCommonLogger ", change the filename in it to e.g. "${server.log.dir}/common.log". ... <!--<appender name=" SerenaCommonLogger " class="com.serena.commonlogger.Appender"> ... <param name=" maxMessageSize " value="8" /> ... <appender name=" SerenaCommonLogger
CMS-XML Common Logger messages are truncated
The actual length of the message is limited by a SerenaCommonLogger appender configuration setting: ... param name=" maxMessageSize " value="8" where the value of maxMessageSize is the number of kilobytes.
CMS-XML Improving Common Log Performance when Debug Logging Is Enabled for Orchestrations
On the server on which SBM Application Administrator is installed, navigate to Program Files\Serena\SBM\Common\jboss405\server\default\conf\jboss-log4j.xml. Search for the SerenaCommonLogger section. Change:

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs