[ http://jira.jboss.com/jira/browse/JBESB-1485?page=all ] Mark Little updated JBESB-1485: ------------------------------- Fix Version/s: 4.2.1 CP1 Assignee: Tom Fennelly (was: Mark Little) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1485?page=comments#action_12396312 ] Tom Fennelly commented on JBESB-1485: ------------------------------------- OK, had a look at this (using JProfiler) and it looks as though the PermGen issue is being caused by soapUI when it's processing the WSDL from the target endpoint. It's a one time hit which obviously causes the Perm Generation space to fill up. When soapUI is loading the wsdl it seems to load a gazzilion other classes. The main culprits are XMLBeans model types for processing SOAP messages... a load of AWT classes (that we don't even need). All told, it looks to cause the heap size to jump by about 7M (lol) and the 2 guys listed above account for ~ 90% of that. I increased the PermGen space to 128M (-XX:MaxPermSize=128m) and it seems to work away fine in that after it gets over that initial hurdle on the initial request the heap seems to be stable enough over multiple requests i.e. I don't think there's an actual leak there, but a soak test should confirm this. So we can... 1. Document "-XX:MaxPermSize=128m" as a solution for now. 2. Try move stuff about a bit in order to make initializations happen in a different order such that there's enough PermGen space available when the Service initalises (and calls soapUI to initalise etc). I'd guess this is a real long shot!! 3. Look at getting into the guts of soaopUI and pulling out only the bits we need from it i.e. try to eliminate at least the AWT aspects which caused ~ 40% of that 7M jump in heap size. This could be a deep hole!! I'd vote for #1 for now, but we def need to look at soapUI as a solution and how we're using it. I think it still has value as an option, but we can't use it as is - it's really a UI app ("soapUI") and we're using it embedded in a way in which it was never intended to be used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1485?page=all ] Mark Little updated JBESB-1485: ------------------------------- Fix Version/s: 4.3 (was: 4.2.1 CP1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1485?page=comments#action_12396359 ] Tom Fennelly commented on JBESB-1485: ------------------------------------- Sorry, I should have also said... I'd be going for the documented fix at this stage. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1485?page=all ] Kevin Conner updated JBESB-1485: -------------------------------- Fix Version/s: 4.4 (was: 4.3) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-1485?page=com.atlassian.jira.plu... ] Tom Fennelly closed JBESB-1485. ------------------------------- Resolution: Out of Date This QS was removed some time ago. -- 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