December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4781) Ability to enable shutdown operation for EmbeddedServer

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4781?page=com.atlassian.jira.plug... ] Jean Francois Denise commented on WFCORE-4781: ---------------------------------------------- [~jamezp], +1 on an Handler passed to the EmbeddedServer that gets called when shutdown is received. > Ability to enable shutdown operation for EmbeddedServer > ------------------------------------------------------- > > Key: WFCORE-4781 > URL: https://issues.redhat.com/browse/WFCORE-4781 > Project: WildFly Core > Issue Type: Enhancement > Components: Embedded > Affects Versions: 11.0.0.Beta5 > Reporter: Jean Francois Denise > Assignee: James Perkins > Priority: Major > > Having the shutdown operation available for embedded is needed when the embedder process and embedded server shutdown phase are bound. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1043) Add possibility to provision RHEL 7 OCP workers

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1043?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1043. ---------------------------------- Resolution: Done https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/infra-jobs/job... now supports RHEL workers > Add possibility to provision RHEL 7 OCP workers > ----------------------------------------------- > > Key: SWSQE-1043 > URL: https://issues.redhat.com/browse/SWSQE-1043 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Istio team needs to test OCP cluster which contains also RHEL 7 workers. We need to update our provisioning jobs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4781) Ability to enable shutdown operation for EmbeddedServer

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4781?page=com.atlassian.jira.plug... ] James Perkins commented on WFCORE-4781: --------------------------------------- I agree. Maybe something like a {{StandaloneServer.start(Runnable shutdownHandler)}}. In other words some way to tell the embedded server to invoke {{stop()}} if a shutdown operation has been invoked. > Ability to enable shutdown operation for EmbeddedServer > ------------------------------------------------------- > > Key: WFCORE-4781 > URL: https://issues.redhat.com/browse/WFCORE-4781 > Project: WildFly Core > Issue Type: Enhancement > Components: Embedded > Affects Versions: 11.0.0.Beta5 > Reporter: Jean Francois Denise > Assignee: James Perkins > Priority: Major > > Having the shutdown operation available for embedded is needed when the embedder process and embedded server shutdown phase are bound. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12899) Failing JMXPropertyEditorsTestCase in 18.0.0.Final

by James Crowley (Jira)

