May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11610) Core JMS client leaks temporary destination names

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11610?page=com.atlassian.jira.plugin... ] James Perkins resolved WFLY-11610. ---------------------------------- Fix Version/s: 17.0.0.Beta1 Resolution: Done > Core JMS client leaks temporary destination names > ------------------------------------------------- > > Key: WFLY-11610 > URL: https://issues.jboss.org/browse/WFLY-11610 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 15.0.1.Final > Environment: Red Hat JBoss Enterprise Application Platform > 7.1.5/7.2.0.GA > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Critical > Fix For: 17.0.0.Beta1 > > > The core JMS client leaks the {{SimpleString}} identifiers for temporary destinations. When a temporary JMS destination is created it is added to two lists on {{ActiveMQConnection}}, but when it is deleted it is only removed from one list. > {code:java} > public void addTemporaryQueue(final SimpleString queueAddress) { > tempQueues.add(queueAddress); > knownDestinations.add(queueAddress); > } > public void removeTemporaryQueue(final SimpleString queueAddress) { > tempQueues.remove(queueAddress); > }{code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11026) Journal compacting doesn't work with JDK 11

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-11026?page=com.atlassian.jira.plugin... ] James Perkins resolved WFLY-11026. ---------------------------------- Fix Version/s: 17.0.0.Beta1 Resolution: Done > Journal compacting doesn't work with JDK 11 > ------------------------------------------- > > Key: WFLY-11026 > URL: https://issues.jboss.org/browse/WFLY-11026 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final, 16.0.0.Final > Environment: {noformat} > java 11-ea 2018-09-25 > Java(TM) SE Runtime Environment 18.9 (build 11-ea+21) > Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode) > {noformat} > Reporter: Martin Styk > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: Java11, jdk10, jdk11 > Fix For: 17.0.0.Beta1 > > > Journal compacting doesn't work with Artemis 1.5 and JDK 11 > It fails with following stack trace: > {noformat} > 12:34:58,017 ERROR [org.apache.activemq.artemis.journal] (Thread-2 (ActiveMQ-IO-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$4@5483fda8)) AMQ144003: Error compacting: java.lang.reflect.InvocationTargetException > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at io.netty@4.1.25.Final//io.netty.util.internal.CleanerJava9.freeDirectBuffer(CleanerJava9.java:77) > at io.netty@4.1.25.Final//io.netty.util.internal.PlatformDependent.freeDirectBuffer(PlatformDependent.java:388) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFileFactory.releaseBuffer(NIOSequentialFileFactory.java:175) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.doInternalWrite(NIOSequentialFile.java:312) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.internalWrite(NIOSequentialFile.java:282) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.io.nio.NIOSequentialFile.writeDirect(NIOSequentialFile.java:255) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.AbstractJournalUpdateTask.flush(AbstractJournalUpdateTask.java:217) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.compact(JournalImpl.java:1520) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl$14.run(JournalImpl.java:2060) > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: java.lang.IllegalArgumentException: duplicate or slice > at jdk.unsupported/sun.misc.Unsafe.invokeCleaner(Unsafe.java:1238) > {noformat} > This causes issues also in scenario with journal replication. > {noformat} > 13:09:32,133 WARN [org.apache.activemq.artemis.core.server] (Thread-173) AMQ222013: Error when trying to start replication: java.lang.RuntimeException: Error during compact, look at the logs > at org.apache.activemq.artemis.journal@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.journal.impl.JournalImpl.scheduleCompactAndBlock(JournalImpl.java:1428) > at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.startReplication(JournalStorageManager.java:540) > at org.apache.activemq.artemis@1.5.5.jbossorg-012//org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation$2.run(SharedNothingLiveActivation.java:166) > at java.base/java.lang.Thread.run(Thread.java:834) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-148) Artemis logging codes/IDs have changed for CORE protocol

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFWIP-148?page=com.atlassian.jira.plugin.... ] James Perkins resolved WFWIP-148. --------------------------------- Resolution: Done > Artemis logging codes/IDs have changed for CORE protocol > -------------------------------------------------------- > > Key: WFWIP-148 > URL: https://issues.jboss.org/browse/WFWIP-148 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Justin Bertram > Priority: Blocker > > Artemis logging codes for CORE protocol has changed in scope of jira: https://issues.apache.org/jira/browse/ARTEMIS-1018 > For example in WF14 if standalone JMS client failed to connect then it was logged with code AMQ119007: > {code} > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.] > {code} > but newly it would have code AMQ219007: > {code} > Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.] > {code} > This is problem for any user/customer who had monitoring based on those codes as this will require to change it. > The reason for change was because those codes were duplicated between AMQP and CORE protocol. As CORE protocol is default and AMQP is not supported for EAP ti would makes sense to change AMQP codes instead and keep codes for CORE protocol without any change. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12105) Upgrade Apache Artemis from 2.8.0.Final to 2.8.1.Final

