-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
None
-
Affects Version/s: 7.3.2
-
Component/s: Data Center - Other
-
7.03
-
7
-
Severity 1 - Critical
-
1
Summary
When customer tried to deploy JIRA using AWS Cloudformation template for JIRA datacenter he was not able to provide custom options to JIRA through the CatalinaOpts template parameter.
Environment
- AWS Cloudformation deployment
Steps to Reproduce
- follow the steps in the JIRA datacenter quick start reference
- When providing the template parameters, try to pass any Java or tomcat options like:
CatalinaOpts -Xmx4096m
Expected Results
JIRA process should pick up the options and use them
Actual Results
JIRA just uses its default configuration and no changes happen to the process.
Even editing the parameter default value in the AWS cloudformation template doesn't work.
Workaround
- Modify the option manually after the JIRA data center is deployed using a script.
- Modify the Atlassian AWS template to change the values in JIRA setenv.sh.
- duplicates
-
JRASERVER-64227 JIRA Software Data Center CloudFormation template does not respect CATALINA_OPTS variable on creation
-
- Closed
-