April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11946) Remove unneeded dependencies from OpenJPA module

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-11946?page=com.atlassian.jira.plugin... ] Scott Marlow closed WFLY-11946. ------------------------------- > Remove unneeded dependencies from OpenJPA module > ------------------------------------------------ > > Key: WFLY-11946 > URL: https://issues.jboss.org/browse/WFLY-11946 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 17.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11950) Error code:IJ000453-Unable to get managed connection for java:/my_data_source

by Vandana Thota (Jira)

Vandana Thota created WFLY-11950: ------------------------------------ Summary: Error code:IJ000453-Unable to get managed connection for java:/my_data_source Key: WFLY-11950 URL: https://issues.jboss.org/browse/WFLY-11950 Project: WildFly Issue Type: Bug Environment: wildfly 11 final Data source min and max pool is 10 and 200 respectively Reporter: Vandana Thota Assignee: Brian Stansberry We have internal server error and have seen below issue and what we can do to resolve this issue Env : wildfly -11-0-0 final XA data source Min-pool :10 and max-pool :200 ERROR [io.undertow.request] (default task-19) UT005023: Exception handling request to /kohls-app/: javax.servlet.ServletException: com.vaadin.server.ServiceException: java.lang.RuntimeException: CustomHostSystem.constructor: failed with error: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/my_data_source at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:381) at innowake.maxenso.runtime.client.vaadin.Servlet.service(Servlet.java:125) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129) at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:130) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.elytron.web.undertow.server.ElytronRunAsHandler.lambda$handleRequest$1(ElytronRunAsHandler.java:68) at org.wildfly.security.auth.server.FlexibleIdentityAssociation.runAsFunctionEx(FlexibleIdentityAssociation.java:101) at org.wildfly.security.auth.server.Scoped.runAsFunctionEx(Scoped.java:150) at org.wildfly.security.auth.server.Scoped.runAs(Scoped.java:62) at org.wildfly.elytron.web.undertow.server.ElytronRunAsHandler.handleRequest(ElytronRunAsHandler.java:67) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.MetricsHandler.handleRequest(MetricsHandler.java:64) at io.undertow.servlet.core.MetricsChainHandler.handleRequest(MetricsChainHandler.java:59) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:326) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-704) Review jenkins2 settings

by Filip Brychta (Jira)

Filip Brychta created SWSQE-704: ----------------------------------- Summary: Review jenkins2 settings Key: SWSQE-704 URL: https://issues.jboss.org/browse/SWSQE-704 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta Check https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/configure for kubernetes settings and usage of b21.jonqe.lab.eng.bos.redhat.com which is now part of prod cluster. Also update https://mojo.redhat.com/docs/DOC-1168333 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-702) Report code coverage for system tests in jenkins job via cobertura plugin

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-702?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-702: ------------------------------------- It's done for https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/run-kiali-e2e-t... > Report code coverage for system tests in jenkins job via cobertura plugin > ------------------------------------------------------------------------- > > Key: SWSQE-702 > URL: https://issues.jboss.org/browse/SWSQE-702 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > https://docs.engineering.redhat.com/display/CentralCI/Golang+Code+Coverag... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11892) With Elytron the legacy RunAsLoginModule no longer works

by Brian Loss (Jira)

[ https://issues.jboss.org/browse/WFLY-11892?page=com.atlassian.jira.plugin... ] Brian Loss commented on WFLY-11892: ----------------------------------- Ok, thanks. I think I can work with that. I have also noticed I can just disable Elytron entirely and that seems to work for my application configuration. > With Elytron the legacy RunAsLoginModule no longer works > -------------------------------------------------------- > > Key: WFLY-11892 > URL: https://issues.jboss.org/browse/WFLY-11892 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Loss > Assignee: Ivo Studensky > Priority: Major > > When using the legacy jaas configuration, the RunAsLoginModule no longer works. While the module is invoked, there is no SecurityContext, so the login module cannot do any work and the temporary identity is never pushed on to the stack. > It seems that previously, [this line|https://github.com/wildfly/wildfly/blob/16.0.0.Final/undertow/src/ma...] was responsible for setting up the security context. However, that action is no longer executed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-686) UI Automation - Refresh Buttons

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-686?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan reassigned SWSQE-686: ------------------------------------ Assignee: Hayk Hovsepyan > UI Automation - Refresh Buttons > ------------------------------- > > Key: SWSQE-686 > URL: https://issues.jboss.org/browse/SWSQE-686 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Verify Refresh Buttons on all List and Details pages. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-686) UI Automation - Refresh Buttons

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-686?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-686: --------------------------------- Sprint: Kiali Sprint #20 > UI Automation - Refresh Buttons > ------------------------------- > > Key: SWSQE-686 > URL: https://issues.jboss.org/browse/SWSQE-686 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > > Verify Refresh Buttons on all List and Details pages. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-607) Run UI Tests on Kiali on OCP4

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-607?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-607. ---------------------------------- Resolution: Done > Run UI Tests on Kiali on OCP4 > ----------------------------- > > Key: SWSQE-607 > URL: https://issues.jboss.org/browse/SWSQE-607 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Currently Kiali UI tests are failing to run on OCP4/AWS because there is OpenShift REST API Python Client library used in tests which have a API problem with OCP4. > We need to have some solution/workaround to make sure that API works. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3843) DMN Editor Decision Navigator differentiate icons for DRGElement

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3843?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3843: ------------------------------------------- [~tirelli] okay > DMN Editor Decision Navigator differentiate icons for DRGElement > ---------------------------------------------------------------- > > Key: DROOLS-3843 > URL: https://issues.jboss.org/browse/DROOLS-3843 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools, ux_needed > Attachments: dmn-icons.png, image-2019-04-03-10-38-39-270.png > > > In this example: > !image-2019-04-03-10-38-39-270.png|thumbnail! > The 1st one is a Decision, the other are Input Data. > Experienced DMN practitioner may know that a decision logic can only happen to Decision or BKM node, hence one could distinguish potential Input data node by not having decision logic (context in the example). But also what about Decision or BKM for which you didn't write the decision logic yet? > PLease consider distinguished icon for DRG Elements. > For example > leave Input Data with the filled circle > Decision: filled square > BKM: filled trapezoid. > Thanks -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11892) With Elytron the legacy RunAsLoginModule no longer works

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-11892?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFLY-11892: ----------------------------------------- The referenced ejb-security-jaas-quickstart is making use of a WildFly Elytron SecurityDomain and SecurityContext to legacy PicketBox security services are no longer available within that deployment. To continue to make use of legacy approaches such as the RunAs LoginModule the application should be deployed to use PicketBox exclusively, i.e. there should be no application-security-domain mapping for that deployment in either the ejb or undertow subsystems, the PicketBox SecurityContext should then be available. > With Elytron the legacy RunAsLoginModule no longer works > -------------------------------------------------------- > > Key: WFLY-11892 > URL: https://issues.jboss.org/browse/WFLY-11892 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Loss > Assignee: Ivo Studensky > Priority: Major > > When using the legacy jaas configuration, the RunAsLoginModule no longer works. While the module is invoked, there is no SecurityContext, so the login module cannot do any work and the temporary identity is never pushed on to the stack. > It seems that previously, [this line|https://github.com/wildfly/wildfly/blob/16.0.0.Final/undertow/src/ma...] was responsible for setting up the security context. However, that action is no longer executed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 April 2019