-
1. Re: JBossWS 3.0.3 memory leak
asoldano Nov 7, 2008 7:52 AM (in response to marlboro)For sure more info would help, perhaps further details on the webservice endpoint(s), the contract and the full memory dump.
-
2. Re: JBossWS 3.0.3 memory leak
marlboro Nov 12, 2008 1:15 AM (in response to marlboro)Hi Alessio,
I'm sorry for the delay. The endpoints are part of web layer of our application. I will send you both wsdl files via email, and also I will send you link to the web page with JHat result because the memory dump is 1.17GB large. Do you need more data or these are sufficient?
Thanks,
Vratislav Kuzela -
3. Re: JBossWS 3.0.3 memory leak
manoj.kumar.jain Dec 15, 2008 8:17 AM (in response to marlboro)I am also facing the similar problem.
HashMapEntries are growing and those have reference to resourceblacklist of org.jboss.mx.loading.InifiedClassLoaderRepository3.
Further investigation shows it is trying to holding the Schema (.xsd) for WebService defination of type-
....../JbossWS_jaxb.dev.java.net_array10100 .xsd
Any help will be highly appriciated -
4. Re: JBossWS 3.0.3 memory leak
ropalka Dec 17, 2008 2:45 AM (in response to marlboro)Switch to JBoss AS 5.0.0.GA. This problem shouldn't be there.
-
5. Re: JBossWS 3.0.3 memory leak
marlboro Jan 15, 2009 8:48 AM (in response to marlboro)Now I'm trying to use 5.0.0 and I expect to have results next week.
I want to ask if there is any record in Jboss Jira which is refers to our problem?
Thank you! -
6. Re: JBossWS 3.0.3 memory leak
ecbdc Feb 11, 2009 2:11 PM (in response to marlboro)Hi Marlboro, were you able to resolve the issue by upgrading to JBoss 5.0?
I'm having a similar issue w/ the web services memory leak.
Thanks -
7. Re: JBossWS 3.0.3 memory leak
vdanda Mar 22, 2009 10:52 PM (in response to marlboro)I am having the same issue with 4.2.2 with WS 2.0.1 SP1.. I tried with JBoss 5.0.0 GA and I see many warning messages (EJBTHREE-1337, EJBTHREE-1246). Also looks threads are getting blocked when I run under the load. Is anyone able to find the solution or work arounds?
Thanks,
Venkat -
8. Re: JBossWS 3.0.3 memory leak
ropalka Mar 23, 2009 3:09 AM (in response to marlboro)And AS 5.0.1 GA + JBossWS 3.1.0?
-
9. Re: JBossWS 3.0.3 memory leak
sintetik7 May 27, 2009 9:17 AM (in response to marlboro)"richard.opalka@jboss.com" wrote:
And AS 5.0.1 GA + JBossWS 3.1.0?
I had similar problems wtih AS 5.0.1 GA (see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4233605). Found some kinda solution but not sure if good one. -
10. Re: JBossWS 3.0.3 memory leak
erili Aug 3, 2009 11:15 AM (in response to marlboro)Hello!
We are running into the same problem. The JVM runs out of memory and heap analysis shows huge HashSets containing entries like "JBossWS_..._20342.xsd". Following the path to GC root shows that resourceBlackList in the unified classloader holds references to these hashmaps.
We are running JBoss AS 4.2.2.GA with JBossWS 3.0.1-native-2.0.4.GA and cannot upgrade to JBoss AS 5, so more information on this problem would be greatly appreciated. -
11. Re: JBossWS 3.0.3 memory leak
erili Aug 5, 2009 10:59 AM (in response to marlboro)I found a poller method in our code that created new instances of WS client objects in the poller method. Even though these were not retained they apparently added data to the classloader's (unifiedclassloader3) resourceBlackList.
-
12. Re: JBossWS 3.0.3 memory leak
hedenberg Aug 17, 2010 2:52 AM (in response to marlboro)Im running Jboss 4.2.3 in a production environment and have this very same issue due to creating vast amounts of new JAXWS clients. I have a quite lock process to go through to upgrade the production environment, but I must do something to get rid of the restarts every 48hrs.
Is there any way to patch JBossWS in Jboss 4.2.3 or make a workarround to avoid this issue? The only one I can think of is a Pool of WS clients for my system, but that's no tiny fix that you just throw into a prod environment.
Anyone got any ideas or further info about this error?
-
13. Re: JBossWS 3.0.3 memory leak
bfp Oct 3, 2011 1:07 AM (in response to hedenberg)Hello,
I am experiencing a similar issue with JBoss 4.2.3 and JBossWS 3.1.0. By upgrading the JBossWS to 3.1.1 was fixing the leak but introduced a side effect with null pointer under load.
Does anyone has a proper recipe for those issues without the change of JBoss AS 4.2.3 ?
For more details please refer the below thread: http://community.jboss.org/thread/171831