[JRASERVER-39580] no need for MaxPermSize when running under Java 8

Type: Bug
Resolution: Fixed
Priority: Low (View bug fix roadmap)
Fix Version/s: 6.5-OD-05
Affects Version/s: 6.3.3
Component/s: Infrastructure & Services - Application Lifecycle
Labels:

Introduced in Version:
6.03
Bug Fix Policy:
View Atlassian Server bug fix policy

MaxPermSize parameter in setenv.sh is obsolete since 6.3.3 ships with JRE 1.8.0_11.

Stopping JIRA (I assume that's true for starting JIRA, too) shows the following message on console:
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=384m; support was removed in 8.0

duplicates

JRASERVER-39621 Remove MaxPermSize JVM argument since Java 8 no longer supports it

Closed

causes: LEGO-1064 Failed to load

Form Name

whereisaaron added a comment - 11/Apr/2015 3:18 AM

Persists in JIRA 6.4.1

whereisaaron added a comment - 11/Apr/2015 3:18 AM Persists in JIRA 6.4.1

D3 Software added a comment - 06/Mar/2015 6:51 PM

So, what is the fix?

D3 Software added a comment - 06/Mar/2015 6:51 PM So, what is the fix?

Assignee:: Semps

Reporter:: Simon Westhues

Affected customers:: 3 This affects my team

Watchers:: 9 Start watching this issue

Created:: 18/Aug/2014 3:04 PM

Updated:: 28/Mar/2019 12:14 AM

Resolved:: 03/Jun/2015 12:08 PM

Details

Description

Attachments

Issue Links

Forms

Activity

Collapse comment: whereisaaron added a comment - 11/Apr/2015 3:18 AM

Expand comment: whereisaaron added a comment - 11/Apr/2015 3:18 AM

Collapse comment: D3 Software added a comment - 06/Mar/2015 6:51 PM

Expand comment: D3 Software added a comment - 06/Mar/2015 6:51 PM

People

Dates