Bug 1023444
Summary: | Domain fails to start with default memory settings on Windows 32bit JDK | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Tomaz Cerar <tcerar> |
Component: | Domain Management, Scripts and Commands | Assignee: | Tomaz Cerar <tcerar> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Kremensky <pkremens> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1.1 | CC: | anmiller, emuckenh, kkhan, smumford |
Target Milestone: | DR1 | ||
Target Release: | EAP 6.3.0 | ||
Hardware: | Unspecified | ||
OS: | Windows | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previous versions of JBoss EAP could fail to start when run in a Windows 32-bit JDK environment with the default memory settings.
In this release of the product, the default memory settings have been lowered to ensure a successful start on a wider array of JVMs.
Customers who rely on the default JVM settings are advised to review their configuration and adjust JVM parameters based on their requirements.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-28 15:41:31 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
Tomaz Cerar
2013-10-25 12:51:44 UTC
Andy WDYT we should do here? "problem" is that this would apply also to all other platforms not just windows. (In reply to Tomaz Cerar from comment #2) > Andy WDYT we should do here? > "problem" is that this would apply also to all other platforms not just > windows. I think its fine the way it is. Andy BZ 956281 is in ASSIGNED status now, it's resolved yet. Fix for Windows 8 which are not supported in EAP. BZ 956281 claims that we should improve EAP usage on Windows 8 with 32bit JVM for development. This BZ is about domain mode which is not used for development. It's used for deployment across large number of nodes + centralized node management. We shouldn't change default JVM values for this mode. Current status (EAP 6.2.0 ER6) for standalone mode: standalone mode - Windows ==> -Xms1G -Xmx1G standalone mode - Linux/Solaris/HP-UX ==> -Xms1303m -Xmx1303m Proposed status for domain mode: domain mode - Windows ==> <heap size="1000m" max-size="1000m"/> domain mode - Linux/Solaris/HP-UX ==> <heap size="1000m" max-size="1000m"/> this issue popped up again in forums https://community.jboss.org/message/846522 Verified on EAP 6.3.0.DR1 Standalone mode: standalone mode - Windows ==> -Xms1G -Xmx1G standalone mode - Linux/Solaris/HP-UX ==> -Xms1303m -Xmx1303m Domain mode: domain mode - Windows ==> <heap size="1000m" max-size="1000m"/> domain mode - Linux/Solaris/HP-UX ==> <heap size="1000m" max-size="1000m"/> |