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: Two ways to clear the DB cache in DA
a. Stop DA b. Go to the temp folder in Tomcat , for example C:\Program Files\Micro Focus\common\ tomcat \8.5\temp, and delete all the files c. Start DA
CMS-XML DA: Two methods to clear the DA DB cache to try and resolve performance issues in the GUI
2. The second method involves manually clearing the temp folder in Tomcat which requires Tomcat to be stopped: a. Stop Tomcat . b. Go to the temp folder in Tomcat, for example C:\Program Files\Micro Focus\common\tomcat\8.5\temp, and delete all the files.
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 Cache is not alive (STATUS_SHUTDOWN)
Seeing many errors in Ns log upon tomcat shutdown. ERROR 25-09-2017 12:14:45 [Notifications] -- While processing en escalation event with ID = 9632893
CMS-XML Dim CM Inefficient cache access
The threads block each other when updating or accessing the cache. By using an init() method in a servelet when connecting to the Tomcat server the cache access could be improved and the inter-blocking between the threads could be avoided.
CMS-XML Endpoints using NTLM authentication cache the password when used with SBM Proxy
To work around this issue, you must r edeploy the process app and r estart SBM Tomcat .
CMS-XML Tomcat memory usage is increasing steadily until it hits the Heap limit since upgrade to 11.3.1
To workaround the issue backup and modify the session-cache.xml located here ...SBM\Common\tomcat\server\default\conf\EhCacheConfig\ directory: < cache name="SessionInfoCache" maxElementsInMemory="5000" eternal="true" overflowToDisk="true" />
CMS-XML Serena VM Web Application Server should use Tomcat 7.0.75
The code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web- cache , perform an XSS attack and/or obtain sensitive information from requests other than their own.
CMS-XML Work Center fails to load when Common Services is included in a Tomcat cluster
3. Copy last two nodes: < cache name="MenuItemForSpecifiedModeCache" maxElementsInMemory="10000" eternal="true" overflowToDisk="false"/>
CMS-XML Is Version Manager 8.5.3 affected by CVEs that include Tomcat 7.0.57 as an affected release?
A bug in the error handling of the send file code for the NIO HTTP connector resulted in the current Processor object being added to the Processor cache multiple times. This in turn meant that the same Processor could be used for concurrent requests. Sharing a Processor can result in information leakage between requests including, not limited to, session ID and the response body.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs