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  
Pages [Next]
  Results
CMS-XML VM: log4j:ERROR Failed to flush writer, java.io.InterruptedIOException
VM: log 4 j :ERROR Failed to flush writer, java.io.InterruptedIOException
CMS-XML PVCS Version Manager mitigation of 'log4j2' compromise - CVE-2021-44228
PVCS Version Manager mitigation of ' log 4 j 2' compromise - CVE-2021-44228
CMS-XML log4j warning in serena vm application server
log 4 j warning in serena vm application server
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 IDE: Enabling logging with the Rich Integration to the Eclipse workbench
To troubleshoot issues with the Rich Integration to Eclipse with VM, the Apache log 4 j logging services can be configured to capture helpful information. In the installation directory for VM, under the /vm/integrations/eclipse/plugins/com.serena.team.core_3.1.0 folder, there is a file named "log4j.properties
CMS-XML How to verify that the SSO Certificate Revocation List (CRL) files are being used
To find out, temporarily increase the debugging level of the STS component of the SSO server. To do this, shutdown the SSO server and edit the log 4 j .properties file that is used by the TokenService.
CMS-XML VM 8.5.x cannot open SSO based Project Databases from SCC-based IDEs
If it does not already exist, create a sub-directory called patch Copy the file log 4 j -1.2.16.jar , located in the current directory, into the folder patch, so you end up with the file VM_Install_Dir
CMS-XML VM: certtool throws error and stack dump if the current directory is not writable
at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:138) at org.apache. logging . log4j .core.impl. Log 4 jContextFactory.getContext( Log 4 jContextFactory.java:147) at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:41)
CMS-XML VM GUI crash attempting to open a pdb with error "pvcs.mlutils.MLAdapter.getSessionId"
5a024000-5a0a9000 r--s 00000000 03:02 8585432 /usr/merant/vm/common/lib/castor.jar 5a0a9000-5a0be000 r--s 00000000 03:02 8585436 /usr/merant/vm/common/lib/ log 4 j .jar 5a0be000-5a1ab000 r--s 00000000 03:02 8585440 /usr/merant/vm/common/lib/xerces.jar
CMS-XML VM 8.6.1: In-place upgrade from VM 8.6.0 fails with Restore report showing a failure for the file gatekeeper-core-config.xml
20190415-165040: File copied successfully. ('D:\PVCS\Serena\bkstore\restores\1904051219.75F\files\common\pvcsprop\pvcs\vm\sso\ log 4 j .properties' -> 'D:\PVCS\Serena\vm\common\pvcsprop\pvcs\vm\sso\ log 4 j .properties'
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs