September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12604) The web-clustering layer needs to ensure the org.wildfly.cluster.web.undertow module is provisioned

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12604: --------------------------------------- Summary: The web-clustering layer needs to ensure the org.wildfly.cluster.web.undertow module is provisioned Key: WFLY-12604 URL: https://issues.jboss.org/browse/WFLY-12604 Project: WildFly Issue Type: Bug Components: Build System, Clustering, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry The WF testsuite includes a test-feature-pack which provide a Galleon feature pack with layers intended to mirror higher level layers that will be used in the WildFly s2i image, with the goal to make those easy to use in WildFly testsuite tests of slimmed servers. See WFLY-12507 and WFLY-12304. One of these layers is 'web-clustering' which is meant to decorate a server provisioned with an undertow web server to add web clustering functionality. Testing reveals a server provisioned with this combination is missing the org.wildfly.cluster.web.undertow module. This is because the chain of module deps from the distributable-web extension module does not force its inclusion, because 'undertow' is an optional impl detail. And the chain of module deps from the undertow extension module does not force its inclusion, because clustering is an optional feature. So something needs to force its inclusion, and a way I see to do it is to have the web-clustering layer do it. That layer knows it wants undertow and it knows it wants clustering. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12603) Add Galleon layers testing to testsuite/integration/clustering

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12603: --------------------------------------- Summary: Add Galleon layers testing to testsuite/integration/clustering Key: WFLY-12603 URL: https://issues.jboss.org/browse/WFLY-12603 Project: WildFly Issue Type: Task Components: Build System, Clustering, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Follow up on the WFLY-12394 work by adding a profile triggered by -Dts.layers to testsuite/integration/clustering. Provision a slimmed server using the test-feature-pack cloud-server + web-clustering layers and execute the portions of the testsuite that are compatible with such a server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12601) Eliminate StabilityMonitor usages in clustering subsystem

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12601?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-12601: ------------------------------------- [~ropalka] Thanks for the documentation. I think I understand the crux of the issue now. There are 2 clustering constructs that currently use StabilityMonitor: 1. ActiveServiceSupplier/PassiveServiceSupplier - essentially, a given metric value needs to be computed within the start() method of the Service that depends on the service that supplies the source of a given metric. 2. ServiceLifecycle - this object is responsible for starting/stopping a given service in response to a change in cluster membership. There is no attempt to obtain service values, so I believe this class should not be affected by the race conditions you described above. Do the modifications to this class in the attached PR look OK to you? > Eliminate StabilityMonitor usages in clustering subsystem > --------------------------------------------------------- > > Key: WFLY-12601 > URL: https://issues.jboss.org/browse/WFLY-12601 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Richard Opalka > Assignee: Paul Ferraro > Priority: Major > Fix For: 19.0.0.Beta1 > > Attachments: ServiceSupplier.png > > > Clustering needs to eliminate usages of StabilityMonitor because SM is not reliable. > It is possible that SM will prematurely inform about achieved stability even if it is not true. > The reason is SM is not propagated up the dependencies chain and thus it may report > about achieved stability even in case dependencies chain didn't finish its processing yet > and 'real' stability wasn't achieved yet. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-208) openshift-common.sh executes CLI command against non-existing standalone.xml

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFWIP-208?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFWIP-208: -------------------------------------- Assignee: Jean Francois Denise (was: Brian Stansberry) > openshift-common.sh executes CLI command against non-existing standalone.xml > ---------------------------------------------------------------------------- > > Key: WFWIP-208 > URL: https://issues.jboss.org/browse/WFWIP-208 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Blocker > > Using image {{docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP7-1216}} we are unable to build an application deployment that will need to setup a datasource, eg. executed with properties: > {code:java} > CUSTOM_INSTALL_DIRECTORIES=mypg_module,mypg_driver > DRIVERS=MYPG > MYPG_DRIVER_NAME=mypg > MYPG_DRIVER_MODULE=org.mypg > MYPG_XA_DATASOURCE_CLASS=org.postgresql.xa.PGXADataSource > {code} > The error in build log is (when executed with SCRIPT_DEBUG=true): > {code:java} > ... > + CLI_SCRIPT_FILE_FOR_EMBEDDED=/tmp/cli-configuration-script-1569488395.cli > + echo 'embed-server --timeout=30 --server-config=standalone.xml --std-out=echo' > + cat /opt/eap/bin/launch/drivers.cli > + echo '' > + echo stop-embedded-server > + echo 'Configuring the server using embedded server' > Configuring the server using embedded server > ++ date +%s%3N > + start=1569488395421 > + eval /opt/eap/bin/jboss-cli.sh --file=/tmp/cli-configuration-script-1569488395.cli --properties=/tmp/cli-script-property.cli '&>/tmp/cli-script-output.cli' > ++ /opt/eap/bin/jboss-cli.sh --file=/tmp/cli-configuration-script-1569488395.cli --properties=/tmp/cli-script-property.cli > error: build error: non-zero (13) exit code from docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... > {code} > The problematic script is /opt/eap/bin/launch/openshift-common.sh. > The problem here is that the script is trying to modify standalone.xml but there is no such file at the time of the execution, only standalone.openshift.xml exists. > I can also see that the config name is looked up in openshift-common.sh by: > {code:java} > SERVER_CONFIG=${WILDFLY_SERVER_CONFIGURATION:-standalone.xml} > {code} > and this variable is set in launch/launch-config.sh: > {code:java} > WILDFLY_SERVER_CONFIGURATION=standalone-openshift.xml > {code} > but according to build log launch/launch-config.sh is never executed or sourced so the wrong default value is used. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4481) [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4481?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4481: ------------------------------------------- [~karreiro] I posted a first pass at a click-thru. I have some questions regarding editing a converted type, and how the conversion mappings might work, so will follow-up with you. > [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX > ------------------------------------------------------------------------------ > > Key: DROOLS-4481 > URL: https://issues.jboss.org/browse/DROOLS-4481 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: 2019-08-26 17.48.30.gif, Screen Shot 2019-08-26 at 18.11.01.png > > > *Requirements* > It should be possible to generate data types from imported data models (java classes). > * As a user I want to be able to use data type definitions that are structured similar to Java data object models (classes) that I have defined externally. > * As I user I want to be able to edit and update data objects that have been converted to data types, so that I can manually update the definitions. > Import/convert data objects: > * 5 levels deep can “introspect” and convert data model, beyond that the data type would be “any.” > * Import (convert) only within the Data Type tab, this is not a feature of the Import/Include function as import DO’s is not supported in the DMN spec. -- > *Current scenario* > Currently, users can create Data Objects on Business Central. See: > !2019-08-26 17.48.30.gif|width=600! > However users cannot re-use Data Objects as Data Types. > --- > *Description* > Data Objects (DO) are pretty similar to DMN Data Types (DT). So, would be great to import the DO above as a DMN DT like the following one: > !Screen Shot 2019-08-26 at 18.11.01.png|width=600! > --- > *Questions to clarify at requirement level* > 1) Some DOs can be quite complex and some fields can be impossible to guess. > - Person > -- name (Some strange type) > -- age (Integer) > What should we do? Import name as "Any"? Remove the name field? Or block the Person type? > 2) Do we need a specific component to import Data Objects as Data Types? Couldn't we just add Data Objects in the type dropdown, but use a different category (Default, Custom Data Types, Data Objects)? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-124) Add marker support

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-124?page=com.atlassian.jira.plugin... ] James Perkins commented on LOGMGR-124: -------------------------------------- Well not really. We have a [log4j|https://github.com/jboss-logging/log4j-jboss-logmanager] where we replace some of the log manager parts to write to JBoss Log Manager. The JBoss Log Manager is really just an extension of JUL which is why it has some of the limitations. It's more like APP -> SLF4J -> JBLM or APP -> log4j -> JBLM. Essentially the JBoss Log Manager is the last stop. > Add marker support > ------------------ > > Key: LOGMGR-124 > URL: https://issues.jboss.org/browse/LOGMGR-124 > Project: JBoss Log Manager > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.2.Final > Reporter: Rob Heine > Priority: Optional > > The logging engine currently (talking about the one included in WF-9) does not support Markers (like in implementations like "logback" and/or "log4j2"). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-124) Add marker support

by Andreas Liebscher (Jira)

[ https://issues.jboss.org/browse/LOGMGR-124?page=com.atlassian.jira.plugin... ] Andreas Liebscher commented on LOGMGR-124: ------------------------------------------ Thanx for the explaination. As I understand, the JBoss Log Manager can be configured to use log4j and that can use logback. So it should be possible to use logback as implementation, but Marker support is not forwarded, APP -> SLF4J -> LogManager -> log4j -> Logback > Add marker support > ------------------ > > Key: LOGMGR-124 > URL: https://issues.jboss.org/browse/LOGMGR-124 > Project: JBoss Log Manager > Issue Type: Feature Request > Components: core > Affects Versions: 2.0.2.Final > Reporter: Rob Heine > Priority: Optional > > The logging engine currently (talking about the one included in WF-9) does not support Markers (like in implementations like "logback" and/or "log4j2"). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12602) Translated clustering attribute do not correctly translate undefine-attribute operation.

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12602?page=com.atlassian.jira.plugin... ] Paul Ferraro closed WFLY-12602. ------------------------------- Resolution: Rejected Actually, this already works! > Translated clustering attribute do not correctly translate undefine-attribute operation. > ---------------------------------------------------------------------------------------- > > Key: WFLY-12602 > URL: https://issues.jboss.org/browse/WFLY-12602 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > Clustering subsystems make use of generic operations handlers for handling things like: > stats-enabled -> statistics-enabled > While the read-attribute and write-attribute operations are correctly handled, the undefine-attribute operation is not. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4576) Data object selector Search widget not enabled in saved tests

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4576?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4576: ------------------------------------------- cc [~yamer] > Data object selector Search widget not enabled in saved tests > ------------------------------------------------------------- > > Key: DROOLS-4576 > URL: https://issues.jboss.org/browse/DROOLS-4576 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Gabriele Cardosi > Priority: Major > Attachments: 2019-09-27 13.36.19.gif > > > The Search widget doesn't work (isn't accessible/enabled) in a test template that has been setup/saved, it does work in a new test though. Example attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4576) Data object selector Search widget not enabled in saved tests

by Elizabeth Clayton (Jira)

Elizabeth Clayton created DROOLS-4576: ----------------------------------------- Summary: Data object selector Search widget not enabled in saved tests Key: DROOLS-4576 URL: https://issues.jboss.org/browse/DROOLS-4576 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Elizabeth Clayton Assignee: Gabriele Cardosi Attachments: 2019-09-27 13.36.19.gif The Search widget doesn't work (isn't accessible/enabled) in a test template that has been setup/saved, it does work in a new test though. Example attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 September 2019