12:54 p.m.
[ http://jira.jboss.com/jira/browse/JBAS-2299?page=comments#action_12344128 ]
Clebert Suconic commented on JBAS-2299:
---------------------------------------
Common-BeanUtils is broken:
org.jboss.web.tomcat.tc5.WebAppClassLoader@6455597
!--- class org.apache.struts.action.ActionServlet
!--- !--- [Ljava.lang.Class;@15889588
!--- !--- !--- java.lang.reflect.Method@2653351
!--- !--- !--- !--- [Ljava.lang.reflect.Method;@14422877
!--- !--- !--- !--- !--- java.util.Hashtable$Entry@23818829
!--- !--- !--- !--- !--- !--- [Ljava.util.Hashtable$Entry;@18693832
!--- !--- !--- !--- !--- !--- !--- java.util.Hashtable@17102985
!---!---!---!---!---!---!---!--- StaticFieldReference private static java.util.Hashtable
org.apache.commons.beanutils.MappedPropertyDescriptor.declaredMethodCache Detail
There is a list of declaredMethods (Reflection) being referenced inside of
MappedPropertyDescriptor.
BeanUtils is now being bundled with JBoss/JSF at this point.
If you want to avoid this bug for this specific application, having BeanUtils deployed
within the application + classLoader isolations will make BeanUtils to keep circular
references inside the classLoader what would avoid the contention.
We should look for a way to contribute a fix for apache.
Besides this reflection cache, it looks also they have a circular reference on their
WeakHashMap, having the classLoader on the value. (but I'm not sure about that one).
But I know for sure BeanUtils is broken.
Dimitris, since this is a Beanutils bug, what should we do here? Close, postpone? It's
your call now.
OutOfMemory error when repetatively deploying and undeploying with 10
minute interval
-------------------------------------------------------------------------------------
Key: JBAS-2299
URL: http://jira.jboss.com/jira/browse/JBAS-2299
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Deployment services
Affects Versions: JBossAS-4.0.3RC2
Environment: WinXP SP2, JBoss 4.0.3RC2, JDK 1.4.2_07
Reporter: Amar Syed
Assigned To: Clebert Suconic
Fix For: JBossAS-4.0.5.GA
Attachments: Data.txt, SampleApp.ear
Using a manual copy and delete mechanism with the server\default\deploy folder the sample
ear (attached) caused an outofmemory error eventually after 90 repetitions.
The min and max heap settings were configured as : -Xms128m -Xmx512m
The time delay after dropping/deploying the ear at each repetition was set to 10 minutes
after which the ear is deleted/undeployed followed by a 10 second sleep till the next
deploy cycle.
I find this behaviour strange because http://jira.jboss.com/jira/browse/JBAS-1319 is
supposed to have fixed this issue.
The lines from the server.log surrounding the java.lang.OutOfMemoryError are as follows:
2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with
url null
2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository,
repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@e51e50,
cl=org.jboss.mx.loading.UnifiedClassLoader3@c90207{ url=null ,addedOrder=0}
2005-09-24 06:04:33,057 ERROR [org.apache.commons.digester.Digester] Begin event threw
error
java.lang.OutOfMemoryError
2005-09-24 06:04:33,057 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]]
StandardWrapper.Throwable
java.lang.OutOfMemoryError
2005-09-24 06:04:33,057 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]]
Servlet /XMPVXE0Partion/VXE1_ContentTestService threw load() exception
java.lang.OutOfMemoryError
2005-09-24 06:04:33,072 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with
url null
The following two jars were added to the server\default\lib folder.
commons-validator.jar --- version 1.1.3
struts.jar ---- version 1.2.4
--
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