[JBoss JIRA] (JGRP-2469) GossipRouter: make GraalVM-compliant
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2469?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2469:
--------------------------------
Didn't even need the {{init()}} method, as GossipRouter doesn't need any build time initialization; it starts up quickly enough (couple of millis), plus this way, we can have all of the command line options:
{noformat}
[belasmac] /Users/bela$ gossiprouter
setrlimit to increase file descriptor limit failed, errno 22
GossipRouter started in 1 ms listening on 0.0.0.0:12001
{noformat}
> GossipRouter: make GraalVM-compliant
> ------------------------------------
>
> Key: JGRP-2469
> URL: https://issues.redhat.com/browse/JGRP-2469
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.0.0.Alpha5
>
>
> Currently, GossipRouter starts threads in the constructor. This prohibits it to run under GraalVM as a native image, as threads cannot be started at build time.
> Create a separate method {{init()}}, which is called after the constructor and after all attributes have been set, but before {{start()}}.
> Alternative: use a builder:
> {code:java}
> router=GossipRouter.builder().setXX().build(); // creates server
> router.start();
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13387) Expose Jaeger Client Metrics
by Tobias Stadler (Jira)
Tobias Stadler created WFLY-13387:
-------------------------------------
Summary: Expose Jaeger Client Metrics
Key: WFLY-13387
URL: https://issues.redhat.com/browse/WFLY-13387
Project: WildFly
Issue Type: Feature Request
Components: MP Metrics, MP OpenTracing
Reporter: Tobias Stadler
Assignee: Jeff Mesnil
I would be nice, if the internal jaeger client metrics could be exposed via mp metrics endpoint.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFCORE-4915) Tighten up the dependency tree of subsystem-test
by Kabir Khan (Jira)
[ https://issues.redhat.com/browse/WFCORE-4915?page=com.atlassian.jira.plug... ]
Kabir Khan commented on WFCORE-4915:
------------------------------------
[~brian.stansberry] I think for the transformer tests (if we need those for) kind of rely on transitive dependencies behind the scenes for the dependencies of the legacy controller. But if I remember correctly (I've not looked) those are more added at runtime stuff. So I think it is possible to trim the tree for what is on the main dependency classpath.
> Tighten up the dependency tree of subsystem-test
> ------------------------------------------------
>
> Key: WFCORE-4915
> URL: https://issues.redhat.com/browse/WFCORE-4915
> Project: WildFly Core
> Issue Type: Task
> Components: Test Suite
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> In general I'd like to tighten (aka eliminate) up the use of transitive dependencies when various WildFly and WildFly Core maven modules depend on each other. Things should be explicit so unwanted coupling cannot creep in.
> The subsystem-test module is important in this regard as pretty much all extension modules depend on it's pom. So I want it and its children and its direct dependencies to only depend on other wf core modules directly, no transitive deps allowed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFCORE-4915) Tighten up the dependency tree of subsystem-test
by Kabir Khan (Jira)
[ https://issues.redhat.com/browse/WFCORE-4915?page=com.atlassian.jira.plug... ]
Kabir Khan edited comment on WFCORE-4915 at 4/17/20 6:51 AM:
-------------------------------------------------------------
[~brian.stansberry] I think for the transformer tests (if we need those for MP) kind of rely on transitive dependencies behind the scenes for the dependencies of the legacy controller. But if I remember correctly (I've not looked) those are more added at runtime stuff. So I think it is possible to trim the tree for what is on the main dependency classpath.
was (Author: kabirkhan):
[~brian.stansberry] I think for the transformer tests (if we need those for) kind of rely on transitive dependencies behind the scenes for the dependencies of the legacy controller. But if I remember correctly (I've not looked) those are more added at runtime stuff. So I think it is possible to trim the tree for what is on the main dependency classpath.
> Tighten up the dependency tree of subsystem-test
> ------------------------------------------------
>
> Key: WFCORE-4915
> URL: https://issues.redhat.com/browse/WFCORE-4915
> Project: WildFly Core
> Issue Type: Task
> Components: Test Suite
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Major
>
> In general I'd like to tighten (aka eliminate) up the use of transitive dependencies when various WildFly and WildFly Core maven modules depend on each other. Things should be explicit so unwanted coupling cannot creep in.
> The subsystem-test module is important in this regard as pretty much all extension modules depend on it's pom. So I want it and its children and its direct dependencies to only depend on other wf core modules directly, no transitive deps allowed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JGRP-2469) GossipRouter: make GraalVM-compliant
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2469?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2469:
--------------------------------
Added an {{init()}} method. Called by {{start()}} if user forgot to call it explictly.
The builder idea creates duplicate code (all attrs), so I rejected it.
> GossipRouter: make GraalVM-compliant
> ------------------------------------
>
> Key: JGRP-2469
> URL: https://issues.redhat.com/browse/JGRP-2469
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.0.0.Alpha5
>
>
> Currently, GossipRouter starts threads in the constructor. This prohibits it to run under GraalVM as a native image, as threads cannot be started at build time.
> Create a separate method {{init()}}, which is called after the constructor and after all attributes have been set, but before {{start()}}.
> Alternative: use a builder:
> {code:java}
> router=GossipRouter.builder().setXX().build(); // creates server
> router.start();
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JGRP-2469) GossipRouter: make GraalVM-compliant
by Bela Ban (Jira)
Bela Ban created JGRP-2469:
------------------------------
Summary: GossipRouter: make GraalVM-compliant
Key: JGRP-2469
URL: https://issues.redhat.com/browse/JGRP-2469
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 5.0.0.Alpha5
Currently, GossipRouter starts threads in the constructor. This prohibits it to run under GraalVM as a native image, as threads cannot be started at build time.
Create a separate method {{init()}}, which is called after the constructor and after all attributes have been set, but before {{start()}}.
Alternative: use a builder:
{code:java}
router=GossipRouter.builder().setXX().build(); // creates server
router.start();
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5250) [Scesim editor] Wrong context type scesim generation
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5250?page=com.atlassian.jira.plug... ]
Anna Dupliak commented on DROOLS-5250:
--------------------------------------
[~yamer] Thanks for noticing moved to DROOLS
> [Scesim editor] Wrong context type scesim generation
> -----------------------------------------------------
>
> Key: DROOLS-5250
> URL: https://issues.redhat.com/browse/DROOLS-5250
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.37.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Fix For: 7.37.0.Final
>
> Attachments: TestPossible types.dmn, image-2020-04-03-11-47-11-708.png
>
>
> When I create a data type in dmn like:
> -tDriver (Structure)
> --tNested (Structure)
> ---nested (string)
> --contextType(context)
> Then fact is generated as tNested.contextType.value but expect contextType.value
> !image-2020-04-03-11-47-11-708.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5250) [Scesim editor] Wrong context type scesim generation
by Anna Dupliak (Jira)
[ https://issues.redhat.com/browse/DROOLS-5250?page=com.atlassian.jira.plug... ]
Anna Dupliak moved KOGITO-1685 to DROOLS-5250:
----------------------------------------------
Project: Drools (was: Kogito)
Key: DROOLS-5250 (was: KOGITO-1685)
Docs QE Status: NEW
Component/s: Test Scenarios Editor
(was: Scenario Simulation)
Affects Version/s: 7.37.0.Final
(was: Kogito Tooling 0.2.9)
QE Status: NEW
Fix Version/s: 7.37.0.Final
(was: Kogito Tooling 0.4.1)
> [Scesim editor] Wrong context type scesim generation
> -----------------------------------------------------
>
> Key: DROOLS-5250
> URL: https://issues.redhat.com/browse/DROOLS-5250
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.37.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Fix For: 7.37.0.Final
>
> Attachments: TestPossible types.dmn, image-2020-04-03-11-47-11-708.png
>
>
> When I create a data type in dmn like:
> -tDriver (Structure)
> --tNested (Structure)
> ---nested (string)
> --contextType(context)
> Then fact is generated as tNested.contextType.value but expect contextType.value
> !image-2020-04-03-11-47-11-708.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4424) [DMN Designer] Copy of BKM node throws an error
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-4424?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-4424:
--------------------------------
Description:
User can create a diagram node copy by standard key compination *Ctrl+C* and *Ctrl+V*. The issue is if a BKM node is copied in this way. Then if user navigates into expression editor of the copied node there are two issues:
# The content is not copied
# Any attempt to define an expression type throws an error, see the attachement
h2. Acceptance test
https://github.com/kiegroup/kie-wb-common/pull/3272
was:
User can create a diagram node copy by standard key compination *Ctrl+C* and *Ctrl+V*. The issue is if a BKM node is copied in this way. Then if user navigates into expression editor of the copied node there are two issues:
# The content is not copied
# Any attempt to define an expression type throws an error, see the attachement
> [DMN Designer] Copy of BKM node throws an error
> -----------------------------------------------
>
> Key: DROOLS-4424
> URL: https://issues.redhat.com/browse/DROOLS-4424
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.25.0.Final, 7.36.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2019-08-12 09-31-02.png
>
>
> User can create a diagram node copy by standard key compination *Ctrl+C* and *Ctrl+V*. The issue is if a BKM node is copied in this way. Then if user navigates into expression editor of the copied node there are two issues:
> # The content is not copied
> # Any attempt to define an expression type throws an error, see the attachement
> h2. Acceptance test
> https://github.com/kiegroup/kie-wb-common/pull/3272
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13386) Hung process instances and associated server.log WARN "Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' "
by Enrique González Martínez (Jira)
[ https://issues.redhat.com/browse/WFLY-13386?page=com.atlassian.jira.plugi... ]
Enrique González Martínez reassigned WFLY-13386:
------------------------------------------------
Assignee: Enrique González Martínez (was: Brian Stansberry)
> Hung process instances and associated server.log WARN "Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' "
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13386
> URL: https://issues.redhat.com/browse/WFLY-13386
> Project: WildFly
> Issue Type: Bug
> Reporter: Enrique González Martínez
> Assignee: Enrique González Martínez
> Priority: Major
>
> When a timer is reloaded for the first time in other node there are no listeners attached to it causing this problem (only in cluster environments with db timers)
> {code}
> 2020-04-15 16:43:57,733 WARN [org.jboss.as.ejb3.timer] (Timer-1) WFLYEJB0161: Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' (id=33170e5f-3b34-4503-8796-9b5e6871c074) from its persistent state: java.lang.NullPointerException
> at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence$RefreshTask.run(DatabaseTimerPersistence.java:851)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years