August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2831) Memory leak when a mvel operator creates an EvaluatorWrapper

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2831?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2831: ---------------------------------- Story Points: 1 > Memory leak when a mvel operator creates an EvaluatorWrapper > ------------------------------------------------------------ > > Key: DROOLS-2831 > URL: https://issues.jboss.org/browse/DROOLS-2831 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Attachments: HxT83G5.png > > > The EvaluatorWrapper (which is created in some cases when a constraint uses an mvel operator) holds a reference to one or two FactHandles. Those reference are retained even after the KieSession has been disposed, thus causing a memory leak. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2831) Memory leak when a mvel operator creates an EvaluatorWrapper

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2831?page=com.atlassian.jira.plugi... ] Tibor Zimányi updated DROOLS-2831: ---------------------------------- Story Points: 2 (was: 1) > Memory leak when a mvel operator creates an EvaluatorWrapper > ------------------------------------------------------------ > > Key: DROOLS-2831 > URL: https://issues.jboss.org/browse/DROOLS-2831 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Attachments: HxT83G5.png > > > The EvaluatorWrapper (which is created in some cases when a constraint uses an mvel operator) holds a reference to one or two FactHandles. Those reference are retained even after the KieSession has been disposed, thus causing a memory leak. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2832) DMN support for DMN v1.2 serialization

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2832: -------------------------------------- Summary: DMN support for DMN v1.2 serialization Key: DROOLS-2832 URL: https://issues.jboss.org/browse/DROOLS-2832 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10799) [GSS](7.1.z) TCCL is not set to datasource module

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-10799: ----------------------------------- Summary: [GSS](7.1.z) TCCL is not set to datasource module Key: WFLY-10799 URL: https://issues.jboss.org/browse/WFLY-10799 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 13.0.0.Final Reporter: Brad Maxwell Assignee: Stefano Maestri TCCL is not set to datasource module User has a datasource that uses ORB classes and is getting a ClassNotFound. If a 3rd party JDBC driver implementation is using e. g. CORBA, the class loader is not set and thus the CORBA classes got loaded from the 'org.jboss.as.connector' modules class loader. So the root cause is the Thread Context ClassLoader (TCCL) is not set to the classloader/module of the datasource driver module. The particular datasource driver is making using of ORB.init which is a JDK class that looks on the TCCL and other places to load the class specified in ORB.init, but JCA when running has not set the TCCL thus the classes cannot be found. Having the TCCL set to the application is how JEE handles related situations to load application classes, so it would make sense that when JCA is running the datasource that it would have the TCCL set to the module of the datasource or a delegate class loader that sees both the datasource module and any other class loader that JCA might need, JBossWS does something similar. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2762) [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2762?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-2762: --------------------------------------- Story Points: 2 > [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table) > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2762 > URL: https://issues.jboss.org/browse/DROOLS-2762 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > > The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition): > - This component must be disabled (or hidden) when an existing/primitive data type is selected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10798) TCCL is not set to datasource module

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-10798: ----------------------------------- Summary: TCCL is not set to datasource module Key: WFLY-10798 URL: https://issues.jboss.org/browse/WFLY-10798 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 13.0.0.Final Reporter: Brad Maxwell Assignee: Stefano Maestri TCCL is not set to datasource module User has a datasource that uses ORB classes and is getting a ClassNotFound. If a 3rd party JDBC driver implementation is using e. g. CORBA, the class loader is not set and thus the CORBA classes got loaded from the 'org.jboss.as.connector' modules class loader. So the root cause is the Thread Context ClassLoader (TCCL) is not set to the classloader/module of the datasource driver module. The particular datasource driver is making using of ORB.init which is a JDK class that looks on the TCCL and other places to load the class specified in ORB.init, but JCA when running has not set the TCCL thus the classes cannot be found. Having the TCCL set to the application is how JEE handles related situations to load application classes, so it would make sense that when JCA is running the datasource that it would have the TCCL set to the module of the datasource or a delegate class loader that sees both the datasource module and any other class loader that JCA might need, JBossWS does something similar. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2716) [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated

by Guilherme Carreiro (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2716?page=com.atlassian.jira.plugi... ] Guilherme Carreiro updated DROOLS-2716: --------------------------------------- Story Points: 5 > [DMN Editor] Custom data-types - When the user changes a row in the treegrid-table, the DMN model needs to be updated > --------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2716 > URL: https://issues.jboss.org/browse/DROOLS-2716 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Labels: drools-tools > > - When the user changes a row in the "Field name" column, the DMN model needs to be updated; > - When the user changes a row in the "Field type" column, the DMN model needs to be updated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1381) it's not possible to build ironjacamar with JDK11

by Martin Simka (JIRA)

Martin Simka created JBJCA-1381: ----------------------------------- Summary: it's not possible to build ironjacamar with JDK11 Key: JBJCA-1381 URL: https://issues.jboss.org/browse/JBJCA-1381 Project: IronJacamar Issue Type: Bug Components: Build Environment: branch 1.4 java version "11-ea" 2018-09-25 Java(TM) SE Runtime Environment 18.9 (build 11-ea+25) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11-ea+25, mixed mode) Reporter: Martin Simka There are more issues when trying to build IJ with JDK11. I'm not sure if it will be requirement for WildFly to build with JDK11 but it is requirement for runtime. These are issues I'm aware of 1. {noformat} [javac] error: java.lang.NoClassDefFoundError: javax/annotation/Generated [javac] at org.jboss.logging.processor.generator.model.ClassModel.generateModel(ClassModel.java:122) [javac] at org.jboss.logging.processor.generator.model.ImplementationClassModel.generateModel(ImplementationClassModel.java:81) [javac] at org.jboss.logging.processor.generator.model.MessageLoggerImplementor.generateModel(MessageLoggerImplementor.java:92) [javac] at org.jboss.logging.processor.generator.model.ClassModel.create(ClassModel.java:104) [javac] at org.jboss.logging.processor.apt.ImplementationClassGenerator.processTypeElement(ImplementationClassGenerator.java:63) [javac] at org.jboss.logging.processor.apt.LoggingToolsProcessor.process(LoggingToolsProcessor.java:145) [javac] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:972) [javac] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:888) [javac] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1214) [javac] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1326) [javac] at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1258) [javac] at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:936) [javac] at jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:311) [javac] at jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:170) [javac] at jdk.compiler/com.sun.tools.javac.Main.compile(Main.java:57) [javac] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [javac] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [javac] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [javac] at java.base/java.lang.reflect.Method.invoke(Method.java:566) [javac] at org.apache.tools.ant.taskdefs.compilers.Javac13.execute(Javac13.java:58) [javac] at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:1395) [javac] at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:1121) [javac] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) [javac] at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) [javac] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [javac] at java.base/java.lang.reflect.Method.invoke(Method.java:566) [javac] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) [javac] at org.apache.tools.ant.Task.perform(Task.java:348) [javac] at org.apache.tools.ant.Target.execute(Target.java:435) [javac] at org.apache.tools.ant.Target.performTasks(Target.java:456) [javac] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405) [javac] at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38) [javac] at org.apache.tools.ant.Project.executeTargets(Project.java:1260) [javac] at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441) [javac] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) [javac] at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) [javac] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [javac] at java.base/java.lang.reflect.Method.invoke(Method.java:566) [javac] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) [javac] at org.apache.tools.ant.Task.perform(Task.java:348) [javac] at org.apache.tools.ant.Target.execute(Target.java:435) [javac] at org.apache.tools.ant.Target.performTasks(Target.java:456) [javac] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405) [javac] at org.apache.tools.ant.Project.executeTarget(Project.java:1376) [javac] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) [javac] at org.apache.tools.ant.Project.executeTargets(Project.java:1260) [javac] at org.apache.tools.ant.Main.runBuild(Main.java:857) [javac] at org.apache.tools.ant.Main.startAnt(Main.java:236) [javac] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:287) [javac] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:113) [javac] 2 errors {noformat} I tried to fix it by upgrading jboss-logging which seemed to work. Additionally I had to fix some {{tracef}} calls which were marked as ambiguous with new version. 2. {{java.xml.bind.*}} was removed from jdk we should probably define it as external dependency and there is likely more issues ... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2826) [DMN Designer] Unable to resolve type reference

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2826?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2826: -------------------------------- Description: During saving (also deploying) non empty dmn model, the error about resolving type reference appears in the server log. h3. Manual acceptance test - Save, Build and deploy dmn model from workbench (/) - Save, Build and deploy dmn model from trisotech (/) was:During saving (also deploying) non empty dmn model, the error about resolving type reference appears in the server log. > [DMN Designer] Unable to resolve type reference > ----------------------------------------------- > > Key: DROOLS-2826 > URL: https://issues.jboss.org/browse/DROOLS-2826 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: error.log > > > During saving (also deploying) non empty dmn model, the error about resolving type reference appears in the server log. > h3. Manual acceptance test > - Save, Build and deploy dmn model from workbench (/) > - Save, Build and deploy dmn model from trisotech (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-12) [Artemis upgrade] Output of CLI operations in messaging subsystem's server changed from 7.1

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFWIP-12?page=com.atlassian.jira.plugin.s... ] Jeff Mesnil commented on WFWIP-12: ---------------------------------- Fix for list-connections-as-json is blocked by https://issues.apache.org/jira/browse/ARTEMIS-1947 that needs to be reopened to properly serialize session metadata (patch available at https://github.com/apache/activemq-artemis/pull/2215) > [Artemis upgrade] Output of CLI operations in messaging subsystem's server changed from 7.1 > ------------------------------------------------------------------------------------------- > > Key: WFWIP-12 > URL: https://issues.jboss.org/browse/WFWIP-12 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Martin Styk > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq, feature-branch-blocker > Original Estimate: 2 hours > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Output of CLI operations in messaging subsystem's server element changed and it is is missing some attributes it used to display in EAP 7.1. > _Affected operations_ > *list-all-consumers-as-json* and *list-consumers-as-json* > Missing attributes > * destinationName > * destinationType > * durable > {noformat:title="7.1.0.GA"} > Result list-all-consumers-as-json{"outcome" => "success","result" => "[{\"consumerID\":0,\"connectionID\":\"-733935378\",\"sessionID\":\"fede1b60-04e9-11e8-9641-cc3d825a3be2\",\"queueName\":\"testSubscriberClientId-hornetqCliOperations.testSubscriber-hqServerCliOperations\",\"browseOnly\":false,\"creationTime\":1517226368495,\"destinationName\":\"testTopic\",\"destinationType\":\"topic\",\"durable\":true}]"} > {noformat} > {noformat:title="Wildfly latest with artemis 2.x"} > Result list-all-consumers-as-json{"outcome" => "success","result" => "[{\"consumerID\":0,\"connectionID\":\"784f1287\",\"sessionID\":\"f146b48e-04e3-11e8-bb50-cc3d825a3be2\",\"queueName\":\"jms.queue.testQueue\",\"browseOnly\":false,\"creationTime\":1517223768695,\"deliveringCount\":8}]"} > {noformat} > *list-connections-as-json* > Missing attributes > * clientID > {noformat:title="7.1.0.GA"} > "result" => "[{\"connectionID\":\"1343044951\",\"clientAddress\":\"/127.0.0.1:57038\",\"creationTime\":1517303830995,\"clientID\":\"testSubscriberClientId-hornetqCliOperations\"},{\"connectionID\":\"2052915500\",\"clientAddress\":\"/127.0.0.1:57040\",\"creationTime\":1517303831216},{\"connectionID\":\"668896556\",\"clientAddress\":\"/127.0.0.1:57042\",\"creationTime\":1517303831210},{\"connectionID\":\"2096792561\",\"clientAddress\":\"/127.0.0.1:57044\",\"creationTime\":1517303831223,\"clientID\":\"testPublisherClientId\"}]" > {noformat} > {noformat:title="Wildfly latest with artemis 2.x"} > "result" => "[{\"connectionID\":\"a8842f44\",\"clientAddress\":\"/127.0.0.1:55938\",\"creationTime\":1517298838294,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"c515bc06\",\"clientAddress\":\"/127.0.0.1:55936\",\"creationTime\":1517298837454,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":0},{\"connectionID\":\"b9a9153f-0592-11e8-80ff-54ee7547c83e\",\"clientAddress\":\"invm:0\",\"creationTime\":1517298837312,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":0},{\"connectionID\":\"fe42578a\",\"clientAddress\":\"/127.0.0.1:55944\",\"creationTime\":1517298838495,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"cde89186\",\"clientAddress\":\"/127.0.0.1:55940\",\"creationTime\":1517298838493,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2},{\"connectionID\":\"480099e7\",\"clientAddress\":\"/127.0.0.1:55942\",\"creationTime\":1517298838495,\"implementation\":\"RemotingConnectionImpl\",\"sessionCount\":2}]" > {noformat} > This is compatibility issue, as some scripts may depend on missing attributes. Customer's tooling which used to work with 7.1 may not work now. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018