[jbosstools-issues] [JBoss JIRA] (JBIDE-15107) JBoss EAP 6.1 Server cannot be started with 32-bit JVM on Windows 7

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-15107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker updated JBIDE-15107:
--------------------------------

    Workaround Description: 
Step 1: Double-click your server to open the server editor
Step 2: In the top-left of the editor page, look for a hyperlink labeled "Launch Configuration"
Step 3: Modify the arguments to lower your memory flags to your own desired targets, click apply. 
Step 4: Start your server normally

    
> JBoss EAP 6.1 Server cannot be started with 32-bit JVM on Windows 7
> -------------------------------------------------------------------
>
>                 Key: JBIDE-15107
>                 URL: https://issues.jboss.org/browse/JBIDE-15107
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.1.0.Beta2
>         Environment: 64-bit Windows 7
> 32-bit JDK 7u25
>            Reporter: Yahor Radtsevich
>            Assignee: Rob Stryker
>            Priority: Critical
>              Labels: jbds711
>             Fix For: 4.1.2.CR1, 4.2.0.Alpha2
>
>         Attachments: screenshot.png
>
>
> I cannot run JBoss EAP 6.1 with its default launch configuration.
> The default launch configuration has {{-Xms1303m}} and {{-Xmx1303m}} in its parameters, which is obviously the reason of this bug.
> *Steps to reproduce:*
> # Install JBDS 7.0.0.Beta2 bundled with JBoss EAP 6.1 Server
> # Open JBoss Central and create new HTML5 Project
> # Try to run this project on the server
> *Actual result:*
> Server cannot be started. The following message is shown in the console:
> {code:title=console output}
> Error occurred during initialization of VM
> Could not reserve enough space for object heap
> {code}
> And this pop-up appears:
> !screenshot.png!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira