[JBoss JIRA] Created: (JBIDE-5838) Default launch configuration for EAP 5.0 and SOA-P 5.0 should have max heap -Xmx value increased to 768m
6:07 a.m.
Default launch configuration for EAP 5.0 and SOA-P 5.0 should have max heap -Xmx value
increased to 768m
--------------------------------------------------------------------------------------------------------
Key: JBIDE-5838
URL: https://jira.jboss.org/jira/browse/JBIDE-5838
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Default launch configuration for EAP 5.0 and SOA-P 5.0 have max heap -Xmx value set to
512m. This is too low, both platforms run.conf defaults to 768MB. Couple of redeployments
on those platforms results in OOMEs or eccessive GB overhead. The -Xmx value should be
changed to 768MB.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:58 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5838) Default launch configuration for EAP 5.0 and SOA-P 5.0 should have max heap -Xmx value increased to 768m
[
https://jira.jboss.org/jira/browse/JBIDE-5838?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-5838:
---------------------------------------
Fix Version/s: 3.1.0.CR2
Assignee: Rob Stryker
Default launch configuration for EAP 5.0 and SOA-P 5.0 should have
max heap -Xmx value increased to 768m
--------------------------------------------------------------------------------------------------------
Key: JBIDE-5838
URL: https://jira.jboss.org/jira/browse/JBIDE-5838
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.1.0.CR2
Default launch configuration for EAP 5.0 and SOA-P 5.0 have max heap -Xmx value set to
512m. This is too low, both platforms run.conf defaults to 768MB. Couple of redeployments
on those platforms results in OOMEs or eccessive GB overhead. The -Xmx value should be
changed to 768MB.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-5838) Default launch configuration for EAP 5.0 and SOA-P 5.0 should have max heap -Xmx value increased to 768m
[
https://jira.jboss.org/jira/browse/JBIDE-5838?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen reassigned JBIDE-5838:
------------------------------------------
Assignee: Max Rydahl Andersen (was: Rob Stryker)
Default launch configuration for EAP 5.0 and SOA-P 5.0 should have
max heap -Xmx value increased to 768m
--------------------------------------------------------------------------------------------------------
Key: JBIDE-5838
URL: https://jira.jboss.org/jira/browse/JBIDE-5838
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Max Rydahl Andersen
Fix For: 3.1.0.CR2
Default launch configuration for EAP 5.0 and SOA-P 5.0 have max heap -Xmx value set to
512m. This is too low, both platforms run.conf defaults to 768MB. Couple of redeployments
on those platforms results in OOMEs or eccessive GB overhead. The -Xmx value should be
changed to 768MB.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:33 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-5838) Default launch configuration for EAP 5.0 and SOA-P 5.0 should have max heap -Xmx value increased to 768m
[
https://jira.jboss.org/jira/browse/JBIDE-5838?page=com.atlassian.jira.plu...
]
Snjezana Peco resolved JBIDE-5838.
----------------------------------
Resolution: Done
Fixed in CR2 and trunk.
Default launch configuration for EAP 5.0 and SOA-P 5.0 should have
max heap -Xmx value increased to 768m
--------------------------------------------------------------------------------------------------------
Key: JBIDE-5838
URL: https://jira.jboss.org/jira/browse/JBIDE-5838
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Max Rydahl Andersen
Fix For: 3.1.0.CR2
Default launch configuration for EAP 5.0 and SOA-P 5.0 have max heap -Xmx value set to
512m. This is too low, both platforms run.conf defaults to 768MB. Couple of redeployments
on those platforms results in OOMEs or eccessive GB overhead. The -Xmx value should be
changed to 768MB.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:28 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5838) Default launch configuration for EAP 5.0 and SOA-P 5.0 should have max heap -Xmx value increased to 768m
[
https://jira.jboss.org/jira/browse/JBIDE-5838?page=com.atlassian.jira.plu...
]
Dominik Pospisil commented on JBIDE-5838:
-----------------------------------------
Some discussion about EAP memmory setting is here:
https://jira.jboss.org/jira/browse/JBPAPP-2052
The reason why EAP is shipping with -Xms1303m -Xmx1303m is to get as much memmory as
possible without causing problems on most systems. So this might not be necessarily
optimum for JBDS. Will do couple of tests with 768MB to see if it is sufficient.
Default launch configuration for EAP 5.0 and SOA-P 5.0 should have
max heap -Xmx value increased to 768m
--------------------------------------------------------------------------------------------------------
Key: JBIDE-5838
URL: https://jira.jboss.org/jira/browse/JBIDE-5838
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Max Rydahl Andersen
Fix For: 3.1.0.CR2
Default launch configuration for EAP 5.0 and SOA-P 5.0 have max heap -Xmx value set to
512m. This is too low, both platforms run.conf defaults to 768MB. Couple of redeployments
on those platforms results in OOMEs or eccessive GB overhead. The -Xmx value should be
changed to 768MB.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:34 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5838) Default launch configuration for EAP 5.0 and SOA-P 5.0 should have max heap -Xmx value increased to 768m
[
https://jira.jboss.org/jira/browse/JBIDE-5838?page=com.atlassian.jira.plu...
]
Dominik Pospisil commented on JBIDE-5838:
-----------------------------------------
SOA-P 5.0 will have synced memory setting with EAP in GA.
Default launch configuration for EAP 5.0 and SOA-P 5.0 should have
max heap -Xmx value increased to 768m
--------------------------------------------------------------------------------------------------------
Key: JBIDE-5838
URL: https://jira.jboss.org/jira/browse/JBIDE-5838
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Max Rydahl Andersen
Fix For: 3.1.0.CR2
Default launch configuration for EAP 5.0 and SOA-P 5.0 have max heap -Xmx value set to
512m. This is too low, both platforms run.conf defaults to 768MB. Couple of redeployments
on those platforms results in OOMEs or eccessive GB overhead. The -Xmx value should be
changed to 768MB.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:54 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5838) Default launch configuration for EAP 5.0 and SOA-P 5.0 should have max heap -Xmx value increased to 768m
[
https://jira.jboss.org/jira/browse/JBIDE-5838?page=com.atlassian.jira.plu...
]
Dominik Pospisil commented on JBIDE-5838:
-----------------------------------------
I did some basics profiling of SOA-P and EAP with the following results:
- when EAP 5.0 default profile is started and full GC is performed, it occupies ~ 280MB on
heap
- when SOA-P 5.0 default profile is started and full GC is performed, it occupies ~ 480MB
on heap
Also, I did some testing with seam dvdstore and booking examples and I would say that for
devel purposes:
For EAP 5.0, 512mb max heap size is sufficient.
For SOA-P 5.0, 512mb is NOT sufficient, but 768 is.
Default launch configuration for EAP 5.0 and SOA-P 5.0 should have
max heap -Xmx value increased to 768m
--------------------------------------------------------------------------------------------------------
Key: JBIDE-5838
URL: https://jira.jboss.org/jira/browse/JBIDE-5838
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Max Rydahl Andersen
Fix For: 3.1.0.CR2
Default launch configuration for EAP 5.0 and SOA-P 5.0 have max heap -Xmx value set to
512m. This is too low, both platforms run.conf defaults to 768MB. Couple of redeployments
on those platforms results in OOMEs or eccessive GB overhead. The -Xmx value should be
changed to 768MB.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:28 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5838) Default launch configuration for EAP 5.0 and SOA-P 5.0 should have max heap -Xmx value increased to 768m
[
https://jira.jboss.org/jira/browse/JBIDE-5838?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-5838:
--------------------------------------------
Ok, for now the tools doesn't differentiate between EAP and SOA-P so using 768MB as
the *max* should work for both, i.e. the min is still the same so EAP 5 should'nt be
using that space anyway.
Default launch configuration for EAP 5.0 and SOA-P 5.0 should have
max heap -Xmx value increased to 768m
--------------------------------------------------------------------------------------------------------
Key: JBIDE-5838
URL: https://jira.jboss.org/jira/browse/JBIDE-5838
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Max Rydahl Andersen
Fix For: 3.1.0.CR2
Default launch configuration for EAP 5.0 and SOA-P 5.0 have max heap -Xmx value set to
512m. This is too low, both platforms run.conf defaults to 768MB. Couple of redeployments
on those platforms results in OOMEs or eccessive GB overhead. The -Xmx value should be
changed to 768MB.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:38 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-5838) Default launch configuration for EAP 5.0 and SOA-P 5.0 should have max heap -Xmx value increased to 768m
[
https://jira.jboss.org/jira/browse/JBIDE-5838?page=com.atlassian.jira.plu...
]
Dominik Pospisil closed JBIDE-5838.
-----------------------------------
Verified on jbdevstudio-linux-gtk-x86_64-3.0.0.v201002190026M-H172-CR2.jar
Default launch configuration for EAP 5.0 and SOA-P 5.0 should have
max heap -Xmx value increased to 768m
--------------------------------------------------------------------------------------------------------
Key: JBIDE-5838
URL: https://jira.jboss.org/jira/browse/JBIDE-5838
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Max Rydahl Andersen
Fix For: 3.1.0.CR2
Default launch configuration for EAP 5.0 and SOA-P 5.0 have max heap -Xmx value set to
512m. This is too low, both platforms run.conf defaults to 768MB. Couple of redeployments
on those platforms results in OOMEs or eccessive GB overhead. The -Xmx value should be
changed to 768MB.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5909
days inactive
5916
days old
jbosstools-issues@lists.jboss.org
8 comments
3 participants
participants (3)
-
Dominik Pospisil (JIRA) -
Max Rydahl Andersen (JIRA)
-
Snjezana Peco (JIRA)