| |
Results |
|
SRA 4.x / server installation : failed to start Tomcat => Failed to start Serena RA : C:\Program Files\Serena\ra401\conf\installed.version (The system cannot find the file specified)
|
The start of Tomcat fails with the following error message : 2013-02-08 11:29:19,953 - Failed to start Serena RA
|
|
|
|
SDA: How to configure tomcat to start a new logfile when the current log file becomes a certain size
|
By default, the Tomcat stdout and stderr utilize their own separate files. These are not managed by the log4j and thus it is not possible to set a maximum size on these files. It is possible to configure tomcat to "swallow" the output and direct it through the log4j software.
|
|
|
|
SRA: Upgrade will render SRA unusable if Tomcat is not stopped beforehand
|
Upgrading to Serena Release Automation 4.5.1 but forgot to stop the Common Tomcat service first, everything worked until a reboot took place, then service wouldn’t start: [2013-08-15 08:54:53] [info] Commons Daemon procrun (1.0.2.0) started [2013-08-15 08:54:53] [info] Running Service...
|
|
|
|
How to install two versions of Serena Common Tomcat on the same server
|
Verify that both services stop and start independently without impacting each other. NOTE: If Tomcat 6 will not start , see “ Tomcat 6 Service Fails to Start ” at the end of this document.
|
|
|
|
SDA: How to debug a plugin that is not loading
|
Clear logs Start tomcat Reproduced issue and ran a find (Windows) or grep (UNIX/Linux) command against the logs specifying the name of the plugin.
|
|
|
|
SDA/SRA: Reasons you cannot use redirected drives for the location path when installing Serena Deployment Automation
|
There are three main differences when you start Tomcat as a service or as a console application: Console application would have interactive user token which service application won’t have (if we are not talking about some custom service)
|
|
|
|
SRA: Installation: When installing Serena Release Automation with Oracle, what should the JDBC connection string look like?
|
Note: If the above is entered incorrectly, Tomcat will not start properly and will either provide a 404 error and/or the configuration page will appear again when attempting to login. Review of the Tomcat log files will provide further details. SRA will need to be uninstalled/reinstalled in order to correct.
|
|
|
|
SRA: Tomcat logs report Oracle constraint violation
|
Customer reports that they get the following in SRA 4.01 on Win2008R2 on Oracle 11.2.0.1.0 ************************************************************************ Serena RA Started
|
|
|
|
SRA: Failed to start Serena RA : java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ001, SQLERRMC: java.lang.NullPointerException^T^TXJ001.U
|
2013-11-19 10:22:33,075 - Waiting for Derby to start... 2013-11-19 10:22:34,117 - The Derby instance on localhost:11377 is started [null] Adding upgrade file for processing: /opt/serena/sra/common/ tomcat /6.0/temp/664693aa-fd1c-4266-893c-25952dc17f61/deploy/derby/upgrade_sql_4.4.xml
|
|
|
|
SRA5: Upgrade: Unable to deflate or expand serena_ra.war file after upgrading to SRA 5.0.1
|
SRA upgrade from 4.5.1 to 5.01 After upgrading and starting Tomcat , the serena_ra.war is not being unpacked. Tomcat reports
|
|
|