[ https://issues.redhat.com/browse/WFLY-12899?page=com.atlassian.jira.plugi... ] James Crowley commented on WFLY-12899: -------------------------------------- [~brian.stansberry] Thanks for linking the other snippet of code. I looked at that before, and figured the value of USER_SYS_PROP should be USER since were running the test on Linux. I am not sure why setting USER=jenkins in the test would have effect on this. I am not 100% if that is setting the env.USER in the test, especially since the test is running in a Docker container. Should env.USER be set to something? Or should it be blank? > Failing JMXPropertyEditorsTestCase in 18.0.0.Final > -------------------------------------------------- > > Key: WFLY-12899 > URL: https://issues.redhat.com/browse/WFLY-12899 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 18.0.0.Final > Reporter: James Crowley > Priority: Major > > When calling "./mvnw install -DallTests", it gets up to the JMXPropertyEditorsTestCase and fails with this error, "Caused by: java.lang.IllegalStateException: Failed to resolve expression: env.USER"}}}}". > Looking at the source code for the test [here|https://github.com/wildfly/wildfly/blob/1bf993be72b570a0c780a58ba05c...], it looks like USER is suppose to be defined by USER_SYS_PROP. > I am not sure what the problem is but I know it is failing somewhere in the above test. > You can see the full log in the in Adopt's test [here|https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/1436/conso...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4781) Ability to enable shutdown operation for EmbeddedServer

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4781?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-4781: ------------------------------------------ This should be a bootable jar requirement with embedded server behavior perhaps an implementation detail. > Ability to enable shutdown operation for EmbeddedServer > ------------------------------------------------------- > > Key: WFCORE-4781 > URL: https://issues.redhat.com/browse/WFCORE-4781 > Project: WildFly Core > Issue Type: Enhancement > Components: Embedded > Affects Versions: 11.0.0.Beta5 > Reporter: Jean Francois Denise > Assignee: James Perkins > Priority: Major > > Having the shutdown operation available for embedded is needed when the embedder process and embedded server shutdown phase are bound. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12899) Failing JMXPropertyEditorsTestCase in 18.0.0.Final

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12899?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-12899: ----------------------------------------- [~james-crowley-ibm] The test assumes an environment variable identifying the user will be available in the server process. What env var it expects depends on the type of system. The logic to work out what env var to check is at https://github.com/wildfly/wildfly/blob/1bf993be72b570a0c780a58ba05cabafe... If there's some additional logic that can be added there to find a property that will be set in your env we could look at that. Otherwise we'd need to work out how to disable that part of the test, or the test altogether, if there is no property. Looking at the log you linked I see '[2019-12-17T02:14:30.524Z] USER=jenkins' so perhaps this is just a matter of your test setup propagating that env var? > Failing JMXPropertyEditorsTestCase in 18.0.0.Final > -------------------------------------------------- > > Key: WFLY-12899 > URL: https://issues.redhat.com/browse/WFLY-12899 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 18.0.0.Final > Reporter: James Crowley > Priority: Major > > When calling "./mvnw install -DallTests", it gets up to the JMXPropertyEditorsTestCase and fails with this error, "Caused by: java.lang.IllegalStateException: Failed to resolve expression: env.USER"}}}}". > Looking at the source code for the test [here|https://github.com/wildfly/wildfly/blob/1bf993be72b570a0c780a58ba05c...], it looks like USER is suppose to be defined by USER_SYS_PROP. > I am not sure what the problem is but I know it is failing somewhere in the above test. > You can see the full log in the in Adopt's test [here|https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/1436/conso...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1041) Automate https://github.com/kiali/kiali/issues/1892

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1041?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1041: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/232 > Automate https://github.com/kiali/kiali/issues/1892 > --------------------------------------------------- > > Key: SWSQE-1041 > URL: https://issues.redhat.com/browse/SWSQE-1041 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4877) Upgrade ECJ to make it Java 11 compatible

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4877?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4877. --------------------------------- Fix Version/s: 7.32.0.Final Resolution: Done Fixed by https://github.com/kiegroup/droolsjbpm-build-bootstrap/commit/30cb3be430c... https://github.com/kiegroup/drools/commit/002ef38751ee17448d0f328207e512e... https://github.com/kiegroup/droolsjbpm-integration/commit/6593a05c86bab0c... > Upgrade ECJ to make it Java 11 compatible > ----------------------------------------- > > Key: DROOLS-4877 > URL: https://issues.redhat.com/browse/DROOLS-4877 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > Labels: java11 > Fix For: 7.32.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12902) [GSS](7.1.z) Improper handling of application exceptions on asynchronous ejb invocations

by Brad Maxwell (Jira)

Brad Maxwell created WFLY-12902: ----------------------------------- Summary: [GSS](7.1.z) Improper handling of application exceptions on asynchronous ejb invocations Key: WFLY-12902 URL: https://issues.redhat.com/browse/WFLY-12902 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 11.0.0.Final Reporter: Brad Maxwell Fix For: 12.0.0.Beta1, 12.0.0.Final If an asynchronous invocation of an ejb method throws an application exception (declared exception) then the returned future will always return false on isDone(). That means: the client will never know that the operation has finished (unscuccessfully) unless get() is called which would rethrow the original exception. This behavior has changed from wildfly 10.1.0.Final to 11.0.0.Final. I pretty sure that the problem is in org.jboss.as.ejb3.component.interceptors.AsyncInvocationTask. The isDone Method is implemented like this: {noformat} @Override public boolean isDone() { return status == ST_DONE; } {noformat} But status can be one of: {noformat} private static final int ST_RUNNING = 0; private static final int ST_DONE = 1; private static final int ST_CANCELLED = 2; private static final int ST_FAILED = 3; {noformat} And and exception sets the status to {noformat} private synchronized void setFailed(final Exception e) { this.failed = e; status = ST_FAILED; done(); } {noformat} So it's pretty obvious. The javadoc on java.util.concurrent.Future states: {quote} Completion may be due to normal termination, an exception, or cancellation -- in all of these cases, this method will return true. {quote} So the isDone() method should look more like this: {noformat} @Override public boolean isDone() { return status == ST_DONE || status == ST_FAILED || status == ST_CANCELLED; } {noformat} In wildfly 10, there was a single boolean variable "done" which was set to true in all three cases: * cancel() * setResult(...) and * setFailed(...) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1401) Avoid flushing pooled connections when matchManagedConnections returns no match

by Stephen Fikes (Jira)

Stephen Fikes created JBJCA-1401: ------------------------------------ Summary: Avoid flushing pooled connections when matchManagedConnections returns no match Key: JBJCA-1401 URL: https://issues.redhat.com/browse/JBJCA-1401 Project: IronJacamar Issue Type: Feature Request Components: Core Affects Versions: 1.4.10 Reporter: Stephen Fikes When no match is returned by the resource adapter implementation of [ManagedConnectionFactory.matchManagedConnections|https://docs.oracle.com/...], the IronJacamar pool implementation [terminates non-matching connections|https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1...]. There may be cases where resource adapters return {{null}} for cases where no connection matches but where the connections in the match set are not invalid though a different connection needs to be created based on the calling context ({{ConnectionRequestInfo}}). A mechanism to avoid the termination of non-matching connections is needed to support such cases. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 2019