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 KM-Dim10: How to update the embedded Tomcat JRE's for DST 2007 compatibility
- If updating a machine with a later java plugin version than the embedded JRE be sure not to accept the JRE installer options to install plugins to your browsers. After updating the JRE delete the Tomcat work directory and restart. Test Adminconsole and Web Client access from another machine in case you inadvertently replace your existing plugins.
CMS-XML KM-Dim9: java.lang out of memory when running tomcat as a service
If you are running the Dimensions webtools as a service, any options set in the catalina.bat and catalina.sh files are not picked up.
CMS-XML MCLG: Solaris: Tomcat log says "Could not load mediaLib accelerator wrapper classes. continuing in pure java mode"
To make them available, add the directory to the LD_LIBRARY_PATH setting in the options .sh file. On the line that sets LD_LIBRARY_PATH and looks something like this :
CMS-XML Monitor your tomcat Java memory and CPU usage
Monitor your tomcat Java memory and CPU usage
CMS-XML Dim: Tomcat: How to determine the version of Tomcat and Java being used
To do this, here's what you will need to do: 1. Log onto the Dimensions CM Server where Tomcat resides. 2. Then open a command prompt and browse to the Tomcat lib directory.
CMS-XML How to setup and use Java VisualVM to troubleshoot, take snapshots and monitor SBM Tomcat nodes
1. Connecting JVVM to Tomcat requires opening up the JMX Console on the target Tomcat node(s). Doing so is a significant security risk; an unrestricted JMX console introduces vulnerabilities by allowing unauthenticated commands against the node.
CMS-XML VM I-Net server shows Java stackdump errors from Tomcat after upgrading to a newer release
The Serena VM Web Application Server is running as a service. When all these are true, the compiled JSP code that is located in vm\common\ tomcat \work will continue to be that of the previous version, which can result in unpredictable errors due to the incompatibility with the newer JSP pages that were just installed. An example of an error cause by this problem:
CMS-XML Dim 10: What Java version can be used by Tomcat ?
Dimensions 10.1.3 web tools were tested on Tomcat running on Java 1.4.2 as supplied by Serena. They have not been tested fully on other Java versions.
CMS-XML Intermittent Deadlock in SSM with Java caches - [error] ajp_service::jk_ajp_common.c (2799): (worker2) connecting to tomcat failed (rc=0, errors=1597, client_errors=26)
[Tue Nov 14 09:17:13.553 2017] [3748:3300] [error] ajp_service::jk_ajp_common.c (2799): (worker2) connecting to tomcat failed (rc=0, errors=1597, client_errors=26).
CMS-XML Is the Apache Tomcat Java Application Server that is included with Version Manager vulnerable to OpenSSL defects?
Apache Tomcat only uses OpenSSL in the optional Apache Tomcat Native Library, which was purposefully not included with the Tomcat server that Version Manager ships with. The server is therefore not affected by OpenSSL related issues.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs