July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ] Tom Jenkinson reassigned WFLY-10541: ------------------------------------ Assignee: Tom Jenkinson (was: Jason Greene) > allow user to easily override the transaction node identifier > ------------------------------------------------------------- > > Key: WFLY-10541 > URL: https://issues.jboss.org/browse/WFLY-10541 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Tom Jenkinson > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10541) allow user to easily override the transaction node identifier

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-10541?page=com.atlassian.jira.plugin... ] Tom Jenkinson updated WFLY-10541: --------------------------------- Forum Reference: https://lists.jboss.org/pipermail/keycloak-dev/2018-July/010985.html > allow user to easily override the transaction node identifier > ------------------------------------------------------------- > > Key: WFLY-10541 > URL: https://issues.jboss.org/browse/WFLY-10541 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Assignee: Tom Jenkinson > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-490) Upgrade EMF to 2.8.0 or higher

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-490?page=com.atlassian.jira.plugin... ] Tibor Zimányi commented on DROOLS-490: -------------------------------------- I see we still use these versions: <version.org.eclipse.emf>2.6.0.v20100614-1136</version.org.eclipse.emf> <version.org.eclipse.emf.ecore.xmi>2.5.0.v20100521-1846</version.org.eclipse.emf.ecore.xmi> however is this version upgrade still relevant? Could you please check [~ge0ffrey]? > Upgrade EMF to 2.8.0 or higher > ------------------------------ > > Key: DROOLS-490 > URL: https://issues.jboss.org/browse/DROOLS-490 > Project: Drools > Issue Type: Enhancement > Affects Versions: 6.1.0.Beta3 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > > Currently we use emf 2.6 with emf xmi 2.5. That's risky. > For more info, see https://github.com/jboss-integration/jboss-integration-platform-bom/pull/... > 1) Upgrade us to at least 2.7.0.v20120123-0926, but preferably 2.8, 2.9 or higher > 2) Send a PR to the ip-bom to change the emf version. > Undo the extra emf xmi version introduced in this pull request: > https://github.com/jboss-integration/jboss-integration-platform-bom/pull/... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-262) Bookinfo installation is failing when istio_auth is enabled

by Prachi Yadav (JIRA)

