March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7040) Add a set of tests for HTTP authentication when backed by Elytron

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7040?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7040: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Add a set of tests for HTTP authentication when backed by Elytron > ----------------------------------------------------------------- > > Key: WFLY-7040 > URL: https://issues.jboss.org/browse/WFLY-7040 > Project: WildFly > Issue Type: Task > Components: Test Suite, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Critical > Labels: elytron_testing > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7564) EJB Attachment protocol mismatch

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7564?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7564: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > EJB Attachment protocol mismatch > -------------------------------- > > Key: WFLY-7564 > URL: https://issues.jboss.org/browse/WFLY-7564 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Blocker > Fix For: 11.0.0.Beta1 > > > In both EJB client and server code, on method invocations where context data is sent, the sender writes the attachment count as a packed integer but the reader consumes it as an unsigned byte. This is not good. > The fix: > * In protocol 3 and higher, always read and write a packed integer > * In protocol 2 and lower, always read a packed integer but write a signed byte, failing if more than 127 attachments are present > Note that this is only temporary in the WFLY project as the server code should ultimately be moving to live in the ejb-client library. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7361) data-source attribute should not be an attribute of all JGroups protocols

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7361?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7361: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > data-source attribute should not be an attribute of all JGroups protocols > ------------------------------------------------------------------------- > > Key: WFLY-7361 > URL: https://issues.jboss.org/browse/WFLY-7361 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > > We should create a custom JDBCProtocolResourceDefinition that extends ProtocolResourceDefinition that adds a data-source attribute and capability reference. > This can be registered separately from the generic protocol resource definition. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7419) Add resteasy wadl as a module

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7419?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7419: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Add resteasy wadl as a module > ----------------------------- > > Key: WFLY-7419 > URL: https://issues.jboss.org/browse/WFLY-7419 > Project: WildFly > Issue Type: Enhancement > Components: REST > Affects Versions: 10.1.0.Final, 11.0.0.Alpha1 > Reporter: Frank Langelage > Assignee: Alessio Soldano > Fix For: 10.2.0.Final, 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7304) Compensations subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7304?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7304: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Compensations subsystem > ----------------------- > > Key: WFLY-7304 > URL: https://issues.jboss.org/browse/WFLY-7304 > Project: WildFly > Issue Type: Task > Components: Transactions > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 11.0.0.Beta1 > > > Currently compensations bootstrap happens in the transactions subsystem. It registers deployment processor to scan the annotations and add the dependencies if necessary. This is not expensive and doesn't cause any issues other than adding the dependencies to the transactions subsystem. However, I'm currently finishing off the recovery implementation and more bootstrap logic will be needed. In addition, two more recovery modules will have to be registered: one for the participant (a new one) and one for the coordinator (from XTS). This will require to add XTS dependency too. > The whole compensations bootstrapping will not need a lot of code. However, I'm thinking maybe it would be good to pull it out to the separate subsystem in order to maintain the separation of concerns. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7303) Unignore tests in org.jboss.as.test.integration.ejb.mdb.MDBTestCase and org.jboss.as.test.integration.ejb.mdb.deliveryactive.MDBTestCase

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7303?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7303: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Unignore tests in org.jboss.as.test.integration.ejb.mdb.MDBTestCase and org.jboss.as.test.integration.ejb.mdb.deliveryactive.MDBTestCase > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7303 > URL: https://issues.jboss.org/browse/WFLY-7303 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Farah Juma > Assignee: Farah Juma > Labels: affects_elytron > Fix For: 11.0.0.Beta1 > > > When tests in {{org.jboss.as.test.integration.ejb.mdb.MDBTestCase}} and {{org.jboss.as.test.integration.ejb.mdb.deliveryactive.MDBTestCase}} fail, the tests that get run after these ones fail as well. These tests in MDBTestCases will be fixed during Phase III Remoting 5 integration but temporarily ignoring them for now to try to get the CI job in better shape. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7537) Review NamingContext.check() method

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7537?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7537: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Review NamingContext.check() method > ----------------------------------- > > Key: WFLY-7537 > URL: https://issues.jboss.org/browse/WFLY-7537 > Project: WildFly > Issue Type: Task > Components: Naming > Reporter: Darran Lofthouse > Assignee: Farah Juma > Fix For: 11.0.0.Beta1 > > > The new naming client is sending in a SimpleName where the lookup was performed using a String. > When a SecurityManager is installed the check() method of NamingContext is called and results in the following error: - > {noformat} > javax.naming.InvalidNameException: Not a composite name: jms > at javax.naming.CompositeName.addAll(CompositeName.java:472) > at org.jboss.as.naming.NamingContext.check(NamingContext.java:592) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) > at org.jboss.naming.remote.protocol.v1.Protocol$1.handleServerMessage(Protocol.java:127) > at org.jboss.naming.remote.protocol.v1.RemoteNamingServerV1$MessageReciever$1.run(RemoteNamingServerV1.java:73) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {noformat} > A fix has been applied to convert the incoming name to a CompositeName but as we deliberately have a SimpleName to avoid CompositeName I wonder if that is completely correct. > Some other options I think of: - > 1. Stick with current fix. > 2 The client should convert to CompositeName before sending. > 3. Manually iterate the segments if not a CompositeName > 4. Check if the NamingStore really needs to use a CompositeName -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7283) Update EJB to use txn spi

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7283?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7283: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Update EJB to use txn spi > ------------------------- > > Key: WFLY-7283 > URL: https://issues.jboss.org/browse/WFLY-7283 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Affects Versions: 10.1.0.Final > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Minor > Fix For: 10.2.0.Final, 11.0.0.Beta1 > > > Remote references from EJB to internal transaction classes, replacing then by references to the spi. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7235) InfinispanResourceRefTestCase fails with security manager

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-7235?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-7235: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > InfinispanResourceRefTestCase fails with security manager > --------------------------------------------------------- > > Key: WFLY-7235 > URL: https://issues.jboss.org/browse/WFLY-7235 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Jan Tymel > Assignee: Ingo Weiss > Fix For: 11.0.0.Beta1 > > > *org.jboss.as.test.integration.ee.injection.resource.infinispan.InfinispanResourceRefTestCase#test* > {{./integration-tests.sh -DtestLogToFile=false -Dts.noSmoke -Dts.basic -Dtest=org.jboss.as.test.integration.ee.injection.resource.infinispan.InfinispanResourceRefTestCase -Dsecurity.manager}} > {code} > Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.lang.RuntimePermission" "getClassLoader")" in code source "(vfs:/content/infinispan-resource-ref.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.infinispan-resource-ref.war:main" from Service Module Loader") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) > at java.lang.ClassLoader.checkClassLoaderPermission(ClassLoader.java:1528) > at java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1442) > at org.infinispan.commons.util.Util.getClassLoaders(Util.java:127) > at org.infinispan.commons.util.Util.loadClassStrict(Util.java:163) > at org.infinispan.commons.util.ReflectionUtil.getClassForName(ReflectionUtil.java:319) > at org.infinispan.commons.util.ReflectionUtil.toClassArray(ReflectionUtil.java:313) > at org.infinispan.factories.AbstractComponentRegistry$Component.buildInjectionMethodsList(AbstractComponentRegistry.java:810) > at org.infinispan.factories.AbstractComponentRegistry.registerComponentInternal(AbstractComponentRegistry.java:213) > at org.infinispan.factories.ComponentRegistry.registerComponentInternal(ComponentRegistry.java:193) > at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:171) > at org.infinispan.factories.AbstractComponentRegistry.registerComponent(AbstractComponentRegistry.java:163) > at org.infinispan.factories.ComponentRegistry.<init>(ComponentRegistry.java:79) > ... 210 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8250) Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8250?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8250: ------------------------------- Fix Version/s: 11.0.0.Beta1 (was: 11.0.0.Alpha1) > Ensure all Elytron subsystem resources that depend on the core services also record a capability dependency. > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-8250 > URL: https://issues.jboss.org/browse/WFLY-8250 > Project: WildFly > Issue Type: Enhancement > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 11.0.0.Beta1 > > > This builds on https://issues.jboss.org/browse/WFCORE-1106 so we can skip runtime steps when the dependent services are not available. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 March 2017