Please add -Dfile.encoding=UTF-8 to JVM startup parameters if the default encoding is different than UTF-8. It is recommended to use UTF-8 encoding in the Jira configuration. Please read more about the Child process option if you would like to enable it. It is possible to run eazyBI report queries in a separate JVM process. Please either remove the -Xss option or increase it (the recommended setting is -Xss1024k) until eazyBI starts without the “stack level too deep” error. You can see if this -Xss option is used in Jira Administration / System / Troubleshooting & Support / System Info / JVM Input Arguments. If eazyBI startup fails and you get SystemStackError: stack level too deep errors in localhost.*.log file (please see Troubleshooting for file location) then you have specified too low -Xss max stack size setting for Java VM.
Later while using eazyBI check Jira Administration / System / Troubleshooting & Support / System Info / Java VM Memory Statistics page to see how much available memory is used and if it is necessary to increase it more. Specify JVM_MAXIMUM_MEMORY=2048m in your setenv.sh or setenv.bat file (if you run Jira as a Windows service then please follow Increasing Jira Memory / Windows service instructions instead).
#Node jira client retry how to
See Increasing Jira Memory for detailed instructions on how to do it in your Jira installation. To ensure better performance of eazyBI it is recommended to set Jira Java VM available memory to 2 GB or more. If your Jira server will not have enough available memory then eazyBI might fail to start as well as overall Jira performance could be affected. Please review your current Jira memory settings before installing eazyBI.
0 kommentar(er)
