[
https://issues.apache.org/jira/browse/BEANUTILS-509?focusedWorklogId=362627&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-362627
]
ASF GitHub Bot logged work on BEANUTILS-509:
--------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Dec/19 18:33
Start Date: 23/Dec/19 18:33
Worklog Time Spent: 10m
Work Description: melloware commented on pull request #21:
[BEANUTILS-509] Wrap WeakHashMap in Collections.synchronizedMap
URL: https://github.com/apache/commons-beanutils/pull/21
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 362627)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 2018-10-13T11-43-27_961-jvmRun1.dump,
> 2018-10-13T11-43-27_961.dumpstream, BEANUTILS-509.diff, WrapDynaCache.patch,
> WrapDynaCache_after_svn_commit.patch, console.log.backup
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
