Bug 998913
Summary: | standalone.bat still sets -XX:+TieredCompilation JVM option | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jaikiran Pai <jpai> |
Component: | Scripts and Commands | Assignee: | David M. Lloyd <david.lloyd> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Kremensky <pkremens> |
Severity: | high | Docs Contact: | Russell Dickenson <rdickens> |
Priority: | unspecified | ||
Version: | 6.1.0 | CC: | aogburn, carlo.marchiori, cdewolf, dimitris, fnasser, jawilson, jdoyle, myarboro, pgier, pslavice, rsvoboda |
Target Milestone: | ER1 | ||
Target Release: | EAP 6.2.0 | ||
Hardware: | Unspecified | ||
OS: | Windows | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
An issue has been resolved in the `standalone.bat` batch file, used on Microsoft Windows Server. The batch file previously contained a JVM option which set tiered compilation: `-XX:+TieredCompilation`. This setting has been removed as it is known to cause performance problems in some circumstances.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-15 16:16:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jaikiran Pai
2013-08-20 10:45:16 UTC
Per http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8008938, some JDK releases may even have tiered compilation enabled by default. We don't want a JDK default setting to lead to those performance issues either so setting -XX:-TieredCompilation instead in the .bat and .sh scripts to override any potential JDK level defaults may be the best option. Verified on 6.2.0.ER1 Assigning jpai EJB issues to david.lloyd. Please re-assign to Cheng or others as needed. Release notes text added, to be published in the JBoss EAP 6.2.0 Release Notes document. I think this problem should be reported to Oracle, because it's a serious bug of their JVM. (In reply to Carlo Marchiori from comment #16) > I think this problem should be reported to Oracle, because it's a serious > bug of their JVM. Already was. http://bugs.java.com/view_bug.do?bug_id=7159766 |