Content Studio Thread Dumps

Occasionally, a situation can arise which causes Content Studio to freeze. If this situation arises, Content Studio will generate a thread dump as a diagnostic aid. If your users experience this kind of problem with Content Studio, you will probably be asked to submit one of these thread dump files to Escenic support.

By default, Content Studio checks the event dispatch thread every 15 seconds. If the event dispatch thread is busy twice in succession, then a thread dump file called Escenic-Content-Studio-thread-dump.log is generated. It is written to the location defined by the java.io.tmpdir system property (as defined on the machine where Content Studio is running).

You can change interval between checks by setting the property.com.escenic.studio.thread.dump.interval property in the configuration-layer-root/com/escenic/webstart/StudioConfig.properties configuration file. Specify the required interval in seconds (as an integer).

You can disable this process by setting property.com.escenic.studio.thread.dump.interval to -1.