September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9406) [WildFly 11] Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin.... ] Tibor Digana updated WFLY-9406: ------------------------------- Component/s: REST > [WildFly 11] Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) > ------------------------------------------------------------------------------------------ > > Key: WFLY-9406 > URL: https://issues.jboss.org/browse/WFLY-9406 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld, Class Loading, REST > Affects Versions: 11.0.0.CR1 > Reporter: Tibor Digana > Assignee: Martin Kouba > Priority: Critical > Fix For: 11.0.0.Final > > > Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 > Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. > Please upgrade it in POM: > https://github.com/wildfly/wildfly/blob/master/pom.xml -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9406) [WildFly 11] Update ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin.... ] Tibor Digana updated WFLY-9406: ------------------------------- Description: Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. Please upgrade it in POM: https://github.com/wildfly/wildfly/blob/master/pom.xml was: Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaoCo uses ASM 5.2. The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. Please upgrade it in POM: https://github.com/wildfly/wildfly/blob/master/pom.xml > [WildFly 11] Update ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) > ----------------------------------------------------------------------------------------- > > Key: WFLY-9406 > URL: https://issues.jboss.org/browse/WFLY-9406 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld, Class Loading > Affects Versions: 11.0.0.CR1 > Reporter: Tibor Digana > Assignee: Martin Kouba > Priority: Critical > Fix For: 11.0.0.Final > > > Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 > Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. > Please upgrade it in POM: > https://github.com/wildfly/wildfly/blob/master/pom.xml -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9406) [WildFly 11] Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin.... ] Tibor Digana updated WFLY-9406: ------------------------------- Summary: [WildFly 11] Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) (was: [WildFly 11] Update ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)) > [WildFly 11] Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) > ------------------------------------------------------------------------------------------ > > Key: WFLY-9406 > URL: https://issues.jboss.org/browse/WFLY-9406 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld, Class Loading > Affects Versions: 11.0.0.CR1 > Reporter: Tibor Digana > Assignee: Martin Kouba > Priority: Critical > Fix For: 11.0.0.Final > > > Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 > Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. > Please upgrade it in POM: > https://github.com/wildfly/wildfly/blob/master/pom.xml -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1374) The elytron-1_0.xsd has elements the parser does not accept

by Ilia Vassilev (JIRA)

Ilia Vassilev created ELY-1374: ---------------------------------- Summary: The elytron-1_0.xsd has elements the parser does not accept Key: ELY-1374 URL: https://issues.jboss.org/browse/ELY-1374 Project: WildFly Elytron Issue Type: Bug Reporter: Ilia Vassilev Assignee: Ilia Vassilev There are elements in the {{elytron-1_0.xsd}} that the parser does not accept. While I didn't check them all here are at least a few that are in the XSD that the parser will reject: * {{allow-sasl-mechanisms}} * {{allow-all-sasl-mechanisms}} * {{forbid-sasl-mechanisms}} This may be all of them, but it should likely be validated that those are the only ones. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-978) Remove DEBUG message in server logs while calling isCallerInRole(String roleName) method

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/SECURITY-978?page=com.atlassian.jira.plug... ] Ilia Vassilev commented on SECURITY-978: ---------------------------------------- PR: https://github.com/picketbox/picketbox/pull/72 > Remove DEBUG message in server logs while calling isCallerInRole(String roleName) method > ---------------------------------------------------------------------------------------- > > Key: SECURITY-978 > URL: https://issues.jboss.org/browse/SECURITY-978 > Project: PicketBox > Issue Type: Bug > Environment: Red Hat JBoss Enterprise Application Platform 7.0.x > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > > While explicitly checking the user roles in the ejb code using context.isCallerInRole(String roleName) and when it return false below exception message got printed at the DEBUG level in server.log file. > {code:java} > 2017-09-13 21:10:24,549 DEBUG [org.jboss.security] sessionhash="b34cb4c5c50e3eefbe4f924ee42fa658" requestid="33015X1505317224509" username="adm2.lg" src_ip="127.0.0.1" PBOX00326: isCallerInRole processing failed: org.jboss.security.authorization.AuthorizationException: PBOX00017: Acces denied: authorization failed > at org.jboss.security.plugins.authorization.JBossAuthorizationContext.invokeAuthorize(JBossAuthorizationContext.java:274) > at org.jboss.security.plugins.authorization.JBossAuthorizationContext.access$000(JBossAuthorizationContext.java:71) > at org.jboss.security.plugins.authorization.JBossAuthorizationContext$1.run(JBossAuthorizationContext.java:147) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.security.plugins.authorization.JBossAuthorizationContext.authorize(JBossAuthorizationContext.java:143) > at org.jboss.security.plugins.JBossAuthorizationManager.internalAuthorization(JBossAuthorizationManager.java:438) > at org.jboss.security.plugins.JBossAuthorizationManager.authorize(JBossAuthorizationManager.java:115) > at org.jboss.security.plugins.javaee.EJBAuthorizationHelper.isCallerInRole(EJBAuthorizationHelper.java:187) > at org.jboss.as.security.service.SimpleSecurityManager.isCallerInRole(SimpleSecurityManager.java:229) > at org.jboss.as.ejb3.component.EJBComponent.isCallerInRole(EJBComponent.java:400) > at org.jboss.as.ejb3.context.EJBContextImpl.isCallerInRole(EJBContextImpl.java:115) > {code} > The exception seems to be printed in DEBUG in the below line > {code:java} > https://github.com/picketbox/picketbox/blob/master/security-jboss-sx/jbos... > {code} > This should not be logged as an exception message may be just a line in DEBUG logs should be enough. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9406) [WildFly 11] Update ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)

