April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2467) Constructing a JChannel using the default Constructor fails while parsing version '${version}'

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2467?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2467. ---------------------------- Resolution: Duplicate Issue Created new issue JGRP-2468 > Constructing a JChannel using the default Constructor fails while parsing version '${version}' > ---------------------------------------------------------------------------------------------- > > Key: JGRP-2467 > URL: https://issues.redhat.com/browse/JGRP-2467 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.2 > Reporter: Patrick Reinhart > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.3 > > > Constructing a JChannel using the default Constructor fails with a {{java.lang.IllegalStateException}} > {code} > java.io.IOException: JGRP000004: Fehler beim Parsen von XML; das Dokument ist nicht korrekt: failed parsing version '${version}': java.lang.IllegalStateException: No match found > at org.jgroups.conf.XmlConfigurator.parse(XmlConfigurator.java:142) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:45) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:41) > at org.jgroups.conf.ConfiguratorFactory.getXmlConfigurator(ConfiguratorFactory.java:174) > at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:63) > at org.jgroups.JChannel.<init>(JChannel.java:107) > at org.jgroups.JChannel.<init>(JChannel.java:98) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2467) Constructing a JChannel using the default Constructor fails while parsing version '${version}'

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2467?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2467: --------------------------- Fix Version/s: 4.2.3 > Constructing a JChannel using the default Constructor fails while parsing version '${version}' > ---------------------------------------------------------------------------------------------- > > Key: JGRP-2467 > URL: https://issues.redhat.com/browse/JGRP-2467 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.2 > Reporter: Patrick Reinhart > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.3 > > > Constructing a JChannel using the default Constructor fails with a {{java.lang.IllegalStateException}} > {code} > java.io.IOException: JGRP000004: Fehler beim Parsen von XML; das Dokument ist nicht korrekt: failed parsing version '${version}': java.lang.IllegalStateException: No match found > at org.jgroups.conf.XmlConfigurator.parse(XmlConfigurator.java:142) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:45) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:41) > at org.jgroups.conf.ConfiguratorFactory.getXmlConfigurator(ConfiguratorFactory.java:174) > at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:63) > at org.jgroups.JChannel.<init>(JChannel.java:107) > at org.jgroups.JChannel.<init>(JChannel.java:98) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2468) Remove osgi and replace version in XML sample configs correctly

by Bela Ban (Jira)

Bela Ban created JGRP-2468: ------------------------------ Summary: Remove osgi and replace version in XML sample configs correctly Key: JGRP-2468 URL: https://issues.redhat.com/browse/JGRP-2468 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.2.3 The backport from master didn't build JAR files correctly, they still had {{version="$\{version\}"}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2468) Remove osgi and replace version in XML sample configs correctly

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2468?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2468: --------------------------- Description: The backport from master didn't build JAR files correctly, they still had {{version="$\{version\}"}}. See JGRP-2467 for details. (was: The backport from master didn't build JAR files correctly, they still had {{version="$\{version\}"}}.) > Remove osgi and replace version in XML sample configs correctly > --------------------------------------------------------------- > > Key: JGRP-2468 > URL: https://issues.redhat.com/browse/JGRP-2468 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.3 > > > The backport from master didn't build JAR files correctly, they still had {{version="$\{version\}"}}. See JGRP-2467 for details. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2467) Constructing a JChannel using the default Constructor fails while parsing version '${version}'

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2467?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2467: -------------------------------- Workaround: remove "version" from the XML. > Constructing a JChannel using the default Constructor fails while parsing version '${version}' > ---------------------------------------------------------------------------------------------- > > Key: JGRP-2467 > URL: https://issues.redhat.com/browse/JGRP-2467 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.2 > Reporter: Patrick Reinhart > Assignee: Bela Ban > Priority: Major > > Constructing a JChannel using the default Constructor fails with a {{java.lang.IllegalStateException}} > {code} > java.io.IOException: JGRP000004: Fehler beim Parsen von XML; das Dokument ist nicht korrekt: failed parsing version '${version}': java.lang.IllegalStateException: No match found > at org.jgroups.conf.XmlConfigurator.parse(XmlConfigurator.java:142) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:45) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:41) > at org.jgroups.conf.ConfiguratorFactory.getXmlConfigurator(ConfiguratorFactory.java:174) > at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:63) > at org.jgroups.JChannel.<init>(JChannel.java:107) > at org.jgroups.JChannel.<init>(JChannel.java:98) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2467) Constructing a JChannel using the default Constructor fails while parsing version '${version}'

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2467?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2467: -------------------------------- Oops, this is a bug in the backport from master! If you use {{ant jar}}, it'll work. I'm going to fix the POM now... > Constructing a JChannel using the default Constructor fails while parsing version '${version}' > ---------------------------------------------------------------------------------------------- > > Key: JGRP-2467 > URL: https://issues.redhat.com/browse/JGRP-2467 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.2 > Reporter: Patrick Reinhart > Assignee: Bela Ban > Priority: Major > > Constructing a JChannel using the default Constructor fails with a {{java.lang.IllegalStateException}} > {code} > java.io.IOException: JGRP000004: Fehler beim Parsen von XML; das Dokument ist nicht korrekt: failed parsing version '${version}': java.lang.IllegalStateException: No match found > at org.jgroups.conf.XmlConfigurator.parse(XmlConfigurator.java:142) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:45) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:41) > at org.jgroups.conf.ConfiguratorFactory.getXmlConfigurator(ConfiguratorFactory.java:174) > at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:63) > at org.jgroups.JChannel.<init>(JChannel.java:107) > at org.jgroups.JChannel.<init>(JChannel.java:98) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-301) SingleServerRuntimeTest intermittent failure in CodeReady Studio jobs

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/WFWIP-301?page=com.atlassian.jira.plugin... ] Josef Kopriva resolved WFWIP-301. --------------------------------- Resolution: Done > SingleServerRuntimeTest intermittent failure in CodeReady Studio jobs > --------------------------------------------------------------------- > > Key: WFWIP-301 > URL: https://issues.redhat.com/browse/WFWIP-301 > Project: WildFly WIP > Issue Type: Bug > Reporter: Marek Kopecky > Assignee: Josef Kopriva > Priority: Blocker > > [CodeReady Studio Jenkins jobs|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/vie...] is not stable. > I started this job a few times and it seems that there is intermittent failure of SingleServerRuntimeTest operate no-configuration test, see [this jenkins run|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view...] or [this run|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view...], both with EAP 7.3.0.GA.CR3. > EAP QE needs clear statement on behalf of JBDS QE Team whether "this test failure doesn't block EAP7-1128 RFE and can be ignored" or let me know when the job will be stable. Until that, I consider that the job is not ready and blocks EAP7-1128 RFE. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-301) SingleServerRuntimeTest intermittent failure in CodeReady Studio jobs

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/WFWIP-301?page=com.atlassian.jira.plugin... ] Josef Kopriva commented on WFWIP-301: ------------------------------------- Resolving this: I have had 6 builds without test failures with EAP 7.3 and CRS 12.15 nightly build. PR: in tests: https://github.com/jbosstools/jbosstools-server/pull/667 > SingleServerRuntimeTest intermittent failure in CodeReady Studio jobs > --------------------------------------------------------------------- > > Key: WFWIP-301 > URL: https://issues.redhat.com/browse/WFWIP-301 > Project: WildFly WIP > Issue Type: Bug > Reporter: Marek Kopecky > Assignee: Josef Kopriva > Priority: Blocker > > [CodeReady Studio Jenkins jobs|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/vie...] is not stable. > I started this job a few times and it seems that there is intermittent failure of SingleServerRuntimeTest operate no-configuration test, see [this jenkins run|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view...] or [this run|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view...], both with EAP 7.3.0.GA.CR3. > EAP QE needs clear statement on behalf of JBDS QE Team whether "this test failure doesn't block EAP7-1128 RFE and can be ignored" or let me know when the job will be stable. Until that, I consider that the job is not ready and blocks EAP7-1128 RFE. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2467) Constructing a JChannel using the default Constructor fails while parsing version '${version}'

