April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-190) Add a filter to remove some jobs

by Jeeva Kandasamy (JIRA)

Jeeva Kandasamy created SWSQE-190: ------------------------------------- Summary: Add a filter to remove some jobs Key: SWSQE-190 URL: https://issues.jboss.org/browse/SWSQE-190 Project: Kiali QE Issue Type: Sub-task Reporter: Jeeva Kandasamy Assignee: Jeeva Kandasamy For now, there is no filter to skip posting some of the jobs. We need to add some of type filter to skip posting some jobs status on PR comment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10094) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10094?page=com.atlassian.jira.plugin... ] Miroslav Novak edited comment on WFLY-10094 at 4/26/18 8:51 AM: ---------------------------------------------------------------- The cause is that GLIBC_2.14 is missing: {code}java.lang.UnsatisfiedLinkError: /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so){code} However GLIBC is present on RHEL 6 but in older version 2.12. I've read something around this and problem is that libartemis-native-64.so was compiled on RHEL 7 where is newer GLIBC_2.14 version. So libartemis-native-64.so should be compiled on RHEL6 to fix this. Just from curiosity when I tried to compile glibc-2.14 and added it to LD_LIBRARY_PATH AIO got loaded on RHEL 6. was (Author: mnovak): The cause is that GLIBC_2.14 is missing: {code}java.lang.UnsatisfiedLinkError: /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so){code} However GLIBC is present on RHEL 6 but in older version 2.12. I've read something around this and problem is that libartemis-native-64.so was compiled on RHEL 7 where is newer GLIBC_2.14 version. So libartemis-native-64.so should be compiled on RHEL6 to fix this. Just from curiosity when I tried to compile glibc-2.14 and added it to LD_LIBRARY_PATH and AIO got loaded on RHEL 6. > [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64 > ----------------------------------------------------------------- > > Key: WFLY-10094 > URL: https://issues.jboss.org/browse/WFLY-10094 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq, feature-branch-blocker > > LibAIO does not get loaded on RHEL 6 x86_64: > {code} > [hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000 > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /tmp/jboss-eap > JAVA: java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > ... > 10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging) > 10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal > ... > {code} > libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag. > Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10094) [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10094?page=com.atlassian.jira.plugin... ] Miroslav Novak commented on WFLY-10094: --------------------------------------- The cause is that GLIBC_2.14 is missing: {code}java.lang.UnsatisfiedLinkError: /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /tmp/jboss-eap/modules/system/layers/base/org/apache/activemq/artemis/journal/main/lib/linux-x86_64/libartemis-native-64.so){code} However GLIBC is present on RHEL 6 but in older version 2.12. I've read something around this and problem is that libartemis-native-64.so was compiled on RHEL 7 where is newer GLIBC_2.14 version. So libartemis-native-64.so should be compiled on RHEL6 to fix this. Just from curiosity when I tried to compile glibc-2.14 and added it to LD_LIBRARY_PATH and AIO got loaded on RHEL 6. > [Artemis 2.x upgrade] libAIO does not get loaded on RHEL 6 x86_64 > ----------------------------------------------------------------- > > Key: WFLY-10094 > URL: https://issues.jboss.org/browse/WFLY-10094 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq, feature-branch-blocker > > LibAIO does not get loaded on RHEL 6 x86_64: > {code} > [hudson@rhel6-large-2723 bin]$ sh standalone.sh -c standalone-full-ha.xml -Djboss.socket.binding.port-offset=1000 > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /tmp/jboss-eap > JAVA: java > JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > ... > 10:14:31,918 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance. > 10:14:32,017 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=/tmp/jboss-eap/standalone/data/activemq/journal,bindingsDirectory=/tmp/jboss-eap/standalone/data/activemq/bindings,largeMessagesDirectory=/tmp/jboss-eap/standalone/data/activemq/largemessages,pagingDirectory=/tmp/jboss-eap/standalone/data/activemq/paging) > 10:14:32,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal > ... > {code} > libAIO in artemis journal module from WF branch. Not from Artemis 2.5.0.Final tag. > Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis: upstreadm master (577b62d5210cdcc0f86ab9bb1b24e944c877dfe7) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-182) Validate that Istio was succesfully deployed

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/SWSQE-182?page=com.atlassian.jira.plugin.... ] Sunil kondkar reassigned SWSQE-182: ----------------------------------- Assignee: Sunil kondkar (was: Michael Foley) > Validate that Istio was succesfully deployed > -------------------------------------------- > > Key: SWSQE-182 > URL: https://issues.jboss.org/browse/SWSQE-182 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Sunil kondkar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2482) Kjars aren't recognized as projects using the executable model when installed directly into the KieRepository

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2482?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2482: ----------------------------------- Sprint: 2018 Week 17-18 (was: RHPAM7-Iteration12) > Kjars aren't recognized as projects using the executable model when installed directly into the KieRepository > ------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2482 > URL: https://issues.jboss.org/browse/DROOLS-2482 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2479) Property reactivity mask is mistakenly set as empty by executable model when it is not possible to infer the modifed properties

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2479?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2479: ----------------------------------- Sprint: 2018 Week 17-18 (was: RHPAM7-Iteration12) > Property reactivity mask is mistakenly set as empty by executable model when it is not possible to infer the modifed properties > ------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2479 > URL: https://issues.jboss.org/browse/DROOLS-2479 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2468) Stateless sessions aren't under control of KieBase coordination during an incremental update

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2468?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2468: ----------------------------------- Sprint: 2018 Week 17-18 (was: RHPAM7-Iteration12) > Stateless sessions aren't under control of KieBase coordination during an incremental update > -------------------------------------------------------------------------------------------- > > Key: DROOLS-2468 > URL: https://issues.jboss.org/browse/DROOLS-2468 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2476) Promote Profile in public kie dmn API

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2476?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2476: ----------------------------------- Sprint: 2018 Week 15-16, 2018 Week 17-18 (was: 2018 Week 15-16) > Promote Profile in public kie dmn API > ------------------------------------- > > Key: DROOLS-2476 > URL: https://issues.jboss.org/browse/DROOLS-2476 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > # Promote DMNProfile and FEELProfile in public kie dmn api > # Have DMNRuntime to expose getProfiles (read-only method) > # Change jBPM as from: https://github.com/mswiderski/jbpm/blob/ff5dd337e5d57c49eb15277a05c3563c1... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2393) [DMN Designer] Not expected results of commands when multiple cells selected

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2393?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2393: ----------------------------------- Sprint: 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18 (was: 2018 Week 11-12, 2018 Week 13-14, 2018 Week 15-16) > [DMN Designer] Not expected results of commands when multiple cells selected > ---------------------------------------------------------------------------- > > Key: DROOLS-2393 > URL: https://issues.jboss.org/browse/DROOLS-2393 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > > When multiple cells of the decision table are selected, then the behavior of inline context menu can be confusing for the user. > Few scenarios: > # Select multiple cells, invoke context menu, select delete rule -> just one deleted > # Select multiple cells from different columns, invoke context menu, select delete -> just one column deleted > # Select both input and output cells, context menu entries are established according to the last click > # Select continuous block of cells, invoke context menu, selec insert rule below -> rule is not inserted below the most bottom cell of the block > # ... > Due to this, we should disable the context menu entries which could bring confusion for cases when multiple cells are selected -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2402) [DMN Designer] Support table header cell selection

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2402?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2402: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18 (was: 2018 Week 13-14, 2018 Week 15-16) > [DMN Designer] Support table header cell selection > -------------------------------------------------- > > Key: DROOLS-2402 > URL: https://issues.jboss.org/browse/DROOLS-2402 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Attachments: Screenshot from 2018-03-20 08-59-39.png, Screenshot from 2018-03-20 09-20-04.png > > > The decision table header cell does not support highlight / selection feature, see: > !Screenshot from 2018-03-20 08-59-39.png|thumbnail! > In contrast context entry name cell support this: > !Screenshot from 2018-03-20 09-20-04.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2018