[
https://issues.jboss.org/browse/WFLY-6405?page=com.atlassian.jira.plugin....
]
James Perkins commented on WFLY-6405:
-------------------------------------
I've added a follow up PR,
https://github.com/wildfly/wildfly/pull/9021, as
{{ConcurrentHashMap}}'s don't allow null keys. {{Class.getClassLoader()}} may
return {{null}} if the class was loaded on the bootstrap class loader. e.g.
{{java.lang.Integer}}.
Performance: WeldDeployment.getBeanDeploymentArchive method is
synchronized
---------------------------------------------------------------------------
Key: WFLY-6405
URL:
https://issues.jboss.org/browse/WFLY-6405
Project: WildFly
Issue Type: Bug
Components: CDI / Weld, Class Loading
Affects Versions: 10.0.0.Final
Reporter: Panos Grigoropoulos
Assignee: Stuart Douglas
(Wildfly 10.0.0.FINAL)
During the performance test of my app (50 concurrent users with jmeter) I am running into
the following issue:
There are locked threads in the method WeldDeployment.getBeanDeploymentArchive(). Looking
the code, this method is synchronized, so it makes sense. The question is, is this the
expected behavior or this is a bug. In both cases is there any workaround to overcome this
limitation?
STACK TRACE:
....
org.jboss.as.weld.WeldProvider$CdiImpl.getBeanManager():73
org.jboss.as.weld.WeldProvider$CdiImpl.getBeanManager():93
org.jboss.as.weld.deployment.WeldDeployment.getBeanDeploymentArchive():226
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)