April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2396) [DMN Designer] Cover dtable commands for non trivial index

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2396?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2396: -------------------------------- Description: Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*. h3. Acceptance criteria # AddInputClauseCommand (/) # AddOutputClauseCommand (/) # DeleteRuleCommand (/) # DeleteInputClauseCommand (?) # DeleteOutputClauseCommand (?) was: Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*. h3. Acceptance criteria # AddInputClauseCommand (/) # AddOutputClauseCommand (/) # DeleteRuleCommand (?) # DeleteInputClauseCommand (?) # DeleteOutputClauseCommand (?) > [DMN Designer] Cover dtable commands for non trivial index > ---------------------------------------------------------- > > Key: DROOLS-2396 > URL: https://issues.jboss.org/browse/DROOLS-2396 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > > Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*. > h3. Acceptance criteria > # AddInputClauseCommand (/) > # AddOutputClauseCommand (/) > # DeleteRuleCommand (/) > # DeleteInputClauseCommand (?) > # DeleteOutputClauseCommand (?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3730) Use of relative-to="jboss.domain.base.dir" prevents the host from starting up

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3730?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3730: ------------------------------------------ I've updated the title of this to better reflect the specific problem. It was problem with a particular path, not a general inability to use relative-to in domain mode. > Use of relative-to="jboss.domain.base.dir" prevents the host from starting up > ----------------------------------------------------------------------------- > > Key: WFCORE-3730 > URL: https://issues.jboss.org/browse/WFCORE-3730 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Teresa Miyar > Assignee: Brian Stansberry > Labels: downstream_dependency > > Server does not start on domain mode when setting relative-to in the path > {code:java} > <paths> > <path name="apps.log.dir" path="/apps/logs" relative-to="jboss.domain.base.dir"/> > </paths> > {code} > {code:java} > [Host Controller] 13:28:05,730 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/path=apps.log.dir' are not available: > [Host Controller] org.wildfly.management.path.jboss.domain.base.dir in context 'global'; Possible registration points for this capability: > [Host Controller] /host=master/path=* > [Host Controller] /host=master/server-config=*/path=* > [Host Controller] /path=* > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3730) Use of relative-to="jboss.domain.base.dir" prevents the host from starting up

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3730?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3730: ------------------------------------- Summary: Use of relative-to="jboss.domain.base.dir" prevents the host from starting up (was: Use of relative-to in path in domain mode prevents the server from starting up.) > Use of relative-to="jboss.domain.base.dir" prevents the host from starting up > ----------------------------------------------------------------------------- > > Key: WFCORE-3730 > URL: https://issues.jboss.org/browse/WFCORE-3730 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Teresa Miyar > Assignee: Brian Stansberry > Labels: downstream_dependency > > Server does not start on domain mode when setting relative-to in the path > {code:java} > <paths> > <path name="apps.log.dir" path="/apps/logs" relative-to="jboss.domain.base.dir"/> > </paths> > {code} > {code:java} > [Host Controller] 13:28:05,730 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/path=apps.log.dir' are not available: > [Host Controller] org.wildfly.management.path.jboss.domain.base.dir in context 'global'; Possible registration points for this capability: > [Host Controller] /host=master/path=* > [Host Controller] /host=master/server-config=*/path=* > [Host Controller] /path=* > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2396) [DMN Designer] Cover dtable commands for non trivial index

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2396?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2396: -------------------------------- Description: Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*. h3. Acceptance criteria # AddInputClauseCommand (/) # AddOutputClauseCommand (/) # DeleteRuleCommand (?) # DeleteInputClauseCommand (?) # DeleteOutputClauseCommand (?) was: Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*. h3. Acceptance criteria # AddInputClauseCommand (/) # AddOutputClauseCommand (?) # DeleteRuleCommand (?) # DeleteInputClauseCommand (?) # DeleteOutputClauseCommand (?) > [DMN Designer] Cover dtable commands for non trivial index > ---------------------------------------------------------- > > Key: DROOLS-2396 > URL: https://issues.jboss.org/browse/DROOLS-2396 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > > Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*. > h3. Acceptance criteria > # AddInputClauseCommand (/) > # AddOutputClauseCommand (/) > # DeleteRuleCommand (?) > # DeleteInputClauseCommand (?) > # DeleteOutputClauseCommand (?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10207) [Artemis 2.x upgrade] journal-jdbc-lock-acquisition-timeout attribute should be removed

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10207?page=com.atlassian.jira.plugin... ] Jeff Mesnil resolved WFLY-10207. -------------------------------- Resolution: Done fix in integration branch https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... > [Artemis 2.x upgrade] journal-jdbc-lock-acquisition-timeout attribute should be removed > --------------------------------------------------------------------------------------- > > Key: WFLY-10207 > URL: https://issues.jboss.org/browse/WFLY-10207 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Labels: feature-branch-blocker > > The new integration code which integrates Artemis 2.x contains new attribute {{journal-jdbc-lock-acquisition-timeout}}. However this attribute has been removed recently in Artemis \[1\] and its value has been hard-coded to -1. Messaging layer should drop this attribute either. > \[1\] https://github.com/apache/activemq-artemis/pull/1972 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2396) [DMN Designer] Cover dtable commands for non trivial index

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2396?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2396: -------------------------------- Description: Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*. h3. Acceptance criteria # AddInputClauseCommand (/) # AddOutputClauseCommand (?) # DeleteRuleCommand (?) # DeleteInputClauseCommand (?) # DeleteOutputClauseCommand (?) was: Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*. h3. Acceptance criteria # AddInputClauseCommand (?) # AddOutputClauseCommand (?) # DeleteRuleCommand (?) # DeleteInputClauseCommand (?) # DeleteOutputClauseCommand (?) > [DMN Designer] Cover dtable commands for non trivial index > ---------------------------------------------------------- > > Key: DROOLS-2396 > URL: https://issues.jboss.org/browse/DROOLS-2396 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > > Cover decision table commands for non trivial cases, it means when table had multiple rules / inputs / outputs. And then *rule / input / output* is *added / deleted*. > h3. Acceptance criteria > # AddInputClauseCommand (/) > # AddOutputClauseCommand (?) > # DeleteRuleCommand (?) > # DeleteInputClauseCommand (?) > # DeleteOutputClauseCommand (?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-111) Update from Openshift 3.7 to Openshift 3.9 on b12

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-111?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-111: ------------------------------------------ Summary: Update from Openshift 3.7 to Openshift 3.9 on b12 (was: Update from Openshift 3.7 to Openshift 3.9) > Update from Openshift 3.7 to Openshift 3.9 on b12 > ------------------------------------------------- > > Key: SWSQE-111 > URL: https://issues.jboss.org/browse/SWSQE-111 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-128) Reinstall Openshift on B11

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-128?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo closed SWSQE-128. ----------------------------------------- Resolution: Done > Reinstall Openshift on B11 > -------------------------- > > Key: SWSQE-128 > URL: https://issues.jboss.org/browse/SWSQE-128 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-111) Update from Openshift 3.7 to Openshift 3.9

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-111?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-111: ------------------------------------------ Priority: Critical (was: Major) > Update from Openshift 3.7 to Openshift 3.9 > ------------------------------------------ > > Key: SWSQE-111 > URL: https://issues.jboss.org/browse/SWSQE-111 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-128) Reinstall Openshift on B11

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-128?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-128: ----------------------------------------------- Hayk Hovsepyan I'm closing this in favor of SWSQE-111 As minor fixing: I extended the root partition from 50GB to 204 GB. With 50GB, it was used 15GB (~30% of the disk) Now it is been used 15GB of 204 GB (~7% of the disk) With 204 GB I think it will have some room for deploy pods on the openshift. I am waiting on Filip Brychta to document the steps that he took on b22, in order to replicate that on b11 (upgrading for openshift 3.9), but I think this card can wait until sprint 4 > Reinstall Openshift on B11 > -------------------------- > > Key: SWSQE-128 > URL: https://issues.jboss.org/browse/SWSQE-128 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 April 2018