[JBoss JIRA] (WFLY-12486) Memory leak in OpenTracing when deployment is redeployed multiple times
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-12486?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet commented on WFLY-12486:
------------------------------------------
https://github.com/wildfly/wildfly/pull/12878 if https://github.com/wildfly/wildfly/pull/12836 doesn't make it to feature freeze.
> Memory leak in OpenTracing when deployment is redeployed multiple times
> -----------------------------------------------------------------------
>
> Key: WFLY-12486
> URL: https://issues.redhat.com/browse/WFLY-12486
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Affects Versions: 17.0.0.Final, 17.0.1.Final, 18.0.1.Final
> Reporter: Jan Stourac
> Assignee: Emmanuel Hugonnet
> Priority: Blocker
> Attachments: memory-leak-bad.png, memory-leak-good.png, wildfly-thread-leak.png
>
>
> There seems to be a memory leak when a deployment is redeployed multiple times (100 times in our test). This is very similar to what has been described in WFLY-10991. Also first commit this started to happen is [this one|https://github.com/wildfly/wildfly/commit/74170b5f49dd83f6b9ebd489f85...] - JaegerTracing and Apache Thrift dependencies update. Thus I selected MP OpenTracing component for this issue.
> Test and deployment is same as is described in WFLY-10991.
> Size of the extra heap in use is about 27MB plus when compared to the initial size before multiple redeploy operations.
> I've tried to check manually via [visualVM|https://visualvm.github.io/] tool. Screenshot with suspicious jaegertracing instances are attached - there are much more jaegertracing class instances with new version of Jager Tracing and Apache Thrift dependencies, which is suspicious.
> Interesting thing is that when microprofile-opentracing-smallrye subsystem is removed via:
> {code}
> /subsystem=microprofile-opentracing-smallrye:remove()
> {code}
> the memory leak is still present. This is kind of confusing to me.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (WFCORE-4787) Fix or disable failing tests on IBM JDK
by Peter Mackay (Jira)
Peter Mackay created WFCORE-4787:
------------------------------------
Summary: Fix or disable failing tests on IBM JDK
Key: WFCORE-4787
URL: https://issues.redhat.com/browse/WFCORE-4787
Project: WildFly Core
Issue Type: Bug
Components: Logging
Reporter: Peter Mackay
Assignee: Richard Opalka
Fix For: 10.0.0.Beta3, 10.0.0.Final
The following tests are failing on latest IBM JDK 8:
---
# testsuite/standalone
SilentModeTestCase
# testsuite/manualmode
CLIEmbedHostControllerTestCase
CLIEmbedServerTestCase
---
Tested on:
---
java version "1.8.0_211"
Java(TM) SE Runtime Environment (build 8.0.5.36 - pxa6480sr5fp36-20190510_01(SR5 FP36))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190502_415899 (JIT enabled, AOT enabled)
OpenJ9 - 46e57f9
OMR - 06a046a
IBM - 0b909bf)
JCL - 20190409_01 based on Oracle jdk8u211-b25
---
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-3048) [DMN Designer] CellEditorControl needs to issue a new instance per use
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-3048?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-3048:
--------------------------------
Attachment: applicationscope-vs-dependendscope.webm
> [DMN Designer] CellEditorControl needs to issue a new instance per use
> ----------------------------------------------------------------------
>
> Key: DROOLS-3048
> URL: https://issues.redhat.com/browse/DROOLS-3048
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.12.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: applicationscope-vs-dependendscope.webm
>
>
> A {{Popover}} used to edit a cell or column header (or any other DOM-based editor for that matter) disappears following a change in the widget that causes a {{Layer.draw()}} if the grid is sufficiently wide that there is a column not visible on screen.
> All cells/columns that use {{CellEditorControls}} (containing, for example, the {{Popover}}) share a single instance from {{CellEditorControl}} and hence although the User makes a change in a visible column the invisible column (scrolled off screen) has its DOM resources destroyed that is the same instance as that for the visible column.
> See https://github.com/kiegroup/appformer/blob/master/uberfire-extensions/ube.... If a column is not in the _body_ or _floating_ columns collection its DOM resources are destroyed.
> I probably need to ensure different instances of {{CellEditorControl}} are created for each column/cell where we currently share the same instance. Also check for destruction of DOM elements in {{Document}} when grids/columns etc are destroyed.
> h3. Acceptance criteria
> # Create a DMN model
> # Add a Decision
> # Set its expression to a Decision Table
> # Add multiple Input and Output columns so that the table is wider than the visible screen space (i.e. some columns are not rendered)
> # Click on the header of a visible column
> # The Name/Data-type popup should appear
> # Repeat for expression type of Relation
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4902) Can not use mod operators (%) in when clause.
by xb l (Jira)
[ https://issues.redhat.com/browse/DROOLS-4902?page=com.atlassian.jira.plug... ]
xb l updated DROOLS-4902:
-------------------------
Summary: Can not use mod operators (%) in when clause. (was: Can not use mod operators (%) in when clouse.)
> Can not use mod operators (%) in when clause.
> ---------------------------------------------
>
> Key: DROOLS-4902
> URL: https://issues.redhat.com/browse/DROOLS-4902
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.31.0.Final
> Reporter: xb l
> Assignee: Mario Fusco
> Priority: Major
>
> When I study drools , I write a rule use divide operator
> {code:java}
> rule "Buzz" salience 2
> when
> $n: Number( this / 5 == 3 )
> then
> System.out.println("Buzz");
> end
> {code}
> It's OK.
> But:
> {code:java}
> rule "Buzz" salience 2
> when
> $n: Number( this % 5 == 0 )
> then
> System.out.println("Buzz");
> end
> {code}
> Report parser error: Unable to Analyse Expression this % 5 == 0:
> The drools document mentioned the same example:
> Person( age > 100 && ( age % 10 == 0 ) )
> % is Multiplicative operators, why parser error?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4902) Can not use mod operators (%) in when closures.
by xb l (Jira)
[ https://issues.redhat.com/browse/DROOLS-4902?page=com.atlassian.jira.plug... ]
xb l updated DROOLS-4902:
-------------------------
Description:
When I study drools , I write a rule use divide operator
{code:java}
rule "Buzz" salience 2
when
$n: Number( this / 5 == 3 )
then
System.out.println("Buzz");
end
{code}
It's OK.
But:
{code:java}
rule "Buzz" salience 2
when
$n: Number( this % 5 == 0 )
then
System.out.println("Buzz");
end
{code}
Report parser error: Unable to Analyse Expression this % 5 == 0:
The drools document mentioned the same example:
Person( age > 100 && ( age % 10 == 0 ) )
% is Multiplicative operators, why parser error?
was:
When I study drools , I write a rule use divide operator
{code:java}
rule "Buzz" salience 2
when
$n: Number( this / 5 == 3 )
then
System.out.println("Buzz");
end
{code}
It's OK.
But:
{code:java}
rule "Buzz" salience 2
when
$n: Number( this % 5 == 0 )
then
System.out.println("Buzz");
end
{code}
Report parser error: Unable to Analyse Expression this % 5 == 0:
> Can not use mod operators (%) in when closures.
> -----------------------------------------------
>
> Key: DROOLS-4902
> URL: https://issues.redhat.com/browse/DROOLS-4902
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.31.0.Final
> Reporter: xb l
> Assignee: Mario Fusco
> Priority: Major
>
> When I study drools , I write a rule use divide operator
> {code:java}
> rule "Buzz" salience 2
> when
> $n: Number( this / 5 == 3 )
> then
> System.out.println("Buzz");
> end
> {code}
> It's OK.
> But:
> {code:java}
> rule "Buzz" salience 2
> when
> $n: Number( this % 5 == 0 )
> then
> System.out.println("Buzz");
> end
> {code}
> Report parser error: Unable to Analyse Expression this % 5 == 0:
> The drools document mentioned the same example:
> Person( age > 100 && ( age % 10 == 0 ) )
> % is Multiplicative operators, why parser error?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (DROOLS-4902) Can not use mod operators (%) in when clouse.
by xb l (Jira)
[ https://issues.redhat.com/browse/DROOLS-4902?page=com.atlassian.jira.plug... ]
xb l updated DROOLS-4902:
-------------------------
Summary: Can not use mod operators (%) in when clouse. (was: Can not use mod operators (%) in when closures.)
> Can not use mod operators (%) in when clouse.
> ---------------------------------------------
>
> Key: DROOLS-4902
> URL: https://issues.redhat.com/browse/DROOLS-4902
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.31.0.Final
> Reporter: xb l
> Assignee: Mario Fusco
> Priority: Major
>
> When I study drools , I write a rule use divide operator
> {code:java}
> rule "Buzz" salience 2
> when
> $n: Number( this / 5 == 3 )
> then
> System.out.println("Buzz");
> end
> {code}
> It's OK.
> But:
> {code:java}
> rule "Buzz" salience 2
> when
> $n: Number( this % 5 == 0 )
> then
> System.out.println("Buzz");
> end
> {code}
> Report parser error: Unable to Analyse Expression this % 5 == 0:
> The drools document mentioned the same example:
> Person( age > 100 && ( age % 10 == 0 ) )
> % is Multiplicative operators, why parser error?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies
by Lin Gao (Jira)
[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ]
Lin Gao commented on WFLY-12913:
--------------------------------
+com.sun.istack+ comes from [istack-commons repository|https://github.com/eclipse-ee4j/jaxb-istack-commons/tree/maste...], which is different than the jaxb-ri one. The version is different as well.
The version of +com.sun.istack+ used by WildFly is +3.0.7+, looks like we need to upgrade it as well together with jaxb-ri.
> Rationalize com.sum.xml.bind module dependencies
> ------------------------------------------------
>
> Key: WFLY-12913
> URL: https://issues.redhat.com/browse/WFLY-12913
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate, REST, Web Services
> Reporter: Brian Stansberry
> Assignee: Lin Gao
> Priority: Minor
>
> The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents:
> {code}
> <module name="com.github.relaxng" export="true" />
> <module name="com.sun.istack" export="true" />
> <module name="com.sun.xml.txw2" export="true" />
> <module name="com.sun.xsom" export="true" />
> {code}
> Task is to:
> 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules.
> 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules.
> 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months
[JBoss JIRA] (WFLY-12913) Rationalize com.sum.xml.bind module dependencies
by Lin Gao (Jira)
[ https://issues.redhat.com/browse/WFLY-12913?page=com.atlassian.jira.plugi... ]
Lin Gao edited comment on WFLY-12913 at 1/6/20 5:38 AM:
--------------------------------------------------------
+com.sun.istack+ comes from [istack-commons repository|https://github.com/eclipse-ee4j/jaxb-istack-commons/tree/maste...], which is different than the jaxb-ri one. The version is different as well.
The version of +com.sun.istack+ used by WildFly is +3.0.7+, looks like we need to upgrade it as well(to 3.0.10) together with jaxb-ri.
was (Author: gaol):
+com.sun.istack+ comes from [istack-commons repository|https://github.com/eclipse-ee4j/jaxb-istack-commons/tree/maste...], which is different than the jaxb-ri one. The version is different as well.
The version of +com.sun.istack+ used by WildFly is +3.0.7+, looks like we need to upgrade it as well together with jaxb-ri.
> Rationalize com.sum.xml.bind module dependencies
> ------------------------------------------------
>
> Key: WFLY-12913
> URL: https://issues.redhat.com/browse/WFLY-12913
> Project: WildFly
> Issue Type: Task
> Components: JPA / Hibernate, REST, Web Services
> Reporter: Brian Stansberry
> Assignee: Lin Gao
> Priority: Minor
>
> The com.sun.xml.bind module depends on and exports four other modules, and those modules in turn are private and have no other dependents:
> {code}
> <module name="com.github.relaxng" export="true" />
> <module name="com.sun.istack" export="true" />
> <module name="com.sun.xml.txw2" export="true" />
> <module name="com.sun.xsom" export="true" />
> {code}
> Task is to:
> 1) Write to wildfly-dev mail list to check for any projects that layer on WildFly that directly use these modules.
> 2) Write to jboss-layered-products (internal Red Hat) mail list to check for any products based on WF/EAP that directly use these modules.
> 3) Assuming no positive responses, make the artifacts from the above four modules direct artifacts of the com.sun.xml.bind module, add any needed module dependencies to con.sum.xml.bind, and get rid of those four modules.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 6 months