January 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6008) CommandDispatcher command execution thread should inherit context of dispatcher thread

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-6008: ---------------------------------- Summary: CommandDispatcher command execution thread should inherit context of dispatcher thread Key: WFLY-6008 URL: https://issues.jboss.org/browse/WFLY-6008 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.0.0.CR5 Reporter: Paul Ferraro Assignee: Paul Ferraro This should be as simple as leveraging the ContextService to create serializable contextual proxies of the submitted command instance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-313) Deadlock in WsRemoteEndpointImplServer.onWritePossible

by Aaron Ogburn (JIRA)

Aaron Ogburn created JBWEB-313: ---------------------------------- Summary: Deadlock in WsRemoteEndpointImplServer.onWritePossible Key: JBWEB-313 URL: https://issues.jboss.org/browse/JBWEB-313 Project: JBoss Web Issue Type: Bug Affects Versions: JBossWeb-7.5.0.GA Environment: JBoss EAP 6.4.5 Reporter: Aaron Ogburn Assignee: Remy Maucherat A deadlock is possible in WsRemoteEndpointImplServer.onWritePossible: {code} http-/0.0.0.0:8080-1": at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.onWritePossible(WsRemoteEndpointImplServer.java:93) - waiting to lock <0x00000006dee6a1a8> (a java.nio.HeapByteBuffer) - locked <0x00000006dee6a200> (a java.lang.Object) at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler$WsWriteListener.onWritePossible(WsHttpUpgradeHandler.java:243) at org.apache.catalina.core.StandardWrapperValve.async(StandardWrapperValve.java:605) at org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:350) at org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:171) at org.apache.catalina.valves.ValveBase.event(ValveBase.java:185) at org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:252) at org.apache.catalina.valves.ValveBase.event(ValveBase.java:185) at org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:121) at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:228) at org.apache.coyote.http11.Http11NioProcessor.event(Http11NioProcessor.java:232) at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.event(Http11NioProtocol.java:818) at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:939) - locked <0x00000006deeeb9c0> (a java.lang.Object) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.net.NioEndpoint$DefaultThreadFactory$1$1.run(NioEndpoint.java:1249) at java.lang.Thread.run(Thread.java:745) "EJB default - 1": at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.onWritePossible(WsRemoteEndpointImplServer.java:81) - waiting to lock <0x00000006dee6a200> (a java.lang.Object) at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doWrite(WsRemoteEndpointImplServer.java:76) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:444) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessage(WsRemoteEndpointImplBase.java:334) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase$TextMessageSendHandler.write(WsRemoteEndpointImplBase.java:741) - locked <0x00000006dee6a1a8> (a java.nio.HeapByteBuffer) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString(WsRemoteEndpointImplBase.java:239) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:182) at org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6007) The root cause of login module failures gets lost when multiple login modules are stacked

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-6007?page=com.atlassian.jira.plugin.... ] Tomas Hofman commented on WFLY-6007: ------------------------------------ I'm gonna post a PR there too. Is it wrong to have it here also? \ > The root cause of login module failures gets lost when multiple login modules are stacked > ----------------------------------------------------------------------------------------- > > Key: WFLY-6007 > URL: https://issues.jboss.org/browse/WFLY-6007 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.CR5 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > https://bugzilla.redhat.com/show_bug.cgi?id=1288668 > The root cause of login module failures gets lost when multiple login modules are stacked and the "flag" attribute is set to "optional". > When the login attempt fails (invalid bindCredential on the LdapExtLoginModule for example) the authentication request will continue to the next login module in the stack. In this situation, the exceptions "cause" attribute is getting overwritten during the processing of the other login modules. This results in the actual cause to get lost during processing. > This makes troubleshooting authentication failures difficult. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6007) The root cause of login module failures gets lost when multiple login modules are stacked

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6007?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-6007: ---------------------------------------- This needs to be in the PicketBox project > The root cause of login module failures gets lost when multiple login modules are stacked > ----------------------------------------------------------------------------------------- > > Key: WFLY-6007 > URL: https://issues.jboss.org/browse/WFLY-6007 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.CR5 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > https://bugzilla.redhat.com/show_bug.cgi?id=1288668 > The root cause of login module failures gets lost when multiple login modules are stacked and the "flag" attribute is set to "optional". > When the login attempt fails (invalid bindCredential on the LdapExtLoginModule for example) the authentication request will continue to the next login module in the stack. In this situation, the exceptions "cause" attribute is getting overwritten during the processing of the other login modules. This results in the actual cause to get lost during processing. > This makes troubleshooting authentication failures difficult. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6007) The root cause of login module failures gets lost when multiple login modules are stacked

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-6007?page=com.atlassian.jira.plugin.... ] Tomas Hofman moved JBEAP-2818 to WFLY-6007: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-6007 (was: JBEAP-2818) Workflow: GIT Pull Request workflow (was: CDW v1) Component/s: Security (was: Security) Target Release: (was: 7.0.0.GA) Affects Version/s: 10.0.0.CR5 (was: 7.0.0.ER3) > The root cause of login module failures gets lost when multiple login modules are stacked > ----------------------------------------------------------------------------------------- > > Key: WFLY-6007 > URL: https://issues.jboss.org/browse/WFLY-6007 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.CR5 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > https://bugzilla.redhat.com/show_bug.cgi?id=1288668 > The root cause of login module failures gets lost when multiple login modules are stacked and the "flag" attribute is set to "optional". > When the login attempt fails (invalid bindCredential on the LdapExtLoginModule for example) the authentication request will continue to the next login module in the stack. In this situation, the exceptions "cause" attribute is getting overwritten during the processing of the other login modules. This results in the actual cause to get lost during processing. > This makes troubleshooting authentication failures difficult. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6006) org.jboss.as.security-api module should be deprecated

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-6006?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-6006: ----------------------------------- Fix Version/s: 10.0.0.Final > org.jboss.as.security-api module should be deprecated > ----------------------------------------------------- > > Key: WFLY-6006 > URL: https://issues.jboss.org/browse/WFLY-6006 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 10.0.0.Final > > > According to Eng, PM and QA inputs in [Module Classification doc|https://mojo.redhat.com/docs/DOC-1053168] there seems to be agreement to change visibility of this module back to deprecated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1303) NPE in principal-to-group group searching

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1303?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-1303: ---------------------------------------- Assignee: Darran Lofthouse (was: Brian Stansberry) > NPE in principal-to-group group searching > ----------------------------------------- > > Key: WFCORE-1303 > URL: https://issues.jboss.org/browse/WFCORE-1303 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.0.7.Final > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > In case when ldap authorization with principal-to-group group searching is used in security realm and LDAP entry found by value of 'group-attribute' does not include attribute mentioned in 'group-name-attribute' then it causes authentication fail. It is caused by missing null check for groupNameAttr and hidden NPE thrown from [1]. > [1] https://github.com/wildfly/wildfly-core/blob/bcc56983730d976ec77ede0d5901... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-120) Static interface methods in Logger interface requires annotation

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-120?page=com.atlassian.jira.plu... ] David Lloyd commented on JBLOGGING-120: --------------------------------------- This should probably also be true of default methods too. > Static interface methods in Logger interface requires annotation > ---------------------------------------------------------------- > > Key: JBLOGGING-120 > URL: https://issues.jboss.org/browse/JBLOGGING-120 > Project: JBoss Logging > Issue Type: Bug > Components: jboss-logging-logmanager > Affects Versions: 3.3.0.Beta1 > Reporter: Radim Vansa > Assignee: James Perkins > > When I want to add a static helper method to the interface used for message logger, I get an error about requiring the @Message annotation. I think that this should not be required for static methods. > My usecase: > {code} > @MessageLogger(projectCode = "FOO") > public interface FooMessageLogger extends BasicLogger { > static FooMessageLogger getLog(Class clazz) { > return Logger.getMessageLogger(FooMessageLogger.class, clazz.getName()); > } > /* regular annotated logging methods */ > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1759) BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1759?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1759. ---------------------------- Resolution: Cannot Reproduce > BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks > ---------------------------------------------------------------- > > Key: JGRP-1759 > URL: https://issues.jboss.org/browse/JGRP-1759 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.5 > Environment: Windows 2008, x86_64 > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.8 > > > Running the Byteman tests in the QA lab, this test deadlocks in a repeatable fashion and causes the testsuite to hang. > The test makes use of the Byteman rendezvous built-in function to suspend (and reorder) thread execution. It appears that with threads re-ordered, certain parts of JGroups block in such a way that no progress is made and the test deadlocks. > . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1759) BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1759?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1759: --------------------------- Fix Version/s: 3.6.8 (was: 4.0) Hasn't failed ever, please re-open should you run into a failed test again... > BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks > ---------------------------------------------------------------- > > Key: JGRP-1759 > URL: https://issues.jboss.org/browse/JGRP-1759 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.5 > Environment: Windows 2008, x86_64 > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6.8 > > > Running the Byteman tests in the QA lab, this test deadlocks in a repeatable fashion and causes the testsuite to hang. > The test makes use of the Byteman rendezvous built-in function to suspend (and reorder) thread execution. It appears that with threads re-ordered, certain parts of JGroups block in such a way that no progress is made and the test deadlocks. > . -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2016