Concurrency: reflection metho d lookups using single sychronous map holding locks under concurrent load

Description

Stack trace:

Caused by the map in SoftMethodStorage being declared synchronized. Does this really need to be a synchronized map? If so, is there a way that performance can be improved by not having a single map instance that all method reflection has to go through?

Environment

None

Status

Assignee

Unassigned

Reporter

Dominic Watson

Labels

Fix versions

Affects versions

5.3.3.63

Priority

Critical
Configure