TechSupport

To analyse problem we are need following information

javamelody monitoring is included in version 4 and available at http://wfserver:8080/wfe/monitoring. In version 3 you can turn it on (by instruction).

# In case of performance problems

1. System info

• Server specification (CPU, RAM)
• Operation system type and version
• Database information
• JVM version

2. JVM settings (from run.bat/run.sh) (JVM settings)

It is useful to gain garbage collector log.

3. Saved javamelody report may be useful

4. JVM memory dump (How to get JVM dumps)

5. JVM stack dump (How to get JVM dumps)

6. Server logs

# In case of process errors

1. System info

• Server specification (CPU, RAM)
• Operation system type and version
• Database information

2. Server logs

3. Minimal process to reproduce problem

If process requires additional setup, please, describe it.

Note ^4.0.6+. You can use support feature in "System" menu from web interface.

# In case of process designer problems

1. System info

• Operation system type and version
• JVM version

2. Log file (workspace/.metadata/.log)

3. Process definition if problem is specific to it

# In case of process designer form editor problems

4. Try to get JavaScript error. For this in IE (in other OS default browser) settings set options:

• Disable script debugging (Internet Explorer) = no.
• Disable script debugging (other) = no.
• Show JavaScript errors = yes.

5. Check that the same error exists in CKeditor (can be switched from application settings)

6. Try to open page http://localhost:48780/fckeditor.html in different browsers when form is open. If some strange behaviour would occurs - describe it.