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 Changing Threshold for Long Running Reports Recorded by Active Diagnostics
Beginning with SBM 11.1, SBM Active Diagnostics now logs any report that takes longer than 20 seconds to complete. If you need to lower this threshold to capture reports that are taking less than 20 seconds, refer to the details below.
CMS-XML Concurrent licenses are not released as expected with Active Diagnostics set to Trace
Concurrent licenses are not released as expected with Active Diagnostics set to Trace
CMS-XML Stability or performance issues can occur when the User Interface logging in Active Diagnostics is set
Please set the Active Diagnostics setting for User Interface to none.
CMS-XML Empty logs in active diagnostics does not seem to empty them
Active diagnostics "empty logs" function is leaving huge files still there and does not seem to be emptying the logs. Currently Configurator reduces the size of the database files when changing the log size limit on Active Diagnostics UI. However, there is an issue , if the log size limit is changed , the size is reduced for previous limit value and not current value.
CMS-XML Common Services Host for Active Diagnostics and Relationship Service Is Not Updated Properly in Cluster
To work around this problem, edit the Active Diagnostics and Relationship Service tabs and select the re-named Common Services host from the drop-down list.
CMS-XML Active Diagnostics not starting correctly can lead to system unavailability - INFO message with ajp thread name and 'Cluster description not yet available. Waiting for 10000 ms before timing out'
"C:\Program Files\Micro Focus\SBM\Common\tomcat\server\default\conf\log4j.xml find ActiveDiagnostic appender and change logBufferSize value from 1 to 200
CMS-XML SBM: Active Diagnostics MongoDB is using too much disk space, and the "Collect Logs" zip file is too large
You can check this box and give it a size (for example 15Mb). This will limit the log to the size specified. If you check this box, be sure to click "Apply Runtime Configuration" to save the change , and click "Empty Logs" to delete the already existing logs.
CMS-XML It looks like you are trying to access MongoDB over HTTP on the native driver port.
"It looks like you are trying to access MongoDB over HTTP on the native driver port." When you see this error message, it means that in Configurator the TCP port for Active Diagnostics has been changed to port 80.
CMS-XML Deploy waiting on Application Engine and does not complete and the gsoap IIS application pool keeps unloading and restarts
(1) Check the Application Windows Event Log and see if the web services is unloading regularly (2) Is the active diagnostics level set to Trace? (3) Check the gsoap_pool setting in IIS - is a private memory limit set?
CMS-XML "log4javascript error: Logger.setLevel: level supplied to logger classic is not an instance of log4javascript.Level" error
An error of "log4javascript error: Logger.setLevel: level supplied to logger classic is not an instance of log4javascript.Level" when logging into the SBM user workspace can be caused by the Active Diagnostics being set to filter by a user ID. To work around the issue, do not filter Active Diagnostics by a user ID.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs