Find Answers

Filter Search Results
All Products:

Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML log4j warning in serena vm application server
log 4 j warning in serena vm application server
CMS-XML SRA:4.5.1: DEF245931: download artifact plugin reports log4j appender warnings
SRA: 4 .5.1: DEF245931: download artifact plugin reports log 4 j appender warnings
CMS-XML VM 8.4.x on UNIX / Linux lacks sso-gatekeeper.log file
This issue is caused by an incorrect LOGFILE directive in the file vm/common/tomcat/webapps/vminet/WEB-INF/alfssogatekeeper/conf/ log 4 j .properties Until this defect has been fixed, the problem can be resolved by manually updating the line: log4j.appender.LOGFILE.File=${jboss.server.home.dir}/log/sso-gatekeeper.log
CMS-XML Tomcat components cannot log in cluster - some log files are empty including console.log
With Tomcat cluster log 4 j .xml file corrupted that results in empty logs in folder
CMS-XML DA: When TRACE logging is enabled for plugin runtime then secure property values may appear unmasked in deployserver.out log file
Trace logging for plugin runtime may be enabled if the following line and setting are present in your DA server log 4 j .properties file:
CMS-XML Problems with SSO Log File Growth After Upgrade to SBM 11.1
To work around this problem, edit the following 2 files: On the Application Engine server, edit [INSTALLDIR]\Application Engine\alfssojavabridge\alfssogatekeeper\conf\ log 4 j .properties On the SSO server, edit [INSTALLDIR]\\Common\Tomcat 7.0\server\default\webapps\idp\WEB-INF\conf\log4j.properties
CMS-XML Invalid Setting Can Break Application Repository Log
Stop the JBoss service. Open the mashupmgr. log4j .properties file located in the installDir
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- log 4 j .xml. Search for the SerenaCommonLogger section. Change:
CMS-XML PDF Widget: Chrome cannot download PDF, get error "HTTP Get is not supported" in Tomcat log
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[catalina.jar:8.5.46] at com.serena. log 4 j .http.TrafficLoggingFilter.doFilter(TrafficLoggingFilter.java:99) ~[common-util-11.7.jar:?] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[catalina.jar:8.5.46]
CMS-XML Common log entries are truncated in composer even when setting maxMessageSize = 128kb
The standard maximum length of a Common Log (CL) entry may be set in Composer to 16KiB. If entries longer than that need to be processed in their entirety, it is possible to increase the upper limit in the log 4 j definition :
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs