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 SRA: Upgrade will render SRA unusable if Tomcat is not stopped beforehand
SRA: Upgrade will render SRA unusable if Tomcat is not stopped beforehand
CMS-XML When restarting IIS or Tomcat service it stops but then doesn't start
2) Configure default settings. 3) Start IIS or Tomcat service on Manage Services page. 4) Click 'Restart' button to restart IIS or Tomcat.
CMS-XML SBM: Tomcat starts and immediately stops with error: StandardServer.await: create[localhost:8005] java.net.BindException: Address already in use: JVM_Bind
Under some circumstances SBM Tomcat may shut down immediately after start and the below error message may appear on C:\Program Files\Serena\SBM\Common\Tomcat 7.0\server\default\logs\tomcat.log
CMS-XML SDA on Tomcat hangs during shutdown process until it is killed forcefully.
SDA on Tomcat hangs during shutdown process until it is killed forcefully.
CMS-XML DM913 - Tomcat not responding, Error - Exception looking up UserDatabase under key UserDatabase
When tomcat is started, Adminconsole and Webclient are not accessible and tomcat home page 8080 does not respond either. Looking in the catalina log you might see something similar to this... Exception looking up UserDatabase under key UserDatabase
CMS-XML Potential memory leaks causing REST interface tomcat task to hang audit job submission
A customer has been testing their upgrade to 8.2 Patch 3. Suddenly and unexpectedly all attempts to run audit against ZMF packages resulted in the file tailoring (e.g. CMNsADSP) tasks hanging. They had to restart both their ZMF Server and their REST API Tomcat started tasks to resolve the issue.
CMS-XML SBM: Tomcat will not stay running. Console log gives: Failed upgrading SLA server schema
After an upgrade, Tomcat will start, run for a few seconds, and stop . When looking in the console.log, the following error displays:
CMS-XML Illegal access: this web application instance has been stopped already
In PVCS Version Manager - versions 8.1.0 through 8.2.1.1, the Tomcat parameter "reloadable" is set to "true" for the web applications used by the Serena VM Web Application Server. In rare instances, this causes excessive repeated logging of the following error message:
CMS-XML DimCM: Pulse: Pulse not working after upgrade to Tomcat 8.5.54
After upgrading Tomcat to a newer version, 8.5.54, Pulse stops working.
CMS-XML Tomcat does not start fully without any obvious error message or explanation
When one of the files in the tomcat "work" directory gets locked by another process (for example by not fully stopped tomcat instance), Configurator fails to proceed with copying webapp contexts files. This may lead to issues with Tomcat without any indication of the problem in Configurator.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs