June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-20) [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored

by Justin Bertram (JIRA)

[ https://issues.jboss.org/browse/WFWIP-20?page=com.atlassian.jira.plugin.s... ] Justin Bertram commented on WFWIP-20: ------------------------------------- I was able to reproduce the failure using the steps provided. However, I wanted to focus on the system property test so I ran that one by itself: {noformat} mvn clean test -Dtest=ClientThreadPoolTestCase#testGlobalPoolsConfiguredBySystemProperty -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1520950239-SNAPSHOT -DfailIfNoTests=true | tee log {noformat} As Jeff noted, the test runs, but it doesn't fail. I ran it several times and it always passed. I suspect there may be an issue with the test itself. [~jmesnil], I also looked into {{org.apache.activemq.artemis.ClientThreadPoolsTest#testSystemPropertyThreadPoolSettings}} in the Artemis code-base and it passes as expected. > [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored > ------------------------------------------------------------------------------------------------ > > Key: WFWIP-20 > URL: https://issues.jboss.org/browse/WFWIP-20 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq, feature-branch-blocker > > Setting client globalThreadPoolSize for configuring max number of ActiveMQ-client-global-threads using system property or in connection factory which is looked up by standalone JMS client is ignored. There is alway 8 * number CPU cores. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-291) Traffic Generator - Produce Traffice Through Route

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-291: ---------------------------------- Summary: Traffic Generator - Produce Traffice Through Route Key: SWSQE-291 URL: https://issues.jboss.org/browse/SWSQE-291 Project: Kiali QE Issue Type: QE Task Reporter: Matt Mahoney Assignee: Michael Foley A discussion with @jshaughn resulted in the need to re-evaluate whether the Traffic Generator should be directing traffic to the service route. This is because the Service Graph generation expectants the traffic to be coming from external to the pod, which is currently not the case. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-290) Roll Pipline Back To Deploying Istio 0.7.1

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-290?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-290: ------------------------------- Description: @jshaughn requested that QE not yet move to Istio 0.8 because of known Kiali issues that development continues to resolve. We are currently blocked from testing further Sprint-6 Jiras, and thus should roll back to using Istio 0.7.1 was: @jshaughn requested that we QE not yet move to Istio 0.8 because of known Kiali issues that development continues to resolve. We are currently blocked from testing further Sprint-6 Jiras, and thus should roll back to using Istio 0.7.1 > Roll Pipline Back To Deploying Istio 0.7.1 > ------------------------------------------ > > Key: SWSQE-290 > URL: https://issues.jboss.org/browse/SWSQE-290 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > > @jshaughn requested that QE not yet move to Istio 0.8 because of known Kiali issues that development continues to resolve. > We are currently blocked from testing further Sprint-6 Jiras, and thus should roll back to using Istio 0.7.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-290) Roll Pipline Back To Deploying Istio 0.7.1

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-290?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-290: ------------------------------- Description: @jshaughn requested that we QE not yet move to Istio 0.8 because of known Kiali issues that development continues to resolve. We are currently blocked from testing further Sprint-6 Jiras, and thus should roll back to using Istio 0.7.1 was: @jshaughn requested that we QE not yet move to Istio 0.8 because if known Kiali issues. We are currently blocked from testing further Sprint-6 Jiras, and thus should roll back to using Istio 0.7.1 > Roll Pipline Back To Deploying Istio 0.7.1 > ------------------------------------------ > > Key: SWSQE-290 > URL: https://issues.jboss.org/browse/SWSQE-290 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > > @jshaughn requested that we QE not yet move to Istio 0.8 because of known Kiali issues that development continues to resolve. > We are currently blocked from testing further Sprint-6 Jiras, and thus should roll back to using Istio 0.7.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-290) Roll Pipline Back To Deploying Istio 0.7.1

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-290?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-290: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Roll Pipline Back To Deploying Istio 0.7.1 > ------------------------------------------ > > Key: SWSQE-290 > URL: https://issues.jboss.org/browse/SWSQE-290 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > > @jshaughn requested that we QE not yet move to Istio 0.8 because if known Kiali issues. > We are currently blocked from testing further Sprint-6 Jiras, and thus should roll back to using Istio 0.7.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-290) Roll Pipline Back To Deploying Istio 0.7.1

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-290?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo commented on SWSQE-290: ----------------------------------------------- I have the commit which reverts 705d5c5ec7b3e5cc9fb4bc1e9fc80729dc906f39 locally [~hhovsepy] Do you think there any other changes to be reverted? > Roll Pipline Back To Deploying Istio 0.7.1 > ------------------------------------------ > > Key: SWSQE-290 > URL: https://issues.jboss.org/browse/SWSQE-290 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > > @jshaughn requested that we QE not yet move to Istio 0.8 because if known Kiali issues. > We are currently blocked from testing further Sprint-6 Jiras, and thus should roll back to using Istio 0.7.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-290) Roll Pipline Back To Deploying Istio 0.7.1

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-290: ---------------------------------- Summary: Roll Pipline Back To Deploying Istio 0.7.1 Key: SWSQE-290 URL: https://issues.jboss.org/browse/SWSQE-290 Project: Kiali QE Issue Type: QE Task Reporter: Matt Mahoney Assignee: Michael Foley Priority: Blocker @jshaughn requested that we QE not yet move to Istio 0.8 because if known Kiali issues. We are currently blocked from testing further Sprint-6 Jiras, and thus should roll back to using Istio 0.7.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2626) Support for Portable Format for Analytics (PFA)

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2626?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2626: --------------------------------------- Thank you for the link. We will look into it. [~mark.proctor] , FYI. > Support for Portable Format for Analytics (PFA) > ----------------------------------------------- > > Key: DROOLS-2626 > URL: https://issues.jboss.org/browse/DROOLS-2626 > Project: Drools > Issue Type: Feature Request > Components: core engine > Reporter: D Shah > Assignee: Edson Tirelli > > I was wondering if [Portable Format for Analytics (PFA)|http://dmg.org/pfa/index.html] would be a standard you'd be interested in supporting in Drools. It is developed by the same [Data Mining Group|http://dmg.org] who developed [PMML|http://dmg.org/pmml/v4-3/GeneralStructure.html]. Here's [the motivation behind them developing PFA|http://dmg.org/pfa/docs/motivation/] - > bq. "PFA is more flexible than PMML, but safer than custom code. In the language of optimizations, it is the most flexible way to describe a scoring engine subject to the constraint that it won’t break the data pipeline." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2626) Support for Portable Format for Analytics (PFA)

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2626?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-2626: ---------------------------------- Component/s: core engine > Support for Portable Format for Analytics (PFA) > ----------------------------------------------- > > Key: DROOLS-2626 > URL: https://issues.jboss.org/browse/DROOLS-2626 > Project: Drools > Issue Type: Feature Request > Components: core engine > Reporter: D Shah > Assignee: Edson Tirelli > > I was wondering if [Portable Format for Analytics (PFA)|http://dmg.org/pfa/index.html] would be a standard you'd be interested in supporting in Drools. It is developed by the same [Data Mining Group|http://dmg.org] who developed [PMML|http://dmg.org/pmml/v4-3/GeneralStructure.html]. Here's [the motivation behind them developing PFA|http://dmg.org/pfa/docs/motivation/] - > bq. "PFA is more flexible than PMML, but safer than custom code. In the language of optimizations, it is the most flexible way to describe a scoring engine subject to the constraint that it won’t break the data pipeline." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-10520: ------------------------------------- Good point, don't want to break code written against 5.3.x :) > Add Hibernate ORM 5.3 compatibility transformer > ----------------------------------------------- > > Key: WFLY-10520 > URL: https://issues.jboss.org/browse/WFLY-10520 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Scott Marlow > Fix For: 14.0.0.CR1 > > > A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 June 2018