| |
Results |
|
SBM: Tomcat services take a lot of time to start (Slow performance during Tomcat startup)
|
to {SBM Dir}\Common\ tomcat \server\default\webapps\commonsvc\payload when it doesn't have to. While it's important to have the SLS information in the database, this copying action should occur only with a new database, and not when the database has already been initialized.
|
|
|
|
Dim14.2: Tomcat: Serena Common Tomcat is slow to start
|
To apply the file, 1. Stop the Serena Common Tomcat Service.
|
|
|
|
JBoss / Tomcat cluster setup is slow if one node is offline
|
Ideally, every recover_time (5 min) at least one user will suffer the hit testing the downed server. If it is still down, node will be marked in error state and other users will avoid it. Due to other bug in mod_jk, after the first 5 min, it will check once per minute (“maintain” time) thereafter (for at least one user).
|
|
|
|
Use of "vtransfer -r" puts java.io.IOException in the tomcat.log file if the target directory did not exist
|
Starting with VM 8.1.4, the File Server and the vtransfer -r ... Unfortunately, if the target directory did not exist, a scary looking message was added in the tomcat .log, even though the command itself completed successfully (albeit in the slowed server > client > server mode). ... at org.apache. tomcat .util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:309) ... at org.apache. tomcat .util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:309)
|
|
|
|
In FileServer, the logs are directed to tomcat.log by default instead of pvcsfs.log
|
If you have grown accustomed to getting detailed logging in tomcat .log, ... to greater detail ( slows performance) ... Older VM releases can perform the following workaround after starting /restarting the File Sever to log to the correct file:
|
|
|
|
Dim2009R2/12: Tomcat does not start on AIX
|
Tomcat will start and immediately shutdown, the logs/catalina.out reports
|
|
|
|
9.1.3 : unable to start Tomcat, always get "java.net.BindException: Address already in use:xxxx"
|
9.1.3 : unable to start Tomcat , always get "java.net.BindException: Address already in use:xxxx"
|
|
|
|
12.x : don't find startup.sh procedure to start Tomcat after installing Dimensions server on unix
|
12.x : don't find startup.sh procedure to start Tomcat after installing Dimensions server on unix
|
|
|
|
Tomcat components fail to start after it's upgraded from 8.5 version.
|
A number of customers have upgraded Tomcat 8.5 that comes with Dimensions CM to newer 8.5.x versions in order to resolve some vulnerabilities. However, after Tomcat is upgraded some of the Connectors fail to start up. Tomcat logs include the following errors:
|
|
|
|
Dim14: Tomcat: AIX 7: When starting Tomcat, an error of "Error: Port Library failed to initialize: -125" is received
|
Dim14: Tomcat : AIX 7: When starting Tomcat , an error of "Error: Port Library failed to initialize: -125" is received
|
|
|
