[ https://jira.jboss.org/jira/browse/JBIDE-6202?page=com.atlassian.jira.plu... ] Max Rydahl Andersen resolved JBIDE-6202. ---------------------------------------- Resolution: Done Great that is solved/worked-around in the product runtime! About what we should fix it would be better to somehow support run.conf than doing our own custom hack based on jar info (which would be much more fragile) in that case it would simply be better to have separate launch configs to make it explicit. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6202?page=com.atlassian.jira.plu... ] Dominik Pospisil commented on JBIDE-6202: ----------------------------------------- Verified on EPP CR1 build. However, there is another problem. EPP 5.0 is extremelly memory hungry. My basic profiling shows than after start and full GC performed listed runtimes occupies following heap sizes: EAP 5.0 ~ 280 MB SOA-P 5.0 ~ 480 MB EPP 5.0.CR1 ~ 570 MB ! Currently, we have max heap size for EAP-5 based runtimes set to 768MB. With EPP 5.0.CR1, this setting is on the limit, runtime is slowed down due to excessive GC. According to portal QA, this is known issue and should be fixed. Will look at it later. -- 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