October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-713) There is too many jenkins slaves

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-713?page=com.atlassian.jira.plugin.... ] Filip Brychta updated SWSQE-713: -------------------------------- Sprint: Kiali Sprint #23, Kiali Sprint #28 (was: Kiali Sprint #23) > There is too many jenkins slaves > -------------------------------- > > Key: SWSQE-713 > URL: https://issues.jboss.org/browse/SWSQE-713 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > There are multiple jenkins slaves started for one jenkins job. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3660) DMN Navigator panel: DRD tree actions

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3660?page=com.atlassian.jira.plugi... ] Elizabeth Clayton closed DROOLS-3660. ------------------------------------- Resolution: Duplicate Issue > DMN Navigator panel: DRD tree actions > ------------------------------------- > > Key: DROOLS-3660 > URL: https://issues.jboss.org/browse/DROOLS-3660 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UXTeam, drools-tools > Attachments: Screen Shot 2019-01-28 at 1.38.21 PM.png, Screen Shot 2019-01-28 at 2.35.00 PM.png, Screen Shot 2019-01-31 at 9.45.39 AM.png, Screen Shot 2019-02-01 at 10.52.51 AM.png > > > As a user I want to be able to be able to use the Navigator tree to create DRD's and assign canvas nodes, so that I can easily modify my graph views. > Notes: > - Drag nodes to DRDs. > - Contextual menu for tree objects? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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: -------------------------------------- Description: 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. * As a user I want to be able to be able to use the Navigator tree to create DRD's and assign canvas nodes, so that I can easily modify my graph views. Notes: Drag nodes to DRDs. Contextual menu for tree objects? was: 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. > 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. > * As a user I want to be able to be able to use the Navigator tree to create DRD's and assign canvas nodes, so that I can easily modify my graph views. > Notes: > Drag nodes to DRDs. > Contextual menu for tree objects? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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: 2019 Week 41-43 (from Okt 7) > 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.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-236) Galleon prosvisioning should ignore MAVEN_ARGS meant for S2I app build

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-236?page=com.atlassian.jira.plugin.... ] Jean Francois Denise resolved WFWIP-236. ---------------------------------------- Resolution: Done > Galleon prosvisioning should ignore MAVEN_ARGS meant for S2I app build > ---------------------------------------------------------------------- > > Key: WFWIP-236 > URL: https://issues.jboss.org/browse/WFWIP-236 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Critical > > Imagine running S2I build with MAVEN_ARGS="myplugin:mygoal" > It will fail the galleon provisioning because the mvn command is using MAVEN_ARGS meant for user app. Users can be very creative so we should be more robust and ideally ignore this input for galleon build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4704) WS integration with WildFly Elytron - AuthenticationClient for Authentication / SSL

by Diana Vilkolakova (Jira)

Diana Vilkolakova created WFCORE-4704: ----------------------------------------- Summary: WS integration with WildFly Elytron - AuthenticationClient for Authentication / SSL Key: WFCORE-4704 URL: https://issues.jboss.org/browse/WFCORE-4704 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Diana Vilkolakova Assignee: Diana Vilkolakova EAP7-1097 introduces new Elytron client configuration properties. This issue is to make it possible to configure these from the Elytron subsystem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12653) Session passivation event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12653?page=com.atlassian.jira.plugin... ] Paul Ferraro moved JBEAP-17759 to WFLY-12653: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12653 (was: JBEAP-17759) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: 18.0.0.Final (was: 7.3.0.CD17) (was: 7.2.4.GA) > Session passivation event can deadlock if it attempts write operations on a session > ----------------------------------------------------------------------------------- > > Key: WFLY-12653 > URL: https://issues.jboss.org/browse/WFLY-12653 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12653) Session passivation event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12653?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-12653: -------------------------------- > Session passivation event can deadlock if it attempts write operations on a session > ----------------------------------------------------------------------------------- > > Key: WFLY-12653 > URL: https://issues.jboss.org/browse/WFLY-12653 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration

by Michal Jurc (Jira)

