[
https://issues.apache.org/jira/browse/BEANUTILS-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16640688#comment-16640688
]
Akshay Gehi commented on BEANUTILS-509:
---------------------------------------
Hi Gary,
I mentioned in the Junit that the test case is extremely hard to reproduce, we
faced this after running the class for 30 hours continuously. As you know,
WeakHashMap is quite unpredictable and the BeanUtils makes use of this class in
a non-thread safe manner which causes the problem and I have fixed that. I
cannot add any further test cases. In case someone else can pitch or have any
suggestions, I can have a look.
Regards,
Akshay Gehi
> WeakHashmap enters into infinite loop in WrapDynaClass.java
> -----------------------------------------------------------
>
> Key: BEANUTILS-509
> URL: https://issues.apache.org/jira/browse/BEANUTILS-509
> Project: Commons BeanUtils
> Issue Type: Bug
> Components: DynaBean
> Affects Versions: 1.8.2
> Reporter: sunil
> Priority: Major
> Attachments: WrapDynaCache.patch,
> WrapDynaCache_after_svn_commit.patch, console.log.backup
>
>
> We noticed that our application was using too much of CPU , all the 6 cores
> were used.
> On capturing the thread dump we saw that large number of threads were in the
> running state and in :
> at java.util.WeakHashMap.get(WeakHashMap.java:403)
> at
> org.apache.commons.beanutils.WrapDynaClass.createDynaClass(WrapDynaClass.java:425)
>
> So we are suspecting that the thread has entered into indefinite while loop
> and hogging all the CPU resources.
> I have attached the thread dump for reference.
>
> what is the solution for this issue?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
