December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14169) Remove the wildfly-ee feature pack dependency on wildfly-servlet

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14169?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14169: ------------------------------------ Summary: Remove the wildfly-ee feature pack dependency on wildfly-servlet (was: Remove wildfly-ee feature pack dependency on wildfly-servlet) > Remove the wildfly-ee feature pack dependency on wildfly-servlet > ---------------------------------------------------------------- > > Key: WFLY-14169 > URL: https://issues.redhat.com/browse/WFLY-14169 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 22.0.0.Beta1 > > > Have the wildfly-ee feature pack share source with the wildfly-servlet feature pack instead of having a feature pack dependency. > As the relevant source is in the same git repo as the wildfly-ee fp's maven module this source sharing would be via maven resource plugin copying during the build, not via GAL-319. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14189) The RunAs annotation doesn't work in EJBs with Elytron

by Alessandro Moscatelli (Jira)

[ https://issues.redhat.com/browse/WFLY-14189?page=com.atlassian.jira.plugi... ] Alessandro Moscatelli updated WFLY-14189: ----------------------------------------- Description: Role is not correctly assigned when using @RunAs annotation and Elytron Security Domain. Everything works correctly with legacy picketbox Security Domain. Wildfly is configured to use default "other" application-security-domain, also using default security domain ApplicationDomain. This exception is rised when deploying the application. Caused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowedCaused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowed at org.jboss.as.ejb3@21.0.0.Final//org.jboss.as.ejb3.security.JaccInterceptor.hasPermission(JaccInterceptor.java:120) Test/Sample project: [^test.zip] was: Role is not correctly assigned when using @RunAs annotation and Elytron Security Domain. Everything works correctly with legacy picketbox Security Domain. Caused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowedCaused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowed at org.jboss.as.ejb3@21.0.0.Final//org.jboss.as.ejb3.security.JaccInterceptor.hasPermission(JaccInterceptor.java:120) Test/Sample project: [^test.zip] > The RunAs annotation doesn't work in EJBs with Elytron > ------------------------------------------------------ > > Key: WFLY-14189 > URL: https://issues.redhat.com/browse/WFLY-14189 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 21.0.0.Final > Reporter: Alessandro Moscatelli > Assignee: Darran Lofthouse > Priority: Major > Labels: ejb, elytron, regression, runas, security, startup > Fix For: 21.0.2.Final > > Attachments: test.zip > > > Role is not correctly assigned when using @RunAs annotation and Elytron Security Domain. Everything works correctly with legacy picketbox Security Domain. > Wildfly is configured to use default "other" application-security-domain, also using default security domain ApplicationDomain. > This exception is rised when deploying the application. > Caused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowedCaused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowed at org.jboss.as.ejb3@21.0.0.Final//org.jboss.as.ejb3.security.JaccInterceptor.hasPermission(JaccInterceptor.java:120) > Test/Sample project: [^test.zip] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14189) The RunAs annotation doesn't work in EJBs with Elytron

by Alessandro Moscatelli (Jira)

[ https://issues.redhat.com/browse/WFLY-14189?page=com.atlassian.jira.plugi... ] Alessandro Moscatelli updated WFLY-14189: ----------------------------------------- Security: (was: Security Issue) > The RunAs annotation doesn't work in EJBs with Elytron > ------------------------------------------------------ > > Key: WFLY-14189 > URL: https://issues.redhat.com/browse/WFLY-14189 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 21.0.0.Final > Reporter: Alessandro Moscatelli > Assignee: Darran Lofthouse > Priority: Major > Labels: ejb, elytron, regression, runas, security, startup > Fix For: 21.0.2.Final > > Attachments: test.zip > > > Role is not correctly assigned when using @RunAs annotation and Elytron Security Domain. Everything works correctly with legacy picketbox Security Domain. > Caused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowedCaused by: javax.ejb.EJBAccessException: WFLYEJB0364: Invocation on method: public abstract void org.visiontech.test.TestInterface.test() of bean: Test2 is not allowed at org.jboss.as.ejb3@21.0.0.Final//org.jboss.as.ejb3.security.JaccInterceptor.hasPermission(JaccInterceptor.java:120) > Test/Sample project: [^test.zip] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14188) Update Apache avro 1.10.1

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-14188?page=com.atlassian.jira.plugi... ] Scott Marlow commented on WFLY-14188: ------------------------------------- [~xf01213] what is the reason for upgrading to a new version of Avro? Is this related to Avro use with Hibernate Search? Or for a different reason? It looks like WildFly is using the same version (1.7.6) of Avro as the [Hibernate Search 5.10 branch is using|https://github.com/hibernate/hibernate-search/blob/5.10/pom.xml#L207]. > Update Apache avro 1.10.1 > ------------------------- > > Key: WFLY-14188 > URL: https://issues.redhat.com/browse/WFLY-14188 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Affects Versions: 22.0.0.Alpha1 > Reporter: Boris Unckel > Assignee: Brian Stansberry > Priority: Major > > Update [Apache avro 1.10.1|https://mvnrepository.com/artifact/org.apache.avro/avro/1.10.1] ([released 2020-12-03|https://avro.apache.org/releases.html]) > 2020-12-07: Release Note generation is outdated -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14188) Update Apache avro 1.10.1

by Boris Unckel (Jira)

Boris Unckel created WFLY-14188: ----------------------------------- Summary: Update Apache avro 1.10.1 Key: WFLY-14188 URL: https://issues.redhat.com/browse/WFLY-14188 Project: WildFly Issue Type: Component Upgrade Components: Server Affects Versions: 22.0.0.Alpha1 Reporter: Boris Unckel Assignee: Brian Stansberry Update [Apache avro 1.10.1|https://mvnrepository.com/artifact/org.apache.avro/avro/1.10.1] ([released 2020-12-03|https://avro.apache.org/releases.html]) 2020-12-07: Release Note generation is outdated -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14187) Upgrade to EE 9 fork of Jakarta Expression Language SPEC API (jboss-jakarta-el-api_spec)

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-14187?page=com.atlassian.jira.plugi... ] Scott Marlow updated WFLY-14187: -------------------------------- Labels: EE9 (was: ) > Upgrade to EE 9 fork of Jakarta Expression Language SPEC API (jboss-jakarta-el-api_spec) > ---------------------------------------------------------------------------------------- > > Key: WFLY-14187 > URL: https://issues.redhat.com/browse/WFLY-14187 > Project: WildFly > Issue Type: Feature Request > Components: EE > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Labels: EE9 > Fix For: 22.0.0.Beta1 > > > Upgrade to EE 9 fork of github.com/jboss/jboss-jakarta-el-api_spec using org.jboss.spec.jakarta.el:jboss-el-api_4.0_spec:3.0.0 > This brings in the [https://issues.redhat.com/browse/WFLY-13969] fix by [~parsharma]! Thanks again Parul for stepping up to fix the EL signature test failures! :-) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14187) Upgrade to EE 9 fork of Jakarta Expression Language SPEC API (jboss-jakarta-el-api_spec)

by Scott Marlow (Jira)

Scott Marlow created WFLY-14187: ----------------------------------- Summary: Upgrade to EE 9 fork of Jakarta Expression Language SPEC API (jboss-jakarta-el-api_spec) Key: WFLY-14187 URL: https://issues.redhat.com/browse/WFLY-14187 Project: WildFly Issue Type: Feature Request Components: EE Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 22.0.0.Beta1 Upgrade to EE 9 fork of github.com/jboss/jboss-jakarta-el-api_spec using org.jboss.spec.jakarta.el:jboss-el-api_4.0_spec:3.0.0 This brings in the [https://issues.redhat.com/browse/WFLY-13969] fix by [~parsharma]! Thanks again Parul for stepping up to fix the EL signature test failures! :-) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14186) Update netty.io to 4.1.54

by Boris Unckel (Jira)

Boris Unckel created WFLY-14186: ----------------------------------- Summary: Update netty.io to 4.1.54 Key: WFLY-14186 URL: https://issues.redhat.com/browse/WFLY-14186 Project: WildFly Issue Type: Component Upgrade Components: Clustering, JMS Reporter: Boris Unckel Assignee: Paul Ferraro Update [netty.io 4.1.54|https://mvnrepository.com/artifact/io.netty/netty-all/4.1.54.Final] Release Notes [https://netty.io/news/2020/11/11/4-1-54-Final.html] [https://netty.io/news/2020/10/13/4-1-53-Final.html] [https://netty.io/news/2020/09/08/4-1-52-Final.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14114) Class loader leaks when JDBC driver as jar deployment is undeloyed

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14114?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFLY-14114: ------------------------------------- Thanks [~gaol] for pointing out I resolved this prematurely. > Class loader leaks when JDBC driver as jar deployment is undeloyed > ------------------------------------------------------------------ > > Key: WFLY-14114 > URL: https://issues.redhat.com/browse/WFLY-14114 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Lin Gao > Assignee: Tomasz Adamski > Priority: Major > Labels: downstream_dependency > Fix For: 22.0.0.Beta1 > > > Class loader leaks when JDBC driver as jar deployment is undeloyed. It will eventually leads to Metaspace out of memory error when "-XX:MaxMetaspaceSize" option is specified. > > Normally JDBC driver is not undeloyed or redeployed by user frequently, but configuration reload command, which is regularly used, also triggers JDBC driver redeployment and cause class loader leak. > JDBC driver should be deregistered while undeloying. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13969) signature test failures in Expression Language (jakarta.el)

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-13969?page=com.atlassian.jira.plugi... ] Scott Marlow commented on WFLY-13969: ------------------------------------- Changes look good: {quote} Passed packages listed below: ... jakarta.el(static mode) jakarta.el(reflection mode) {quote} Will go ahead an push an initial release soon. > signature test failures in Expression Language (jakarta.el) > ----------------------------------------------------------- > > Key: WFLY-13969 > URL: https://issues.redhat.com/browse/WFLY-13969 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: Scott Marlow > Assignee: Parul Sharma > Priority: Major > Labels: EE9 > > jakarta.el > {quote} > Missing Methods > [javatest.batch] --------------- > [javatest.batch] > [javatest.batch] jakarta.el.ELContext: method public java.lang.Object jakarta.el.ELContext.getContext(java.lang.Class<?>) > [javatest.batch] jakarta.el.ELContext: method public void jakarta.el.ELContext.putContext(java.lang.Class<?>,java.lang.Object) > [javatest.batch] jakarta.el.StandardELContext: method public java.lang.Object jakarta.el.StandardELContext.getContext(java.lang.Class<?>) > [javatest.batch] jakarta.el.StandardELContext: method public void jakarta.el.StandardELContext.putContext(java.lang.Class<?>,java.lang.Object) > [javatest.batch] > [javatest.batch] Added Methods > [javatest.batch] ------------- > [javatest.batch] > [javatest.batch] jakarta.el.ELContext: method public java.lang.Object jakarta.el.ELContext.getContext(java.lang.Class) > [javatest.batch] jakarta.el.ELContext: method public void jakarta.el.ELContext.putContext(java.lang.Class,java.lang.Object) > [javatest.batch] jakarta.el.StandardELContext: method public java.lang.Object jakarta.el.StandardELContext.getContext(java.lang.Class) > [javatest.batch] jakarta.el.StandardELContext: method public void jakarta.el.StandardELContext.putContext(java.lang.Class,java.lang.Object) > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 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 December 2020