User Guides for CCMS Desktop for v5.0 in DRM Mode for Advanced Users

CCMS Desktop User Guide
CCMS Desktop Dynamic Release Management User Guide
User FAQs
Notices

Home
User FAQs
DITA CMS performance troubleshooting

User FAQs
- DITA CMS troubleshooting
- DITA CMS performance troubleshooting
  - How do I delete a workspace?
    The workspace can be deleted by deleting the workspace folder; however, before deleting it you should release all the topics locked by you and possibly export your preferences from the existing workspace.
  - Why is my Eclipse workspace unstable and how can I fix it?
    The Eclipse workspace may become unstable over time and must be cleaned or replaced.
  - How can I improve DITA CMS performance?
    You can perform some troubleshooting to improve the performance of DITA CMS.
  - Why does a .metadata error appear when trying to launch the DITA CMS Eclipse Client?
    This can be resolved by removing some corrupted Eclipse files.
  - Why am I seeing an "JVM terminated. Exit code = -1" error when I try to start EclipseEclipse and how can I fix it?
    Eclipse cannot get a continuous block of memory of the size specified by the -Xmx value, which prevents the DITA CMS from opening.
  - How can I prevent Java heap space errors when performing large client actions like publishing, localizing, and DRM cloning?
    You can increase the amount of memory allocated to DITA CMS.
  - How do I get a log file for debugging the DITA CMS?
    You need to launch the DITA CMS in debugging mode so you can obtain the log files. Once you start the DITA CMS in debugging mode, a log file called DITA_CMS.log will be created in your workspace folder.
- Editing topics troubleshooting
- Citrix troubleshooting
- Localization troubleshooting
- Dynamic Release Management troubleshooting

DITA CMS performance troubleshooting

This section contains FAQs for troubleshooting DITA CMS performance issues.

Generated by IXIASOFT CCMS oXygen Webhelp