by Carlo de Wolf (Jira)

[ https://issues.jboss.org/browse/WFLY-12105?page=com.atlassian.jira.plugin... ] Carlo de Wolf updated WFLY-12105: --------------------------------- Labels: downstream_dependency (was: ) > Upgrade Apache Artemis from 2.8.0.Final to 2.8.1.Final > ------------------------------------------------------ > > Key: WFLY-12105 > URL: https://issues.jboss.org/browse/WFLY-12105 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: James Perkins > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: downstream_dependency > Fix For: 17.0.0.Beta1 > > > Upgrade Apache Artemis from 2.8.0.Final to 2.8.1.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12105) Upgrade Apache Artemis from 2.8.0.Final to 2.8.1.Final

by James Perkins (Jira)

James Perkins created WFLY-12105: ------------------------------------ Summary: Upgrade Apache Artemis from 2.8.0.Final to 2.8.1.Final Key: WFLY-12105 URL: https://issues.jboss.org/browse/WFLY-12105 Project: WildFly Issue Type: Component Upgrade Components: JMS Reporter: James Perkins Assignee: Emmanuel Hugonnet Fix For: 17.0.0.Beta1 Upgrade Apache Artemis from 2.8.0.Final to 2.8.1.Final. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4049) PMML files are not listed in Library only in Project Explorer

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-4049?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-4049: --------------------------------------- I guess the definition is very loose, as at the same time that PMML models can define decisions (e.g. decision trees, or neural network classification), it also does things like regressions, that may or may not be seen as a decision. Anyway, since it is a loose definition, listing it under either Decision or Model is fine with me. > PMML files are not listed in Library only in Project Explorer > ------------------------------------------------------------- > > Key: DROOLS-4049 > URL: https://issues.jboss.org/browse/DROOLS-4049 > Project: Drools > Issue Type: Enhancement > Components: PMML > Affects Versions: 7.21.0.Final > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: image-2019-05-17-15-43-45-741.png, image-2019-05-17-15-44-06-544.png, image-2019-05-17-15-44-30-629.png, test_scorecard.pmml > > > As title I upload a .pmml file > !image-2019-05-17-15-43-45-741.png|thumbnail! > it does not appear in asset view despite refresh and multiple time waiting: > !image-2019-05-17-15-44-06-544.png|thumbnail! > the only way to check if the file is there is to open another editor at random and check in file explorer: > !image-2019-05-17-15-44-30-629.png|thumbnail! > h2. Acceptance test > - Import (/) > - Change and reopen (/) > - Download (/) > - Remove (/) > - Rename (/) > - Filter (/) > - View in Project view (/) > - View in repository view (/) > - Build project (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4049) PMML files are not listed in Library only in Project Explorer

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4049?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-4049: --------------------------------------- To be honest I consider {{PMML}} more like a {{Decision}} than a {{Model}}. It is the serialization of the model of a predictive decision like DMN is the serialization of the model of a rule decision. Btw fine for me whatever you choose :) > PMML files are not listed in Library only in Project Explorer > ------------------------------------------------------------- > > Key: DROOLS-4049 > URL: https://issues.jboss.org/browse/DROOLS-4049 > Project: Drools > Issue Type: Enhancement > Components: PMML > Affects Versions: 7.21.0.Final > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: image-2019-05-17-15-43-45-741.png, image-2019-05-17-15-44-06-544.png, image-2019-05-17-15-44-30-629.png, test_scorecard.pmml > > > As title I upload a .pmml file > !image-2019-05-17-15-43-45-741.png|thumbnail! > it does not appear in asset view despite refresh and multiple time waiting: > !image-2019-05-17-15-44-06-544.png|thumbnail! > the only way to check if the file is there is to open another editor at random and check in file explorer: > !image-2019-05-17-15-44-30-629.png|thumbnail! > h2. Acceptance test > - Import (/) > - Change and reopen (/) > - Download (/) > - Remove (/) > - Rename (/) > - Filter (/) > - View in Project view (/) > - View in repository view (/) > - Build project (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4049) PMML files are not listed in Library only in Project Explorer

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4049?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-4049: ---------------------------------------- [~tirelli] I've commented the PR (as [~danielezonca] has queried use of _model_)... "Model" is traditionally Java (although {{KieModule}} is also considered a _model_ as far as Business Central is concerned). "Others" is traditionally more _system_ centric things like "Dynamic Menu definition", "Perspective definition" etc (although {{pom.xml}} is considered _others_). > PMML files are not listed in Library only in Project Explorer > ------------------------------------------------------------- > > Key: DROOLS-4049 > URL: https://issues.jboss.org/browse/DROOLS-4049 > Project: Drools > Issue Type: Enhancement > Components: PMML > Affects Versions: 7.21.0.Final > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: image-2019-05-17-15-43-45-741.png, image-2019-05-17-15-44-06-544.png, image-2019-05-17-15-44-30-629.png, test_scorecard.pmml > > > As title I upload a .pmml file > !image-2019-05-17-15-43-45-741.png|thumbnail! > it does not appear in asset view despite refresh and multiple time waiting: > !image-2019-05-17-15-44-06-544.png|thumbnail! > the only way to check if the file is there is to open another editor at random and check in file explorer: > !image-2019-05-17-15-44-30-629.png|thumbnail! > h2. Acceptance test > - Import (/) > - Change and reopen (/) > - Download (/) > - Remove (/) > - Rename (/) > - Filter (/) > - View in Project view (/) > - View in repository view (/) > - Build project (/) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4047) Unable to use CSV in a ruleTemplate