by Tibor Digana (JIRA)

[ https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin.... ] Tibor Digana updated WFLY-9406: ------------------------------- Description: Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaoCo uses ASM 5.2. The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. Please upgrade it in POM: https://github.com/wildfly/wildfly/blob/master/pom.xml was: Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaoCo uses ASM 5.2. The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{ org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. Please upgrade it in POM: https://github.com/wildfly/wildfly/blob/master/pom.xml > [WildFly 11] Update ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) > ----------------------------------------------------------------------------------------- > > Key: WFLY-9406 > URL: https://issues.jboss.org/browse/WFLY-9406 > Project: WildFly > Issue Type: Component Upgrade > Components: CDI / Weld, Class Loading > Affects Versions: 11.0.0.CR1 > Reporter: Tibor Digana > Assignee: Martin Kouba > Priority: Critical > Fix For: 11.0.0.Final > > > Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 > Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaoCo uses ASM 5.2. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. > Please upgrade it in POM: > https://github.com/wildfly/wildfly/blob/master/pom.xml -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9406) [WildFly 11] Update ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)

by Tibor Digana (JIRA)

Tibor Digana created WFLY-9406: ---------------------------------- Summary: [WildFly 11] Update ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) Key: WFLY-9406 URL: https://issues.jboss.org/browse/WFLY-9406 Project: WildFly Issue Type: Component Upgrade Components: CDI / Weld, Class Loading Affects Versions: 11.0.0.CR1 Reporter: Tibor Digana Assignee: Martin Kouba Priority: Critical Fix For: 11.0.0.Final Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaoCo uses ASM 5.2. The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{ org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. Please upgrade it in POM: https://github.com/wildfly/wildfly/blob/master/pom.xml -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3322) Invalid socket-binding config in remoting connector resource does not lead to model integrity failure

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3322: ---------------------------------------- Summary: Invalid socket-binding config in remoting connector resource does not lead to model integrity failure Key: WFCORE-3322 URL: https://issues.jboss.org/browse/WFCORE-3322 Project: WildFly Core Issue Type: Bug Components: Remoting Reporter: Brian Stansberry Assignee: Brian Stansberry A remoting connector with a socket-binding attribute pointing to a non-existing s-b does not fail with a capability validation failure: {code} [standalone@localhost:9990 /] /subsystem=remoting/connector=remoting-connector:add(security-realm=ApplicationRealm,socket-binding=remoting) { "outcome" => "failed", "failure-description" => { "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.network.socket-binding.remoting"], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.remoting-connector is missing [org.wildfly.network.socket-binding.remoting]"] }, "rolled-back" => true } {code} As in all such cases of missing cap validation, that means it doesn't fail at all in admin-only: {code} [standalone@localhost:9990 /] reload --admin-only=true [standalone@localhost:9990 /] /subsystem=remoting/connector=remoting-connector:add(security-realm=ApplicationRealm,socket-binding=remoting) {"outcome" => "success"} {code} Problem is ConnectorAdd isn't passing its attributes into the superclass, which means the superclass' recording of capability requirements isn't done. I'll check for other occurrences of this pattern in the subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9405) NPE when trying to recursively remove the EJB subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9405?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9405: ----------------------------------- Workaround Description: Put the server in admin-only mode before removing the subsystem. {code} [standalone@localhost:9990 /] reload --admin-only=true [standalone@localhost:9990 /] /subsystem=ejb3:remove {"outcome" => "success"} {code} Putting the server in admin-only before doing this kind of surgery is probably a good idea anyway. was: Put the server in admin-only mode before removing the subsystem. {code} [standalone@localhost:9990 /] reload --admin-only=true [standalone@localhost:9990 /] /subsystem=ejb3:remove {"outcome" => "success"} {code} > NPE when trying to recursively remove the EJB subsystem > ------------------------------------------------------- > > Key: WFLY-9405 > URL: https://issues.jboss.org/browse/WFLY-9405 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.CR1 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > This fails: > {code} > [standalone@localhost:9990 /] /subsystem=ejb3:remove > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException", > "rolled-back" => true > } > {code} > with this in the server log: > {code} > 15:53:42,572 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("remove") failed - address: ([ > ("subsystem" => "ejb3"), > ("service" => "remote"), > ("channel-creation-options" => "MAX_OUTBOUND_MESSAGES") > ]): java.lang.NullPointerException > at org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:894) > at org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:884) > at org.jboss.as.controller.RestartParentResourceHandlerBase.getModel(RestartParentResourceHandlerBase.java:216) > at org.jboss.as.controller.RestartParentResourceHandlerBase.access$000(RestartParentResourceHandlerBase.java:39) > at org.jboss.as.controller.RestartParentResourceHandlerBase$1.execute(RestartParentResourceHandlerBase.java:66) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:980) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418) > ... > {code} > I believe a post-boot add of this resource would fail as well. > Problem is ChannelCreationOptionRemove and ChannelCreationOptionAdd in RemoteConnectorChannelCreationOptionResource use an incorrect parentKeyName. These handlers extend RestartParentResourceHandlerBase but are passing the *value* of the parent element as "parentKeyName" instead of its *key*; i.e. "remote" instead of "service". > Even though this code has been like this since 2012, this is somewhat a regression since before the current version our standard configs did not include resources of this type. So users could hit this in previous releases but now they are more likely to. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9405) NPE when trying to recursively remove the EJB subsystem

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-9405: -------------------------------------- Summary: NPE when trying to recursively remove the EJB subsystem Key: WFLY-9405 URL: https://issues.jboss.org/browse/WFLY-9405 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 11.0.0.CR1 Reporter: Brian Stansberry Assignee: Brian Stansberry This fails: {code} [standalone@localhost:9990 /] /subsystem=ejb3:remove { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException", "rolled-back" => true } {code} with this in the server log: {code} 15:53:42,572 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("remove") failed - address: ([ ("subsystem" => "ejb3"), ("service" => "remote"), ("channel-creation-options" => "MAX_OUTBOUND_MESSAGES") ]): java.lang.NullPointerException at org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:894) at org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:884) at org.jboss.as.controller.RestartParentResourceHandlerBase.getModel(RestartParentResourceHandlerBase.java:216) at org.jboss.as.controller.RestartParentResourceHandlerBase.access$000(RestartParentResourceHandlerBase.java:39) at org.jboss.as.controller.RestartParentResourceHandlerBase$1.execute(RestartParentResourceHandlerBase.java:66) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:980) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418) ... {code} I believe a post-boot add of this resource would fail as well. Problem is ChannelCreationOptionRemove and ChannelCreationOptionAdd in RemoteConnectorChannelCreationOptionResource use an incorrect parentKeyName. These handlers extend RestartParentResourceHandlerBase but are passing the *value* of the parent element as "parentKeyName" instead of its *key*; i.e. "remote" instead of "service". Even though this code has been like this since 2012, this is somewhat a regression since before the current version our standard configs did not include resources of this type. So users could hit this in previous releases but now they are more likely to. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 September 2017