close

Filter

loading table of contents...

Site Manager Developer Manual / Version 2310

Table Of Contents

3.12.1 Taking a Thread Dump

When the Site Manager does not respond, or is performing poorly, you can take a thread dump to identify the problem or attach it as a file to a support ticket.

There are three options to take a thread dump depending on how the Site Manager was started and what version of Java you are running.

  • Point your web browser to the URL: http://localhost:<port>/coremedia/threaddump (the default port is 44444). This generates a thread dump in the browser window. You can copy and paste it into an email for example. Additionally, the thread dump is written to a file in your user home directory. The filename matches the pattern threaddump.editor.<timestamp>. This file can be attached to a support ticket to help determine the cause of the problem. For this option the minimum required Java version is JRE 5.0 and the remote control of the Site Manager must be enabled but it is independent of how the editor was started.

  • When you started the Site Manager via bin/cm editor in the bin directory of the CoreMedia installation, you can also take a thread dump by pressing Ctrl-Break (Windows) or Ctrl-\ (Unix, Linux, Mac OS X) in the console you used to start the editor. A thread dump will be generated in the console.

  • When you started the CoreMedia Site Manager via the web browser using Java Web Start and the Java Console window is enabled, (on Windows, this can be done by going to the Windows Control Panel, and double-clicking the Java icon, then enabling the Java Console on the Advanced Tab) you can press 'v' in the Java Console window. A thread dump will be generated in the console. For this option the minimum required Java version is JRE 6.0.

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.