by Patrick Reinhart (Jira)

[ https://issues.redhat.com/browse/JGRP-2467?page=com.atlassian.jira.plugin... ] Patrick Reinhart commented on JGRP-2467: ---------------------------------------- In this case the {{udp.xml}} contained within the JGoups distribution jar does seems to contain a non working default configuration: {code:xml}  <config xmlns="urn:org:jgroups" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd" version="${version}"> <UDP ... {code} > Constructing a JChannel using the default Constructor fails while parsing version '${version}' > ---------------------------------------------------------------------------------------------- > > Key: JGRP-2467 > URL: https://issues.redhat.com/browse/JGRP-2467 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.2 > Reporter: Patrick Reinhart > Assignee: Bela Ban > Priority: Major > > Constructing a JChannel using the default Constructor fails with a {{java.lang.IllegalStateException}} > {code} > java.io.IOException: JGRP000004: Fehler beim Parsen von XML; das Dokument ist nicht korrekt: failed parsing version '${version}': java.lang.IllegalStateException: No match found > at org.jgroups.conf.XmlConfigurator.parse(XmlConfigurator.java:142) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:45) > at org.jgroups.conf.XmlConfigurator.getInstance(XmlConfigurator.java:41) > at org.jgroups.conf.ConfiguratorFactory.getXmlConfigurator(ConfiguratorFactory.java:174) > at org.jgroups.conf.ConfiguratorFactory.getStackConfigurator(ConfiguratorFactory.java:63) > at org.jgroups.JChannel.<init>(JChannel.java:107) > at org.jgroups.JChannel.<init>(JChannel.java:98) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5235) An existing decision table already binding an object doesn't see when a field is added to that object

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5235?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-5235: ---------------------------------------- When you say "go back to the decision table" have you closed and re-opened the editor? It is a known limitation of Business Central that the (Reflection type) meta-data for editors is cached with the editor instance and changes to the underlying classes etc needs the editor to be closed and re-opened. > An existing decision table already binding an object doesn't see when a field is added to that object > ----------------------------------------------------------------------------------------------------- > > Key: DROOLS-5235 > URL: https://issues.redhat.com/browse/DROOLS-5235 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Mario Fusco > Assignee: Michael Anstis > Priority: Major > > Steps to reproduce: > 1. Create a data object with a few fields > 2. Create a Guided decision table with at least a condition column binding that object > 3. Go back to the object definition and add a new field and save > 4. Go back to the decision table and add a second column condition on the same object: the newly added field is not available among the other old fields in the drop down menu > Note that if you create a brand new table and try to add a condition on that object than also the new field is available. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 April 2020