Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML DA: Getting occurrences of java.lang.OutOfMemoryError: GC overhead limit exceeded in Tomcat logs
DA: Getting occurrences of java.lang.OutOfMemoryError: GC overhead limit exceeded in Tomcat logs
CMS-XML DA: How to run DA Component Process on only one resource/agent at a time
The simplest method of restricting the process to one resource at a time is to use the "Max # of concurrent jobs" property in the Install Component Process Step (of the Application). To change this,
CMS-XML SDA: There is no configuration that can be utilized to mitigate the risk of POODLE on Agent Relay http proxy port
Please see the knowledgebase, solution S140815 for details of mitigating this issue on jms port used by the Agent Relay port as well as the ports used by the SDA Server. If POODLE is a concern, we recommend utilizing firewall rules to restrict which hosts may connect to the Agent Relay http proxy port.
CMS-XML Agents don't appear online after a server upgrade to Deployment Automation version 6.1.1 or higher
: Some JRE's will also restrict the use of SSLv3. It may be worth checking the JRE used by Tomcat and the DA server. Within the JRE, navigate to: jre\lib\security.
PDF Serena Deployment Automation Guide
These roles determine which parts of the Deployment Automation web application users can access. Each page, such as Reports, on the web application's home page can be restricted . Available permissions are described in the following table.
CMS-XML SDA: Error "This version cannot be deleted because it is in use by the following" when deleting component version history
Component versions cannot be deleted, if ANY of these constraints are true:
CMS-XML SDA: Run Component Process dialog does not format correctly
The Run Component Process dialog does not format correctly for a Resource or Process longer than approximately 10 characters. These numbers overflow the bounds of the display box rather than wrapping within the box.
CMS-XML SDA: Error "The base filesystem path for this component does not exist"
This is actually caused by a Windows restriction . When the process was viewed using ProcMon it was clear that the Tomcat8 process was denied access to the relevant Windows share. This is because the service runs as Local System but when attempting to access a network location it doesn't provide any authentication so effectively connects as "anonymous".
CMS-XML DA615: DA Report hangs with large number of environments and other database objects
- HHH000443: Dialect [org.hibernate.dialect.Oracle10gDialect] limits the
CMS-XML DA: Getting ehcache errors about expired entries in the log file frequently
A soft-locked cache entry was expired by the underlying Ehcache. If this happens regularly you should consider increasing the cache timeouts and/or capacity limits .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs