December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4776) NPE in EmbeddedServer for version/help arguments

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-4776: -------------------------------------------- Summary: NPE in EmbeddedServer for version/help arguments Key: WFCORE-4776 URL: https://issues.redhat.com/browse/WFCORE-4776 Project: WildFly Core Issue Type: Bug Components: Embedded Reporter: Jean Francois Denise Assignee: Jean Francois Denise -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12751) Move base layers to the full galleon feature pack

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFLY-12751?page=com.atlassian.jira.plugi... ] Jean Francois Denise updated WFLY-12751: ---------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12851 > Move base layers to the full galleon feature pack > ------------------------------------------------- > > Key: WFLY-12751 > URL: https://issues.redhat.com/browse/WFLY-12751 > Project: WildFly > Issue Type: Feature Request > Components: Build System, Clustering > Reporter: Brian Stansberry > Assignee: Jean Francois Denise > Priority: Major > > Move the web-clustering, cloud-server, jaxrs-server and datasources-web-server layers from https://github.com/wildfly/wildfly/tree/master/testsuite/test-feature-pac... to the galleon-pack module so non-test users can use it. It got put in test-feature-pack because it came in late for WF 18. > [~jdenise] you said this needed some form of adjustment, which is why I assigned this to you. > [~pferraro] FYI. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFWIP-287: --------------------------------- Workaround Description: Use globally scoped configuration for Hystrix and not bundled within deployments - which is the general recommendation regardless. Workaround: Workaround Exists > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFWIP-287: -------------------------------------- Making this critical as multiple deployments is not fully supported and workaround exists. > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFWIP-287: --------------------------------- Priority: Critical (was: Blocker) > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFWIP-287: -------------------------------------- It appears this is MP Config issue as [~mnovak] pointed out rather than the initialization issue – https://github.com/smallrye/smallrye-metrics/issues/216. Switching components. > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Blocker > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFWIP-287: --------------------------------- Component/s: MP Config (was: MP Fault Tolerance) > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Blocker > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFWIP-287: --------------------------------- Steps to Reproduce: *NOT 100% reproducer will it issue in 50% of run as it's random which MP FT module from EAR gets loaded* Steps to reproduce: * Build Wildfly with MP FT: ** https://github.com/rhusar/wildfly/tree/WFLY-12590 ** Commit: 3ff9787ca147a45c1651fe1946b02c07c0a6ad15 * Run the test by (provide path to build Wildfly server): {code} git clone git@github.com:mnovak1/eap-microprofile-test-suite.git cd eap-microprofile-test-suite git checkout EAP7-1347 # checkout the right branch mvn clean verify -DfailIfNoTests=false -Darquillian.deploymentExportPath=target/deployments/ -Djboss.home=$WILDFLY_HOME -P mp-ft -Dtest=MultipleFaultToleranceModuleEarTest#testFirstModuleConfiguresHystrix {code} was: *NOT 100% reproducer will it issue in 50% of run as it's random which MP FT module from EAR gets loaded* Steps to reproduce: * Build Wildfly with MP FT: ** https://github.com/rhusar/wildfly/tree/WFLY-12590 ** Commit: 3ff9787ca147a45c1651fe1946b02c07c0a6ad15 * Run the test by (provide path to build Wildfly server): {code} git clone git@github.com:mnovak1/eap-microprofile-test-suite.git cd eap-microprofile-test-suite mvn clean verify -DfailIfNoTests=false -Darquillian.deploymentExportPath=target/deployments/ -Djboss.home=$WILDFLY_HOME -P mp-ft -Dtest=MultipleFaultToleranceModuleEarTest#testFirstModuleConfiguresHystrix {code} > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Blocker > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFWIP-287: -------------------------------------- [~mnovak] Also, its possible that the {{initialize-in-order}} doesn't work in general – could you check with non-FT deployment? In that case its not a MP FT issue. > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Blocker > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFWIP-287: -------------------------------------- [~mnovak] This is not a viable configuration strategy, for multideployment like this the use case as designed is to scope those properties globally or have all deployments bring the same configuration. The {{initialize-in-order}} is not going to help if {{second-module}} depends on the {{first-module}}. > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Fault Tolerance > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Blocker > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- 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