[ https://issues.jboss.org/browse/WFWIP-229?page=com.atlassian.jira.plugin.... ] Michal Jurc commented on WFWIP-229: ----------------------------------- [~yersan] You're correct. If there's a way to configure non-deprecated encryption, this is not an issue. > Configuring JGroups encryption protocols produces deprecated configuration > -------------------------------------------------------------------------- > > Key: WFWIP-229 > URL: https://issues.jboss.org/browse/WFWIP-229 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Environment: The example has been produced with the following S2I environment variables: > {code} > OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service > JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT > JGROUPS_CLUSTER_PASSWORD=foobar123 > OPENSHIFT_DNS_PING_SERVICE_PORT=8888 > JGROUPS_PING_PROTOCOL=dns.DNS_PING > SCRIPT_DEBUG=true > {code} > Reporter: Michal Jurc > Assignee: Yeray Borges > Priority: Critical > > Any S2I configuration of ping protocols utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to. > {code:title=Example JGroups ASYM_ENCRYPT configuration} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description > { > "outcome" => "success", > "result" => { > "description" => "The configuration of a protocol within a protocol stac > k.", > "capabilities" => [{ > "name" => "org.wildfly.clustering.jgroups.protocol", > "dynamic" => true, > "dynamic-elements" => [ > "stack", > "protocol" > ] > }], > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead." > }, > "attributes" => { > "module" => { > "type" => STRING, > "description" => "The module with which to resolve the protocol > type.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => "org.jgroups", > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "properties" => { > "type" => OBJECT, > "description" => "The properties of this protocol.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "value-type" => STRING, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "socket-binding" => { > "type" => STRING, > "description" => "Defines the bind address/port used of the serv > er socket used to receive messages from other cluster members.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Supports EAP 7.0 slaves." > }, > "access-type" => "read-only", > "storage" => "configuration" > }, > "statistics-enabled" => { > "type" => BOOLEAN, > "description" => "Indicates whether or not this protocol will co > llect statistics overriding stack configuration.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > } > }, > "operations" => undefined, > "notifications" => undefined, > "children" => {"property" => { > "description" => "A JGroups protocol property.", > "model-description" => undefined > }} > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-229) Configuring JGroups encryption protocols produces deprecated configuration

by Michal Jurc (Jira)

[ https://issues.jboss.org/browse/WFWIP-229?page=com.atlassian.jira.plugin.... ] Michal Jurc closed WFWIP-229. ----------------------------- Resolution: Explained > Configuring JGroups encryption protocols produces deprecated configuration > -------------------------------------------------------------------------- > > Key: WFWIP-229 > URL: https://issues.jboss.org/browse/WFWIP-229 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Environment: The example has been produced with the following S2I environment variables: > {code} > OPENSHIFT_DNS_PING_SERVICE_NAME=ping-service > JGROUPS_ENCRYPT_PROTOCOL=ASYM_ENCRYPT > JGROUPS_CLUSTER_PASSWORD=foobar123 > OPENSHIFT_DNS_PING_SERVICE_PORT=8888 > JGROUPS_PING_PROTOCOL=dns.DNS_PING > SCRIPT_DEBUG=true > {code} > Reporter: Michal Jurc > Assignee: Yeray Borges > Priority: Critical > > Any S2I configuration of ping protocols utilising encryption for protocols will result in deprecated configuration. S2I should not configure runtime to deprecated configuration by default, unless the user chooses to. > {code:title=Example JGroups ASYM_ENCRYPT configuration} > [standalone@localhost:9990 /] /subsystem=jgroups/stack=tcp/protocol=org.jgroups.protocols.ASYM_ENCRYPT:read-resource-description > { > "outcome" => "success", > "result" => { > "description" => "The configuration of a protocol within a protocol stac > k.", > "capabilities" => [{ > "name" => "org.wildfly.clustering.jgroups.protocol", > "dynamic" => true, > "dynamic-elements" => [ > "stack", > "protocol" > ] > }], > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Use protocol=ASYM_ENCRYPT instead." > }, > "attributes" => { > "module" => { > "type" => STRING, > "description" => "The module with which to resolve the protocol > type.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "default" => "org.jgroups", > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "properties" => { > "type" => OBJECT, > "description" => "The properties of this protocol.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "value-type" => STRING, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "socket-binding" => { > "type" => STRING, > "description" => "Defines the bind address/port used of the serv > er socket used to receive messages from other cluster members.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "5.0.0", > "reason" => "Deprecated. Supports EAP 7.0 slaves." > }, > "access-type" => "read-only", > "storage" => "configuration" > }, > "statistics-enabled" => { > "type" => BOOLEAN, > "description" => "Indicates whether or not this protocol will co > llect statistics overriding stack configuration.", > "expressions-allowed" => true, > "required" => false, > "nillable" => true, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > } > }, > "operations" => undefined, > "notifications" => undefined, > "children" => {"property" => { > "description" => "A JGroups protocol property.", > "model-description" => undefined > }} > } > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

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