Hi, I upgraded from Jira Core server 7.1.7 to 8.22. Since the upgrade, any attempt to open a project under the Projects menu results in a completely greyed out screen.
The first issue in the list loads, but the entire screen (apart from the top and left navs) is greyed-out. Loading issues through the Issues / Search screen works fine.
This javascript error is triggered from batch.js:
Uncaught TypeError: Cannot set properties of undefined (setting 'bootstrap')
at D.n.initialize (batch.js?baseurl-check-resources=true&healthcheck-resources=true&jira.create.linked.issue=true&locale=en-US&richediton=true:41042:2535)
at e.View (batch.js?locale=en-US:740:14114)
at D.n [as constructor] (batch.js?locale=en-US:740:23495)
at new D.n (batch.js?locale=en-US:740:23495)
at eval (eval at globalEval (batch.js?locale=en-US:158:1085), <anonymous>:8:34)
at eval (eval at globalEval (batch.js?locale=en-US:158:1085), <anonymous>:14:6)
at eval (<anonymous>)
at Function.globalEval (batch.js?locale=en-US:158:1085)
at ye (batch.js?locale=en-US:184:1380)
at u.fn.init.append (batch.js?locale=en-US:189:1099)
Does anybody know how to work around this or what the cause could be? It's my first time posting here so let me know if further info is required.
Thank you,
Pascal.
I wouldn't do this. Atlassian's standard recommendation is to run their applications in separate Tomcat installations.
If you look at the way Tomcat runs, you'll generally find that it is using a tiny fraction of the resources that are in use for Stash or Jira. The resource saving of running them both in one Tomcat is so small, you probably won't even be able to detect it. But you'll quickly notice the slower threading, issues with class paths, the annoyance that you can't analyse their running separately, the need to stop both just to change something on one of them, and, and, and...
Keep them separate, it's well worth it.
OK, but how can I limit Tomcat's memory usage? 2,5 GB for two applications is too much. I only have 2,5 GB available so the server is slow because of all the swapping :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Set the upper limits on the processes using the -Xmx flags in setenv.sh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.