September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12558) Intermittent failures in TCPSyslogAuditLogTestCase

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12558?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-12558: -------------------------------------- Ah you're correct. I forgot the initialization of the service, in Elytron itself IIRC, attempts to log a debug message. So a reconnect attempt may fix this. > Intermittent failures in TCPSyslogAuditLogTestCase > -------------------------------------------------- > > Key: WFLY-12558 > URL: https://issues.jboss.org/browse/WFLY-12558 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Major > > 5 tests in TCPSyslogAuditLogTestCase are frequently failing since late August: > https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... > Initial failure has this in the server log: > {code} > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("syslog-audit-log" => "TCPSyslogAuditLogTestCase") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.security-event-listener.TCPSyslogAuditLogTestCase" => "WFLYELY00004: Unable to start the service. > Caused by: java.io.IOException: ELY12001: The maximum reconnect attempts value of 0 was reached. The syslog endpoint will be shutdown."}} > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4666) Implement a non-user standalone.sh extension mechanism

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4666?page=com.atlassian.jira.plugi... ] James Perkins edited comment on WFCORE-4666 at 9/16/19 2:56 PM: ---------------------------------------------------------------- A bit off topic, but I'd still love to have some kind of other entry point where hooks like this would be easier to insert. I think I've been talking about that for a number of years now and I'm not sure if this is a good excuse to explore it more or not :) My assumption here is this is something that would be executed just before the {{java}} command not after it's been launched in the background correct? > Implement a non-user standalone.sh extension mechanism > ------------------------------------------------------ > > Key: WFCORE-4666 > URL: https://issues.jboss.org/browse/WFCORE-4666 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Reporter: Brian Stansberry > Priority: Major > > We have a reasonable architecture for how standalone.sh works: standalone.sh itself is not meant to be touched and has a lot of complex logic, and then standalone.conf is for users to manipulate as they wish to set up env vars. The standalone.conf is sourced early in the standalone.sh execution. > What's missing is a hook for non-user extensions to the standalone.conf concept. Primary use case being cloud containers where the container developers also don't want to maintain their own variant of standalone.sh but need to do env var manipulation before the main script logic runs. Right now images are handling this by shipping their own standalone.conf with a bunch of content appended, but that has the effect of making the file no longer a 'user' file. > A possible simple way to improve this is to have standalone.sh look for a 'standalone.conf.post' file and, if present, source it after standalone.conf. Perhaps a standalone.conf.pre as well. > (Tangent: I think our stock standalone.conf/bat etc should have a leading comment section explaining the "API" of standalone.sh, i.e. what are the env vars that standalone.sh will process that the user may wish to manipulate in standalone.sh. > [~luck3y] FYI and input. Whether this is a good idea in our images is a good thing to discuss; i.e. whether easing end-user manipulation is something desirable. The basic design is users should not do that, and instead they should use the various cloud-specific env vars processed by the image logic to manipulate the server launch. And I think that's fine/correct. I just don't like the way that image logic is implemented by having the image build append logic to standalone.conf. That's conceptually unclean. > [~jamezp] [~jmesnil] FYI. > This is not urgent; just something I was thinking about after helping with some user issues with our image launch. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4666) Implement a non-user standalone.sh extension mechanism

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4666?page=com.atlassian.jira.plugi... ] James Perkins edited comment on WFCORE-4666 at 9/16/19 2:56 PM: ---------------------------------------------------------------- [~jamezp] I was thinking directly after execution of standalone.conf, as the semantics of what's meant to be done in such a file are the same as those of standalone.conf, just 'after'. https://github.com/wildfly/wildfly-core/blob/master/core-feature-pack/src... I definitely was not thinking about something running after the JMV launch. If you look at the standalone.conf in one of the EAP images you can get a sense of the kinds of things that are being appended. Some of it's complex but IIRC in the end it comes down to changing the values of typical env vars, e.g. JAVA_OPTS. > Implement a non-user standalone.sh extension mechanism > ------------------------------------------------------ > > Key: WFCORE-4666 > URL: https://issues.jboss.org/browse/WFCORE-4666 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Reporter: Brian Stansberry > Priority: Major > > We have a reasonable architecture for how standalone.sh works: standalone.sh itself is not meant to be touched and has a lot of complex logic, and then standalone.conf is for users to manipulate as they wish to set up env vars. The standalone.conf is sourced early in the standalone.sh execution. > What's missing is a hook for non-user extensions to the standalone.conf concept. Primary use case being cloud containers where the container developers also don't want to maintain their own variant of standalone.sh but need to do env var manipulation before the main script logic runs. Right now images are handling this by shipping their own standalone.conf with a bunch of content appended, but that has the effect of making the file no longer a 'user' file. > A possible simple way to improve this is to have standalone.sh look for a 'standalone.conf.post' file and, if present, source it after standalone.conf. Perhaps a standalone.conf.pre as well. > (Tangent: I think our stock standalone.conf/bat etc should have a leading comment section explaining the "API" of standalone.sh, i.e. what are the env vars that standalone.sh will process that the user may wish to manipulate in standalone.sh. > [~luck3y] FYI and input. Whether this is a good idea in our images is a good thing to discuss; i.e. whether easing end-user manipulation is something desirable. The basic design is users should not do that, and instead they should use the various cloud-specific env vars processed by the image logic to manipulate the server launch. And I think that's fine/correct. I just don't like the way that image logic is implemented by having the image build append logic to standalone.conf. That's conceptually unclean. > [~jamezp] [~jmesnil] FYI. > This is not urgent; just something I was thinking about after helping with some user issues with our image launch. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4537) Update Keyboard Navigation Guidelines, with Decision Table information.