by Tibor Zimanyi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4047?page=com.atlassian.jira.plugi... ] Tibor Zimanyi updated DROOLS-4047: ---------------------------------- Story Points: 1 > Unable to use CSV in a ruleTemplate > ----------------------------------- > > Key: DROOLS-4047 > URL: https://issues.jboss.org/browse/DROOLS-4047 > Project: Drools > Issue Type: Bug > Components: decision tables > Affects Versions: 6.5.0.Final, 7.21.0.Final > Environment: Any Java env > Reporter: Adam Baxter > Assignee: Tibor Zimanyi > Priority: Major > Attachments: csv_import_test.tar.gz > > > I believe there is a bug where you cannot use a CSV file to use as a decision table to drive a ruleTemplate. Our issue appears to be a duplicate of the one mentioned in this pull request -https://github.com/kiegroup/drools/pull/1920 > The drools version we're using is 6.50.FINAL, but the reproducer I've attached is for the latest released version. > We'd like to move away from binary files as they're opaque to most version control and it makes branching difficult. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4047) Unable to use CSV in a ruleTemplate

by Tibor Zimanyi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4047?page=com.atlassian.jira.plugi... ] Tibor Zimanyi reassigned DROOLS-4047: ------------------------------------- Assignee: Tibor Zimanyi (was: Mario Fusco) > Unable to use CSV in a ruleTemplate > ----------------------------------- > > Key: DROOLS-4047 > URL: https://issues.jboss.org/browse/DROOLS-4047 > Project: Drools > Issue Type: Bug > Components: decision tables > Affects Versions: 6.5.0.Final, 7.21.0.Final > Environment: Any Java env > Reporter: Adam Baxter > Assignee: Tibor Zimanyi > Priority: Major > Attachments: csv_import_test.tar.gz > > > I believe there is a bug where you cannot use a CSV file to use as a decision table to drive a ruleTemplate. Our issue appears to be a duplicate of the one mentioned in this pull request -https://github.com/kiegroup/drools/pull/1920 > The drools version we're using is 6.50.FINAL, but the reproducer I've attached is for the latest released version. > We'd like to move away from binary files as they're opaque to most version control and it makes branching difficult. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019