[ https://issues.jboss.org/browse/SWSQE-262?page=com.atlassian.jira.plugin.... ] Prachi Yadav reassigned SWSQE-262: ---------------------------------- Assignee: Prachi Yadav (was: Michael Foley) > Bookinfo installation is failing when istio_auth is enabled > ----------------------------------------------------------- > > Key: SWSQE-262 > URL: https://issues.jboss.org/browse/SWSQE-262 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Prachi Yadav > > This job http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo/ is failing on b15 when istio_auth is enabled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-328) Fix automations after KIALI-810

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-328?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-328. ---------------------------------- Resolution: Done PR merged https://github.com/Kiali-QE/kiali-qe-python/pull/59 > Fix automations after KIALI-810 > ------------------------------- > > Key: SWSQE-328 > URL: https://issues.jboss.org/browse/SWSQE-328 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-328) Fix automations after KIALI-810

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-328?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-328: --------------------------------- Sprint: Kiali QE Sprint 7, Kiali QE Sprint 8 (was: Kiali QE Sprint 7) > Fix automations after KIALI-810 > ------------------------------- > > Key: SWSQE-328 > URL: https://issues.jboss.org/browse/SWSQE-328 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2342) Update Kie Navigator to the new git/rest structure

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2342?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on DROOLS-2342: ------------------------------------------- Hi [~tomasdavidorg], could you check this issue, please? > Update Kie Navigator to the new git/rest structure > -------------------------------------------------- > > Key: DROOLS-2342 > URL: https://issues.jboss.org/browse/DROOLS-2342 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.5.0.Final > Environment: 7.7.0-SNAPSHOT > Reporter: Tomas David > Assignee: Tiago Bento > Labels: AppFormer, AppFormer-Prioritized > Fix For: 7.8.0.Final > > > Drools eclipse plugin contains Kie Navigator tool which uses git structure and rest calls to connect to kie-wb. According to changes made in kie-wb 7.7.0 the tooling should be updated. > The rest api and the git structure changed. and the kie navigator doesn't work. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10688) Bad unit conversion of jdbc-network-timeout attribute

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10688?page=com.atlassian.jira.plugin... ] Erich Duda updated WFLY-10688: ------------------------------ Description: In the messaging subsystem there is an attribute {{jdbc-network-timeout}} with default value 20 seconds. However this parameter is passed to ActiveMQ Artemis as 20 000 000 milliseconds (20 000 seconds). For reproducing the issue just configure JDBC persistence store and attach debugger with breakpoint on {{AbstractJDBCDriver::connect}}. *Blocker* priority was set because it is regression against Wildfly 12. was: In the messaging subsystem there is an attribute {{jdbc-network-timeout}} with default value 20 seconds. However this parameter is passed to ActiveMQ Artemis as 20 000 000 milliseconds (20 000 seconds). For reproducing the issue just configure JDBC persistence store and attach debugger with breakpoint on {{AbstractJDBCDriver::connect}}. *Blocker* priority was set because it is regression against Wildfly 12. The issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d) > Bad unit conversion of jdbc-network-timeout attribute > ----------------------------------------------------- > > Key: WFLY-10688 > URL: https://issues.jboss.org/browse/WFLY-10688 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Labels: feature-branch-blocker > > In the messaging subsystem there is an attribute {{jdbc-network-timeout}} with default value 20 seconds. However this parameter is passed to ActiveMQ Artemis as 20 000 000 milliseconds (20 000 seconds). > For reproducing the issue just configure JDBC persistence store and attach debugger with breakpoint on {{AbstractJDBCDriver::connect}}. > *Blocker* priority was set because it is regression against Wildfly 12. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2662) Guided Rule Editor does not open popup when binding a variable of type java.time.LocalDate in another constraint

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2662?page=com.atlassian.jira.plugi... ] Jozef Marko edited comment on DROOLS-2662 at 7/10/18 9:47 AM: -------------------------------------------------------------- Just for record, the reason why issue occurs just for {{java.time.LocalDate}} field is that {{AsyncPackageDataModelOracleImpl}} assumes {{java.time.LocalDate}} fields have type {{Comparable}} while {{java.util.Date}} fields have type {{Date}}. This difference caused that different branches of code were executed for different field types and we didn't spot the issue sooner. If we decide to support {{java.time.LocalDate}} we will have to update [converter|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-co...] was (Author: jomarko): Just for record, the reason why issue occurs just for {java.time.LocalDate} field is that {AsyncPackageDataModelOracleImpl} assumes {java.time.LocalDate} fields have type {Comparable} while {java.util.Date} fields have type {Date}. This difference caused that different branches of code were executed for different field types and we didn't spot the issue sooner. If we decide to support {java.time.LocalDate} we will have to update [converter|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-co...] > Guided Rule Editor does not open popup when binding a variable of type java.time.LocalDate in another constraint > ---------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2662 > URL: https://issues.jboss.org/browse/DROOLS-2662 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Jozef Marko > Assignee: Jozef Marko > Attachments: out-15.ogv > > > Consider a Data Object Test with a single field date of type java.time.LocalDate. When using Guided Rule Editor with two different conditions on Test object, with two Test object (the condition are in two separated objects), when we bind the date to a variable the constraint pop up won't open for the other condition, showing an error in console. > The attached video will clarify the issue. > That does not seem to happen with built in types and not even with java.util.Date type. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2662) Guided Rule Editor does not open popup when binding a variable of type java.time.LocalDate in another constraint

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2662?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2662: ------------------------------------- Just for record, the reason why issue occurs just for {java.time.LocalDate} field is that {AsyncPackageDataModelOracleImpl} assumes {java.time.LocalDate} fields have type {Comparable} while {java.util.Date} fields have type {Date}. This difference caused that different branches of code were executed for different field types and we didn't spot the issue sooner. If we decide to support {java.time.LocalDate} we will have to update [converter|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-co...] > Guided Rule Editor does not open popup when binding a variable of type java.time.LocalDate in another constraint > ---------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2662 > URL: https://issues.jboss.org/browse/DROOLS-2662 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Jozef Marko > Assignee: Jozef Marko > Attachments: out-15.ogv > > > Consider a Data Object Test with a single field date of type java.time.LocalDate. When using Guided Rule Editor with two different conditions on Test object, with two Test object (the condition are in two separated objects), when we bind the date to a variable the constraint pop up won't open for the other condition, showing an error in console. > The attached video will clarify the issue. > That does not seem to happen with built in types and not even with java.util.Date type. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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