December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14193) Extend session expiration tests to cover expiration during server startup.

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-14193: ----------------------------------- Summary: Extend session expiration tests to cover expiration during server startup. Key: WFLY-14193 URL: https://issues.redhat.com/browse/WFLY-14193 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: 22.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro See linked issue containing reproducer on which to base test coverage. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (AG-153) Application blocked getting Connection from shared handler cache.

by Luis Barreiro (Jira)

[ https://issues.redhat.com/browse/AG-153?page=com.atlassian.jira.plugin.sy... ] Luis Barreiro commented on AG-153: ---------------------------------- Thanks for the report [~whitingjr] More info is needed in order to understand this issue. At least a thread dump including the Agroal thread(s) and would be very nice if you could provide pool statistics as well. With the info provided, is just not clear if there are connections on the pool or not, and if they are, what state they are in. The configuration of the pool is required too. It's wise to run with a non-zero value of `acquisitionTimeout`. Leak detection is also advisable, even though Agroal does not remove leaking connections automatically, > Application blocked getting Connection from shared handler cache. > ----------------------------------------------------------------- > > Key: AG-153 > URL: https://issues.redhat.com/browse/AG-153 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 1.8 > Reporter: Jeremy Whiting > Assignee: Luis Barreiro > Priority: Major > Attachments: jstack-tree.txt, summary-of-getConnection-method-calls.txt > > > I am inspecting an application that stopped nearly all processing. > A jstack dump reveals one of the thread pools (40 threads) has all threads blocked waiting for a database Connection. See the "summary-of-getConnection-method-calls.txt" file. > -There are no other threads that already have a connection leased out.- -- 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 commented on WFLY-14189: ---------------------------------------------- This is my standalone :[^standalone-full-ha.new.xml] ^I activated Elytron security in both undertow and EJB. Elytron works for me for servlets and EJBs in general. The only thing is not working is the annotation (used for Startup EJBs). Let me know if I missed something.^ ^Thank you in advance^ > 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: Diana Vilkolakova > Priority: Major > Labels: ejb, elytron, regression, runas, security, startup > Fix For: 21.0.2.Final > > Attachments: standalone-full-ha.new.xml, 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: ----------------------------------------- Attachment: standalone-full-ha.new.xml > 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: Diana Vilkolakova > Priority: Major > Labels: ejb, elytron, regression, runas, security, startup > Fix For: 21.0.2.Final > > Attachments: standalone-full-ha.new.xml, 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 Diana Vilkolakova (Jira)

[ https://issues.redhat.com/browse/WFLY-14189?page=com.atlassian.jira.plugi... ] Diana Vilkolakova reassigned WFLY-14189: ---------------------------------------- Assignee: Diana Vilkolakova (was: Darran Lofthouse) > 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: Diana Vilkolakova > 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] (SWSQE-1168) Document alternatives for PSI OpenStack

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1168?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1168. ---------------------------------- Resolution: Done > Document alternatives for PSI OpenStack > --------------------------------------- > > Key: SWSQE-1168 > URL: https://issues.redhat.com/browse/SWSQE-1168 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > When the PSI OpenStack is down, we need to use something else to provisioning OCP clusters. > We need to document options: > * AWS > * https://quicklab.upshift.redhat.com/clusters > * bot on coreos slack -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-482) Add log4j2 support for WildFly

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-482?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-482: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4384, https://github.com/wildfly/wildfly-core/pull/4424 (was: https://github.com/wildfly/wildfly-core/pull/4384) > Add log4j2 support for WildFly > ------------------------------ > > Key: WFCORE-482 > URL: https://issues.redhat.com/browse/WFCORE-482 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Environment: Spring 3, Hibernate, Wicket, JBoss AS7 > Reporter: Amarkanth Ranganamayna > Assignee: James Perkins > Priority: Major > Fix For: 14.0.0.Beta3 > > > I am trying to use Flume Appender which comes with Log4j2 (log4j 1.x doesn't support flume appender) (AND) inorder to acheive this, I am looking at how to configure JBoss AS7 to use log4j2. > Looks like Jboss AS7 by default use log4j 1.x > Are you guys already working on using log4j2 ? > If NOT, can you please suggest how to configure Jboss AS7 such that it picks up "log4j2.xml" file and doesn't use its own logging. > Thanks, > Amar -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14191) Internal Error accessing EJB Runtime option at Management Console

by Bartosz Spyrko-Smietanko (Jira)

Bartosz Spyrko-Smietanko created WFLY-14191: ----------------------------------------------- Summary: Internal Error accessing EJB Runtime option at Management Console Key: WFLY-14191 URL: https://issues.redhat.com/browse/WFLY-14191 Project: WildFly Issue Type: Bug Components: Management Affects Versions: 21.0.1.Final Reporter: Bartosz Spyrko-Smietanko Assignee: Bartosz Spyrko-Smietanko Hi, It seems that EJB Runtime monitor at Management Console is broken. I cannot monitor EJBs deployed at server because an error happens when the option is selected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (AG-153) Application blocked getting Connection from shared handler cache.

by Jeremy Whiting (Jira)

[ https://issues.redhat.com/browse/AG-153?page=com.atlassian.jira.plugin.sy... ] Jeremy Whiting updated AG-153: ------------------------------ Description: I am inspecting an application that stopped nearly all processing. A jstack dump reveals one of the thread pools (40 threads) has all threads blocked waiting for a database Connection. See the "summary-of-getConnection-method-calls.txt" file. -There are no other threads that already have a connection leased out.- was: I am inspecting an application that stopped nearly all processing. A jstack dump reveals one of the thread pools (40 threads) has all threads blocked waiting for a database Connection. See the "summary-of-getConnection-method-calls.txt" file. There are no other threads that already have a connection leased out. > Application blocked getting Connection from shared handler cache. > ----------------------------------------------------------------- > > Key: AG-153 > URL: https://issues.redhat.com/browse/AG-153 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 1.8 > Reporter: Jeremy Whiting > Assignee: Luis Barreiro > Priority: Major > Attachments: jstack-tree.txt, summary-of-getConnection-method-calls.txt > > > I am inspecting an application that stopped nearly all processing. > A jstack dump reveals one of the thread pools (40 threads) has all threads blocked waiting for a database Connection. See the "summary-of-getConnection-method-calls.txt" file. > -There are no other threads that already have a connection leased out.- -- 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 Diana Vilkolakova (Jira)

[ https://issues.redhat.com/browse/WFLY-14189?page=com.atlassian.jira.plugi... ] Diana Vilkolakova commented on WFLY-14189: ------------------------------------------ [~alessandromoscatelli] Thank you for the sample project. Could you share configuration of the server as well? It seems that the Elytron security domain is not getting picked up. > 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

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