by Elizabeth Clayton (Jira)

Elizabeth Clayton created DROOLS-4537: ----------------------------------------- Summary: Update Keyboard Navigation Guidelines, with Decision Table information. Key: DROOLS-4537 URL: https://issues.jboss.org/browse/DROOLS-4537 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Elizabeth Clayton Update the Keyboard focus document for detailed keyboard recommendations for Decision Tables, currently it has Context Tables (which should be reviewed by SME, to make sure it follows the correct order.) detailed keyboard recommendations for Decision Table. https://docs.google.com/document/d/13XYx-IaVm_49J-j0MboPVsHWS8aTlG5ByeIfn... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12558) Intermittent failures in TCPSyslogAuditLogTestCase

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12558?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12558: ----------------------------------------- AIUI the test is failing because /subsystem=elytron/syslog-audit-log=TCPSyslogAuditLogTestCase:add fails during some setup task, and that op is when the connection must be established. IOW it's not because of timing related to actually sending a message. The reconnect workaround was an attempt to get that add op to not fail. > Intermittent failures in TCPSyslogAuditLogTestCase > -------------------------------------------------- > > Key: WFLY-12558 > URL: https://issues.jboss.org/browse/WFLY-12558 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Major > > 5 tests in TCPSyslogAuditLogTestCase are frequently failing since late August: > https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... > Initial failure has this in the server log: > {code} > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("syslog-audit-log" => "TCPSyslogAuditLogTestCase") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.security-event-listener.TCPSyslogAuditLogTestCase" => "WFLYELY00004: Unable to start the service. > Caused by: java.io.IOException: ELY12001: The maximum reconnect attempts value of 0 was reached. The syslog endpoint will be shutdown."}} > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8549) Create Externalizers, @Immutable and general session replication/failover quickstart

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-8549?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-8549: --------------------------------- Priority: Major (was: Critical) > Create Externalizers, @Immutable and general session replication/failover quickstart > ------------------------------------------------------------------------------------ > > Key: WFLY-8549 > URL: https://issues.jboss.org/browse/WFLY-8549 > Project: WildFly > Issue Type: Enhancement > Components: Clustering, Quickstarts > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: Awaiting Volunteers > > > Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication. > To demonstrate externalizers, we can demonstrate with non-serializable objects > For @ Immutable we can take 2 classes, one is immutable, one not, we can demonstrate getting attribute and mutating object vs get attribute, mutate, subsequent requests won't see mutation on failover – set attribute must be used. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8549) Create Externalizers, @Immutable and general session replication/failover quickstart

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-8549?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-8549: -------------------------------------- Let me just make this major then. > Create Externalizers, @Immutable and general session replication/failover quickstart > ------------------------------------------------------------------------------------ > > Key: WFLY-8549 > URL: https://issues.jboss.org/browse/WFLY-8549 > Project: WildFly > Issue Type: Enhancement > Components: Clustering, Quickstarts > Affects Versions: 11.0.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: Awaiting Volunteers > > > Demonstrate the marshalling mechanism via implementations of {{org.wildfly.clustering.marshalling.Externalizer}} in conjunction with general session replication. > To demonstrate externalizers, we can demonstrate with non-serializable objects > For @ Immutable we can take 2 classes, one is immutable, one not, we can demonstrate getting attribute and mutating object vs get attribute, mutate, subsequent requests won't see mutation on failover – set attribute must be used. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3957) Make verifier panel use docks

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3957?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-3957: -------------------------------------- [~jomarko] at the moment on hold. I'll try to get this forward so it does not get stale again. This is a part of the V&V effort. > Make verifier panel use docks > ----------------------------- > > Key: DROOLS-3957 > URL: https://issues.jboss.org/browse/DROOLS-3957 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Attachments: v&v.webm > > > Pretty sure we had a ticket for this, but could not find it. Here it is. > h3. Acceptance test > On both Firefox and Chrome (x) > - Opening multiple decision tables, switching between them > - Repeated reopening of guided decision table > - Opening other asset that uses docks - scenario, data object -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3566) DMN:Detailed interactions for creating and managing DRDs

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3566?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3566: -------------------------------------- Sprint: (was: 2019 Week 38-40) > DMN:Detailed interactions for creating and managing DRDs > -------------------------------------------------------- > > Key: DROOLS-3566 > URL: https://issues.jboss.org/browse/DROOLS-3566 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: contextual-menu.png > > > Canvas node actions related to grouping and assigning to DRDs. > As a user I want to easily select and group nodes on the canvas so that I can add them to a DRD or to create a new DRD. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4373) Review current implementation of Data Types section.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4373?page=com.atlassian.jira.plugi... ] Elizabeth Clayton closed DROOLS-4373. ------------------------------------- Resolution: Done out of date > Review current implementation of Data Types section. > ----------------------------------------------------- > > Key: DROOLS-4373 > URL: https://issues.jboss.org/browse/DROOLS-4373 > Project: Drools > Issue Type: Task > Reporter: Elizabeth Clayton > Assignee: Sarahjane Clark > Priority: Major > Labels: UX, UXTeam > > Preparatory work for a usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types. > * Review the current CICD implementation of the 7.x DMN editor, data types section. > * Review documented usability concerns. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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