July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6405) Performance: WeldDeployment.getBeanDeploymentArchive method is synchronized

by Jan Swaelens (JIRA)

[ https://issues.jboss.org/browse/WFLY-6405?page=com.atlassian.jira.plugin.... ] Jan Swaelens commented on WFLY-6405: ------------------------------------ Thanks [~kabirkhan] > 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 > Fix For: 10.1.0.CR1, 10.1.0.Final > > > (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 (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2227) Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2227?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2227: -------------------------------- Perhaps the members don't find each other? If B starts and doesn't find A in the discovery process, then of course no exception will be thrown. I suggest setting a breakpoint in {{JChannel._connect(Event evt)}}, to see what's going on. Also, if you enable trace logging of {{GMS}} and your discovery protocol (e.g. {{PING}}), you'll see whether B discovers A, or not. > Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name > ----------------------------------------------------------------------------------------------------------------- > > Key: JGRP-2227 > URL: https://issues.jboss.org/browse/JGRP-2227 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.6 > Reporter: Robert Cernak > Assignee: Bela Ban > Fix For: 4.0.12 > > Attachments: jgroupsDoesNotThrowSecurityExceptionWithJgroups4012.zip, jgroupsLogs.zip > > > I implemented method org.jgroups.auth.AuthToken#authenticate(AuthToken token, Message msg) in my class and its body contained only one line: return false; > In this way authentication should be false and I should get SecurityException. > When I started joining of nodes together to form a cluster, instead of getting SecurityException, nodes formed 2 different clusters with the same name. > I am sure method was evaluated, since I tried to run it also with breakpoint, which was triggered during joining process. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1946) DMN Editor