January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4959) Package name does not changes on copying of an existing package

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4959?page=com.atlassian.jira.plug... ] Toni Rikkola commented on DROOLS-4959: -------------------------------------- [~nicktsek] I could use some additional information about where the project was opened and how it was moved in that tool? > Package name does not changes on copying of an existing package > --------------------------------------------------------------- > > Key: DROOLS-4959 > URL: https://issues.redhat.com/browse/DROOLS-4959 > Project: Drools > Issue Type: Bug > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > > After copying a package to a new one, all copied resources will remain referencing the existing one. > This becomes a bigger issue once you use guided rules, which their source cannot be edited. > Due to that, duplication alerts will be raised. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4961) User / Role Permissions on package level

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4961?page=com.atlassian.jira.plug... ] Toni Rikkola commented on DROOLS-4961: -------------------------------------- [~nicktsek] The best way to do this at the moment is to use seperate projects for what would be in these packages. > User / Role Permissions on package level > ---------------------------------------- > > Key: DROOLS-4961 > URL: https://issues.redhat.com/browse/DROOLS-4961 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: David Gutierrez > Priority: Major > Labels: drools-tools > > It will be amazingly helpful to have the ability to minimize the access / permissions of a user / group on package level. > Within a project you can define several packages - for different purposes - and you need each team to be able to work on / view a specific package. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4960) Reference a data object from one project to another one.

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4960?page=com.atlassian.jira.plug... ] Toni Rikkola resolved DROOLS-4960. ---------------------------------- Resolution: Explained I'll close this. Since the projects in workbench are actually Maven projects that can have each other as a dependency like Michael Anstis mentioned. > Reference a data object from one project to another one. > -------------------------------------------------------- > > Key: DROOLS-4960 > URL: https://issues.redhat.com/browse/DROOLS-4960 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Currently, nothing can be referenced from one project to another one. > Using a common area to create the Data Objects etc. and reference them on several projects will be very helpful. > Java-wise is like we are creating two projects and we reference the first one in the second one, in order to use some classes in our code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4809) Allow composite operation to read the model without need to acquired the write lock in domain mode

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-4809?page=com.atlassian.jira.plug... ] Yeray Borges updated WFCORE-4809: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4064 > Allow composite operation to read the model without need to acquired the write lock in domain mode > -------------------------------------------------------------------------------------------------- > > Key: WFCORE-4809 > URL: https://issues.redhat.com/browse/WFCORE-4809 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > > Currently, the web console is highly affected by the write lock acquisition. Most of the read operations done by the web console are translated into composite operations, that under some circumstances (target to a single host, non-wildcards..), require the DC write lock. This write lock acquisition has a huge impact on the web console since each operation is queued until the lock is released. > As an example, if we have a deployment that takes some minutes in the middle the user is clicking to see the server status, soon the web console gets unresponsible. > This issue tries to reduce the write lock acquisition in these cases and allow read operations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1924) EntityTest Failing on OpenJ9

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1924: ------------------------------------- Summary: EntityTest Failing on OpenJ9 Key: ELY-1924 URL: https://issues.redhat.com/browse/ELY-1924 Project: WildFly Elytron Issue Type: Bug Components: Testsuite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.11.1.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4959) Package name does not changes on copying of an existing package

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4959?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-4959: ---------------------------------------- [~Rikkola] I'd be tempted to punt to the _core_ team.. this is not a {{drools-tooling}} specific requirement... The _mechanism_ is already available (IIRC {{CopyHelper}} and {{RenameHelper}} interfaces)... > Package name does not changes on copying of an existing package > --------------------------------------------------------------- > > Key: DROOLS-4959 > URL: https://issues.redhat.com/browse/DROOLS-4959 > Project: Drools > Issue Type: Bug > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > After copying a package to a new one, all copied resources will remain referencing the existing one. > This becomes a bigger issue once you use guided rules, which their source cannot be edited. > Due to that, duplication alerts will be raised. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4960) Reference a data object from one project to another one.

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4960?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-4960: ---------------------------------------- You should create one project containing the DO's etc you want to share and then add it as a dependency to the other project. > Reference a data object from one project to another one. > -------------------------------------------------------- > > Key: DROOLS-4960 > URL: https://issues.redhat.com/browse/DROOLS-4960 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Currently, nothing can be referenced from one project to another one. > Using a common area to create the Data Objects etc. and reference them on several projects will be very helpful. > Java-wise is like we are creating two projects and we reference the first one in the second one, in order to use some classes in our code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4961) User / Role Permissions on package level

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4961?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-4961: -------------------------------------- Assignee: David Gutierrez (was: Toni Rikkola) > User / Role Permissions on package level > ---------------------------------------- > > Key: DROOLS-4961 > URL: https://issues.redhat.com/browse/DROOLS-4961 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: David Gutierrez > Priority: Major > Labels: drools-tools > > It will be amazingly helpful to have the ability to minimize the access / permissions of a user / group on package level. > Within a project you can define several packages - for different purposes - and you need each team to be able to work on / view a specific package. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4966) [DMN Designer] Dragging a field at the bottom of type designer

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4966: -------------------------------------- Summary: [DMN Designer] Dragging a field at the bottom of type designer Key: DROOLS-4966 URL: https://issues.redhat.com/browse/DROOLS-4966 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.32.0.Final Reporter: Edoardo Vacchi Assignee: Michael Anstis Attachments: drag-2.gif - add several fields/structures so that the list exceeds the viewport - scroll down to the bottom of the editor - try dragging the bottom field - the view does not scroll, but the field will jump "up" at seemingly random positions at the top it's nearly impossible to reorder a field when it's at the bottom -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4964) [DMN Designer] Type designer scrolls up to the top when any element of the table is clicked

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4964?page=com.atlassian.jira.plug... ] Edoardo Vacchi updated DROOLS-4964: ----------------------------------- Affects Version/s: 7.32.0.Final > [DMN Designer] Type designer scrolls up to the top when any element of the table is clicked > ------------------------------------------------------------------------------------------- > > Key: DROOLS-4964 > URL: https://issues.redhat.com/browse/DROOLS-4964 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Edoardo Vacchi > Assignee: Michael Anstis > Priority: Major > Attachments: scroll-up.gif > > > - scroll down > - click on a non-active part of the table (i.e. not a button) > result: the viewport scrolls up to the top > !scroll-up.gif! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4965) [DMN Designer] Dragged structure fields nest in a counterintuitive way

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4965?page=com.atlassian.jira.plug... ] Edoardo Vacchi updated DROOLS-4965: ----------------------------------- Fix Version/s: (was: 7.32.0.Final) Affects Version/s: 7.32.0.Final > [DMN Designer] Dragged structure fields nest in a counterintuitive way > ---------------------------------------------------------------------- > > Key: DROOLS-4965 > URL: https://issues.redhat.com/browse/DROOLS-4965 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.32.0.Final > Reporter: Edoardo Vacchi > Assignee: Michael Anstis > Priority: Major > Attachments: drag-1.gif > > > Because the handle is aligned leftmost, I tend to keep it aligned to the left; > but this causes the field to be "unnested" and moved to toplevel. > I suggest to draw the handle aligned to label, instead of the border, suggesting that drag has to start from that point > !drag-1.gif! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4965) [DMN Designer] Dragged structure fields nest in a counterintuitive way

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4965: -------------------------------------- Summary: [DMN Designer] Dragged structure fields nest in a counterintuitive way Key: DROOLS-4965 URL: https://issues.redhat.com/browse/DROOLS-4965 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Edoardo Vacchi Assignee: Michael Anstis Fix For: 7.32.0.Final Attachments: drag-1.gif Because the handle is aligned leftmost, I tend to keep it aligned to the left; but this causes the field to be "unnested" and moved to toplevel. I suggest to draw the handle aligned to label, instead of the border, suggesting that drag has to start from that point !drag-1.gif! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4964) [DMN Designer] Type designer scrolls up to the top when any element of the table is clicked

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4964: -------------------------------------- Summary: [DMN Designer] Type designer scrolls up to the top when any element of the table is clicked Key: DROOLS-4964 URL: https://issues.redhat.com/browse/DROOLS-4964 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Edoardo Vacchi Assignee: Michael Anstis Attachments: scroll-up.gif - scroll down - click on a non-active part of the table (i.e. not a button) result: the viewport scrolls up to the top !scroll-up.gif! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4963) [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-4963: -------------------------------------- Summary: [DMN Designer] Type designer does not show save/cancel when many constraints are presents and the inspector is open Key: DROOLS-4963 URL: https://issues.redhat.com/browse/DROOLS-4963 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.32.0.Final Reporter: Edoardo Vacchi Assignee: Michael Anstis Attachments: Screenshot from 2020-01-22 16-16-29.png, Screenshot from 2020-01-22 16-16-29.png hiding the inspector on the right-hand side uncovers the save/cancel buttons !Screenshot from 2020-01-22 16-16-29.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13006) KUBE_PING Occasional NPE on shutdown

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13006?page=com.atlassian.jira.plugi... ] Radoslav Husar commented on WFLY-13006: --------------------------------------- Requires 1.0.15.Final upgrade. > KUBE_PING Occasional NPE on shutdown > ------------------------------------- > > Key: WFLY-13006 > URL: https://issues.redhat.com/browse/WFLY-13006 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > 05:52:55,313 ERROR [org.jgroups.util.TimeScheduler3] (thread-6,null,xa-load-2) JGRP000169: failed executing task MERGE3: InfoSender: java.lang.NullPointerException > at org.jgroups.protocols.kubernetes.KUBE_PING.readAll(KUBE_PING.java:313) > at org.jgroups.protocols.kubernetes.KUBE_PING.findMembers(KUBE_PING.java:206) > at org.jgroups.protocols.Discovery.invokeFindMembers(Discovery.java:216) > at org.jgroups.protocols.Discovery.findMembers(Discovery.java:241) > at org.jgroups.protocols.Discovery.down(Discovery.java:384) > at org.jgroups.protocols.MERGE3$InfoSender.run(MERGE3.java:413) > at org.jgroups.util.TimeScheduler3$Task.run(TimeScheduler3.java:328) > at org.jgroups.util.TimeScheduler3$RecurringTask.run(TimeScheduler3.java:362) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at org.jboss.as.clustering.jgroups.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:52) > at java.lang.Thread.run(Thread.java:748) > https://github.com/jgroups-extras/jgroups-kubernetes/issues/39 > https://github.com/jgroups-extras/jgroups-kubernetes/pull/88 > Will be resolved with a next jgroups-kubernetes upgrade. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2438) MPerf: add -nohup option

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2438?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2438. ---------------------------- Resolution: Done > MPerf: add -nohup option > ------------------------ > > Key: JGRP-2438 > URL: https://issues.redhat.com/browse/JGRP-2438 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.0, 4.0.22 > > > Add -nohup option to MPerf -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2438) MPerf: add -nohup option

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2438?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2438: --------------------------- Description: Add -nohup option to MPerf Fix Version/s: 4.0.22 > MPerf: add -nohup option > ------------------------ > > Key: JGRP-2438 > URL: https://issues.redhat.com/browse/JGRP-2438 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.0, 4.0.22 > > > Add -nohup option to MPerf -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2438) MPerf: add -nohup option

by Bela Ban (Jira)

Bela Ban created JGRP-2438: ------------------------------ Summary: MPerf: add -nohup option Key: JGRP-2438 URL: https://issues.redhat.com/browse/JGRP-2438 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0, 4.2.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4936) Unsaved changes dialog appears even if it just have been saved

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4936?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4936: -------------------------------- Tester: Anna Dupliak > Unsaved changes dialog appears even if it just have been saved > -------------------------------------------------------------- > > Key: DROOLS-4936 > URL: https://issues.redhat.com/browse/DROOLS-4936 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Open a GRE file. Add a fact pattern. Save. > Close and the editor still thinks it has not been saved. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13007) New subsystem for configuring clustering API implementations

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13007?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13007: -------------------------------- Description: Currently, WildFly creates services for the following objects for every JGroups channel: * CommandDispatcherFactory * Group ... and creates services the following objects for every Infinispan cache: * SingletonServiceConfiguratorFactory * ServiceProviderRegistry * Registry * Group Only some of these services are ever started. If we instead created a separate subsystem that configures these objects, we could significantly reduce the number of services created (but never started) by the jgroups and infinispan subsystems. This has a number of benefits for users as well: * Increases overall visibility of the public clustering API * Simplifies the current mysterious state of service wiring by establishing explicit capability requirements where necessary * Simplifies inter-component capability requirements (e.g. SingletonServiceConfiguratorFactory depends on ServiceProviderRegistry and CommandDispatcherFactory). was: Currently, WildFly creates services for the following objects for every JGroups channel: * CommandDispatcherFactory * Group ... and creates services the following objects for every Infinispan cache: * SingletonServiceConfiguratorFactory * ServiceProviderRegistry * Registry * Group Only some of these services are ever started. If we instead created a separate subsystem that configures these objects, we could significantly reduce the number of services created (but never started) by the jgroups and infinispan subsystems. This has a number of benefits for users as well: * Increases overall visibility of the public clustering API * Simplifies the current mysterious state of service wiring by establishing explicit capability requirements where necessary > New subsystem for configuring clustering API implementations > ------------------------------------------------------------ > > Key: WFLY-13007 > URL: https://issues.redhat.com/browse/WFLY-13007 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 19.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Currently, WildFly creates services for the following objects for every JGroups channel: > * CommandDispatcherFactory > * Group > ... and creates services the following objects for every Infinispan cache: > * SingletonServiceConfiguratorFactory > * ServiceProviderRegistry > * Registry > * Group > Only some of these services are ever started. If we instead created a separate subsystem that configures these objects, we could significantly reduce the number of services created (but never started) by the jgroups and infinispan subsystems. > This has a number of benefits for users as well: > * Increases overall visibility of the public clustering API > * Simplifies the current mysterious state of service wiring by establishing explicit capability requirements where necessary > * Simplifies inter-component capability requirements (e.g. SingletonServiceConfiguratorFactory depends on ServiceProviderRegistry and CommandDispatcherFactory). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4961) User / Role Permissions on package level

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4961?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4961: --------------------------------- Labels: drools-tools (was: ) > User / Role Permissions on package level > ---------------------------------------- > > Key: DROOLS-4961 > URL: https://issues.redhat.com/browse/DROOLS-4961 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > It will be amazingly helpful to have the ability to minimize the access / permissions of a user / group on package level. > Within a project you can define several packages - for different purposes - and you need each team to be able to work on / view a specific package. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4960) Reference a data object from one project to another one.

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4960?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-4960: ------------------------------------ Assignee: Toni Rikkola (was: Mario Fusco) > Reference a data object from one project to another one. > -------------------------------------------------------- > > Key: DROOLS-4960 > URL: https://issues.redhat.com/browse/DROOLS-4960 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Currently, nothing can be referenced from one project to another one. > Using a common area to create the Data Objects etc. and reference them on several projects will be very helpful. > Java-wise is like we are creating two projects and we reference the first one in the second one, in order to use some classes in our code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4961) User / Role Permissions on package level

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4961?page=com.atlassian.jira.plug... ] Mario Fusco reassigned DROOLS-4961: ----------------------------------- Assignee: Toni Rikkola (was: Mario Fusco) > User / Role Permissions on package level > ---------------------------------------- > > Key: DROOLS-4961 > URL: https://issues.redhat.com/browse/DROOLS-4961 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > It will be amazingly helpful to have the ability to minimize the access / permissions of a user / group on package level. > Within a project you can define several packages - for different purposes - and you need each team to be able to work on / view a specific package. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4959) Package name does not changes on copying of an existing package

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4959?page=com.atlassian.jira.plug... ] Mario Fusco reassigned DROOLS-4959: ----------------------------------- Assignee: Toni Rikkola (was: Mario Fusco) > Package name does not changes on copying of an existing package > --------------------------------------------------------------- > > Key: DROOLS-4959 > URL: https://issues.redhat.com/browse/DROOLS-4959 > Project: Drools > Issue Type: Bug > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > After copying a package to a new one, all copied resources will remain referencing the existing one. > This becomes a bigger issue once you use guided rules, which their source cannot be edited. > Due to that, duplication alerts will be raised. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4960) Reference a data object from one project to another one.

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4960?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4960: --------------------------------- Labels: drools-tools (was: ) > Reference a data object from one project to another one. > -------------------------------------------------------- > > Key: DROOLS-4960 > URL: https://issues.redhat.com/browse/DROOLS-4960 > Project: Drools > Issue Type: Feature Request > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Currently, nothing can be referenced from one project to another one. > Using a common area to create the Data Objects etc. and reference them on several projects will be very helpful. > Java-wise is like we are creating two projects and we reference the first one in the second one, in order to use some classes in our code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4959) Package name does not changes on copying of an existing package

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4959?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4959: --------------------------------- Labels: drools-tools (was: ) > Package name does not changes on copying of an existing package > --------------------------------------------------------------- > > Key: DROOLS-4959 > URL: https://issues.redhat.com/browse/DROOLS-4959 > Project: Drools > Issue Type: Bug > Affects Versions: 7.31.0.Final > Reporter: Nikos Tsekouras > Assignee: Mario Fusco > Priority: Major > Labels: drools-tools > > After copying a package to a new one, all copied resources will remain referencing the existing one. > This becomes a bigger issue once you use guided rules, which their source cannot be edited. > Due to that, duplication alerts will be raised. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4809) Allow composite operation to read the model without need to acquired the write lock in domain mode

by Yeray Borges (Jira)

Yeray Borges created WFCORE-4809: ------------------------------------ Summary: Allow composite operation to read the model without need to acquired the write lock in domain mode Key: WFCORE-4809 URL: https://issues.redhat.com/browse/WFCORE-4809 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Yeray Borges Assignee: Yeray Borges Currently, the web console is highly affected by the write lock acquisition. Most of the read operations done by the web console are translated into composite operations, that under some circumstances (target to a single host, non-wildcards..), require the DC write lock. This write lock acquisition has a huge impact on the web console since each operation is queued until the lock is released. As an example, if we have a deployment that takes some minutes in the middle the user is clicking to see the server status, soon the web console gets unresponsible. This issue tries to reduce the write lock acquisition in these cases and allow read operations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4791) HttpManagementConstantHeadersTestCase causes tests failures

by Tomas Terem (Jira)

[ https://issues.redhat.com/browse/WFCORE-4791?page=com.atlassian.jira.plug... ] Tomas Terem commented on WFCORE-4791: ------------------------------------- Hi [~ropalka], I've created a PR: https://github.com/wildfly/wildfly-core/pull/4063. Can you execute tests on your laptop (since that was the only place where issue could be observed) and verify if it's fixed? > HttpManagementConstantHeadersTestCase causes tests failures > ----------------------------------------------------------- > > Key: WFCORE-4791 > URL: https://issues.redhat.com/browse/WFCORE-4791 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Reporter: Richard Opalka > Assignee: Tomas Terem > Priority: Major > Fix For: 11.0.0.Beta8 > > Attachments: testsuite.log > > > Commit 68928b0b in WildFly-Core introduced new regression. > High probably test doesn't do proper test environment clean up > and some tests following it are thus failing. The issue isn't visible > in our CI environment so it probably depends on actual tests ordering. > I am able to reproduce this issue on my laptop always. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1056) Try OCP 4.4 on IPv6 in PSI

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1056: ------------------------------------ Summary: Try OCP 4.4 on IPv6 in PSI Key: SWSQE-1056 URL: https://issues.redhat.com/browse/SWSQE-1056 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13007) New subsystem for configuring clustering API implementations

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13007: ----------------------------------- Summary: New subsystem for configuring clustering API implementations Key: WFLY-13007 URL: https://issues.redhat.com/browse/WFLY-13007 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 19.0.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, WildFly creates services for the following objects for every JGroups channel: * CommandDispatcherFactory * Group ... and creates services the following objects for every Infinispan cache: * SingletonServiceConfiguratorFactory * ServiceProviderRegistry * Registry * Group Only some of these services are ever started. If we instead created a separate subsystem that configures these objects, we could significantly reduce the number of services created (but never started) by the jgroups and infinispan subsystems. This has a number of benefits for users as well: * Increases overall visibility of the public clustering API * Simplifies the current mysterious state of service wiring by establishing explicit capability requirements where necessary -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13006) KUBE_PING Occasional NPE on shutdown

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-13006: ------------------------------------- Summary: KUBE_PING Occasional NPE on shutdown Key: WFLY-13006 URL: https://issues.redhat.com/browse/WFLY-13006 Project: WildFly Issue Type: Bug Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar 05:52:55,313 ERROR [org.jgroups.util.TimeScheduler3] (thread-6,null,xa-load-2) JGRP000169: failed executing task MERGE3: InfoSender: java.lang.NullPointerException at org.jgroups.protocols.kubernetes.KUBE_PING.readAll(KUBE_PING.java:313) at org.jgroups.protocols.kubernetes.KUBE_PING.findMembers(KUBE_PING.java:206) at org.jgroups.protocols.Discovery.invokeFindMembers(Discovery.java:216) at org.jgroups.protocols.Discovery.findMembers(Discovery.java:241) at org.jgroups.protocols.Discovery.down(Discovery.java:384) at org.jgroups.protocols.MERGE3$InfoSender.run(MERGE3.java:413) at org.jgroups.util.TimeScheduler3$Task.run(TimeScheduler3.java:328) at org.jgroups.util.TimeScheduler3$RecurringTask.run(TimeScheduler3.java:362) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.jboss.as.clustering.jgroups.ClassLoaderThreadFactory.lambda$newThread$0(ClassLoaderThreadFactory.java:52) at java.lang.Thread.run(Thread.java:748) https://github.com/jgroups-extras/jgroups-kubernetes/issues/39 https://github.com/jgroups-extras/jgroups-kubernetes/pull/88 Will be resolved with a next jgroups-kubernetes upgrade. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9609) Avoid unnecessary marshalling of AddressableNode wherever possible

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-9609?page=com.atlassian.jira.plugin... ] Paul Ferraro resolved WFLY-9609. -------------------------------- Resolution: Duplicate Issue Duplicate of WFLY-9521 > Avoid unnecessary marshalling of AddressableNode wherever possible > ------------------------------------------------------------------ > > Key: WFLY-9609 > URL: https://issues.redhat.com/browse/WFLY-9609 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Serialization of an AddressableNode requires an additional 7 or 19 bytes (depending on whether the corresponding bind address is IPv4 or IPv6) as well as the logical name as a UTF-8 string; all on top of the 16 bytes required to serialize the JGroups/Infinispan address. > In most cases, this is completely unnecessary, as the Node can always be recreated from the address via a NodeFactory<Address>. > Known offenders are: > * org.wildfly.clustering.server.registry.CacheRegistry which stores the Node as a cache key. > * org.wildfly.clustering.server.provider.CacheServiceProviderRegistry which stores a Set<Node> as a cache value. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1053) Automate Weight < 100 https://github.com/kiali/kiali/pull/2108

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1053?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1053. ----------------------------------- Resolution: Done https://github.com/Kiali-QE/kiali-qe-python/pull/242 > Automate Weight < 100 https://github.com/kiali/kiali/pull/2108 > -------------------------------------------------------------- > > Key: SWSQE-1053 > URL: https://issues.redhat.com/browse/SWSQE-1053 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2437) Log local_addr and name in JChannel

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/JGRP-2437?page=com.atlassian.jira.plugin... ] Diego Lovison updated JGRP-2437: -------------------------------- Description: As a developer I would like to know what is the local_address ( the value printed in the log ) and what will be the address sent over the network ( the value that will be captured by TShark ) When running a benchmark in the perf lab we start running tshark after the initial load. In this case, in the tshark dump we won't have the PING request. was: As a developer I would like to know what is the local_address ( the value printed in the log ) and what will be the address sent over the network ( the value that will be captured by TShark ) > Log local_addr and name in JChannel > ----------------------------------- > > Key: JGRP-2437 > URL: https://issues.redhat.com/browse/JGRP-2437 > Project: JGroups > Issue Type: Enhancement > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Minor > > As a developer I would like to know what is the local_address ( the value printed in the log ) and what will be the address sent over the network ( the value that will be captured by TShark ) > When running a benchmark in the perf lab we start running tshark after the initial load. In this case, in the tshark dump we won't have the PING request. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1923) NPE in AuthenticationConfiguration.toString()

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1923: ------------------------------------- Summary: NPE in AuthenticationConfiguration.toString() Key: ELY-1923 URL: https://issues.redhat.com/browse/ELY-1923 Project: WildFly Elytron Issue Type: Bug Components: Authentication Client Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.11.1.CR1 {noformat} LogManager error of type FORMAT_FAILURE: Formatting error java.lang.NullPointerException at org.wildfly.security.auth.client.AuthenticationConfiguration.toString(AuthenticationConfiguration.java:1654) {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1923) NPE in AuthenticationConfiguration.toString()

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1923?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated ELY-1923: ---------------------------------- Priority: Critical (was: Major) > NPE in AuthenticationConfiguration.toString() > --------------------------------------------- > > Key: ELY-1923 > URL: https://issues.redhat.com/browse/ELY-1923 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.11.1.CR1 > > > {noformat} > LogManager error of type FORMAT_FAILURE: Formatting error > java.lang.NullPointerException > at org.wildfly.security.auth.client.AuthenticationConfiguration.toString(AuthenticationConfiguration.java:1654) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2437) Log local_addr and name in JChannel

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/JGRP-2437?page=com.atlassian.jira.plugin... ] Diego Lovison reassigned JGRP-2437: ----------------------------------- Assignee: Diego Lovison (was: Bela Ban) > Log local_addr and name in JChannel > ----------------------------------- > > Key: JGRP-2437 > URL: https://issues.redhat.com/browse/JGRP-2437 > Project: JGroups > Issue Type: Enhancement > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Minor > > As a developer I would like to know what is the local_address ( the value printed in the log ) and what will be the address sent over the network ( the value that will be captured by TShark ) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2437) Log local_addr and name in JChannel

by Diego Lovison (Jira)

Diego Lovison created JGRP-2437: ----------------------------------- Summary: Log local_addr and name in JChannel Key: JGRP-2437 URL: https://issues.redhat.com/browse/JGRP-2437 Project: JGroups Issue Type: Enhancement Reporter: Diego Lovison Assignee: Bela Ban As a developer I would like to know what is the local_address ( the value printed in the log ) and what will be the address sent over the network ( the value that will be captured by TShark ) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13005) Upgrade BouncyCastle to 1.64

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-13005: --------------------------------------- Summary: Upgrade BouncyCastle to 1.64 Key: WFLY-13005 URL: https://issues.redhat.com/browse/WFLY-13005 Project: WildFly Issue Type: Component Upgrade Components: REST, Security, Web Services Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 19.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4943) Guided Decision Table Validation and Verification feature is broken

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4943?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-4943. ------------------------------- Resolution: Cannot Reproduce > Guided Decision Table Validation and Verification feature is broken > ------------------------------------------------------------------- > > Key: DROOLS-4943 > URL: https://issues.redhat.com/browse/DROOLS-4943 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2020-01-16 16-01-08.png > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4943) Guided Decision Table Validation and Verification feature is broken

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4943?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4943: ------------------------------------- [~Rikkola] thank you, I can not reproduce the issue more. > Guided Decision Table Validation and Verification feature is broken > ------------------------------------------------------------------- > > Key: DROOLS-4943 > URL: https://issues.redhat.com/browse/DROOLS-4943 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2020-01-16 16-01-08.png > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1922) Upgrade BouncyCastle to 1.64

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1922: ------------------------------------- Summary: Upgrade BouncyCastle to 1.64 Key: ELY-1922 URL: https://issues.redhat.com/browse/ELY-1922 Project: WildFly Elytron Issue Type: Component Upgrade Components: Testsuite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.11.1.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4927) Memory leak in PrometheusKieServerExtension

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4927?page=com.atlassian.jira.plug... ] Mario Fusco reassigned DROOLS-4927: ----------------------------------- Assignee: Luca Molteni (was: Mario Fusco) > Memory leak in PrometheusKieServerExtension > ------------------------------------------- > > Key: DROOLS-4927 > URL: https://issues.redhat.com/browse/DROOLS-4927 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.31.0.Final > Reporter: Karel Suta > Assignee: Luca Molteni > Priority: Major > > Prometheus Kie server extensions contains support for custom metrics [1]. > These metrics are added when a new container is called [2]. > However when container is removed then these metrics stay active. Agenda event listener has container instance as a HashMap key. This container instance is quite big, causing memory leak. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4927) Memory leak in PrometheusKieServerExtension

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4927?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4927. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/droolsjbpm-integration/commit/453d9960d63be91... > Memory leak in PrometheusKieServerExtension > ------------------------------------------- > > Key: DROOLS-4927 > URL: https://issues.redhat.com/browse/DROOLS-4927 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.31.0.Final > Reporter: Karel Suta > Assignee: Luca Molteni > Priority: Major > > Prometheus Kie server extensions contains support for custom metrics [1]. > These metrics are added when a new container is called [2]. > However when container is removed then these metrics stay active. Agenda event listener has container instance as a HashMap key. This container instance is quite big, causing memory leak. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4962) [GSS](7.z) A Spreadsheet decision tables does not convert to a DRL file correctly when a Function is being used in the RuleTable constraints

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4962?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4962: --------------------------------- Tester: Jozef Marko Labels: drools-tools (was: ) > [GSS](7.z) A Spreadsheet decision tables does not convert to a DRL file correctly when a Function is being used in the RuleTable constraints > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4962 > URL: https://issues.redhat.com/browse/DROOLS-4962 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > 1. Create a "test_functions" project in the "MySpace" space. > 2. Create a "Person" Data Object > {code:java} > package com.myspace.test_functions; > /** > * This class was automatically generated by the data modeler tool. > */ > public class Person implements java.io.Serializable { > static final long serialVersionUID = 1L; > @org.kie.api.definition.type.Label("Gender") > private java.lang.String gender; > @org.kie.api.definition.type.Label("Is Married") > private java.lang.Boolean married; > @org.kie.api.definition.type.Label("Name") > private java.lang.String name; > @org.kie.api.definition.type.Label(value = "Message") > private java.lang.String message; > public Person() { > } > public void setHelloMsg(String arg) { > this.message = arg; > } > public java.lang.String getGender() { > return this.gender; > } > public void setGender(java.lang.String gender) { > this.gender = gender; > } > public java.lang.Boolean getMarried() { > return this.married; > } > public void setMarried(java.lang.Boolean married) { > this.married = married; > } > public java.lang.String getName() { > return this.name; > } > public void setName(java.lang.String name) { > this.name = name; > } > public java.lang.String getMessage() { > return this.message; > } > public void setMessage(java.lang.String message) { > this.message = message; > } > public Person(java.lang.String gender, java.lang.Boolean married, > java.lang.String name, java.lang.String message) { > this.gender = gender; > this.married = married; > this.name = name; > this.message = message; > } > } > {code} > 3. Import the "test_functions.xlsx" > 4. Convert the "test_functions.xlsx" > 5. Check the result files -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4962) [GSS](7.z) A Spreadsheet decision tables does not convert to a DRL file correctly when a Function is being used in the RuleTable constraints

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4962?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-4962: --------------------------------- Description: 1. Create a "test_functions" project in the "MySpace" space. 2. Create a "Person" Data Object {code:java} package com.myspace.test_functions; /** * This class was automatically generated by the data modeler tool. */ public class Person implements java.io.Serializable { static final long serialVersionUID = 1L; @org.kie.api.definition.type.Label("Gender") private java.lang.String gender; @org.kie.api.definition.type.Label("Is Married") private java.lang.Boolean married; @org.kie.api.definition.type.Label("Name") private java.lang.String name; @org.kie.api.definition.type.Label(value = "Message") private java.lang.String message; public Person() { } public void setHelloMsg(String arg) { this.message = arg; } public java.lang.String getGender() { return this.gender; } public void setGender(java.lang.String gender) { this.gender = gender; } public java.lang.Boolean getMarried() { return this.married; } public void setMarried(java.lang.Boolean married) { this.married = married; } public java.lang.String getName() { return this.name; } public void setName(java.lang.String name) { this.name = name; } public java.lang.String getMessage() { return this.message; } public void setMessage(java.lang.String message) { this.message = message; } public Person(java.lang.String gender, java.lang.Boolean married, java.lang.String name, java.lang.String message) { this.gender = gender; this.married = married; this.name = name; this.message = message; } } {code} 3. Import the "test_functions.xlsx" 4. Convert the "test_functions.xlsx" 5. Check the result files > [GSS](7.z) A Spreadsheet decision tables does not convert to a DRL file correctly when a Function is being used in the RuleTable constraints > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4962 > URL: https://issues.redhat.com/browse/DROOLS-4962 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > > 1. Create a "test_functions" project in the "MySpace" space. > 2. Create a "Person" Data Object > {code:java} > package com.myspace.test_functions; > /** > * This class was automatically generated by the data modeler tool. > */ > public class Person implements java.io.Serializable { > static final long serialVersionUID = 1L; > @org.kie.api.definition.type.Label("Gender") > private java.lang.String gender; > @org.kie.api.definition.type.Label("Is Married") > private java.lang.Boolean married; > @org.kie.api.definition.type.Label("Name") > private java.lang.String name; > @org.kie.api.definition.type.Label(value = "Message") > private java.lang.String message; > public Person() { > } > public void setHelloMsg(String arg) { > this.message = arg; > } > public java.lang.String getGender() { > return this.gender; > } > public void setGender(java.lang.String gender) { > this.gender = gender; > } > public java.lang.Boolean getMarried() { > return this.married; > } > public void setMarried(java.lang.Boolean married) { > this.married = married; > } > public java.lang.String getName() { > return this.name; > } > public void setName(java.lang.String name) { > this.name = name; > } > public java.lang.String getMessage() { > return this.message; > } > public void setMessage(java.lang.String message) { > this.message = message; > } > public Person(java.lang.String gender, java.lang.Boolean married, > java.lang.String name, java.lang.String message) { > this.gender = gender; > this.married = married; > this.name = name; > this.message = message; > } > } > {code} > 3. Import the "test_functions.xlsx" > 4. Convert the "test_functions.xlsx" > 5. Check the result files -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4962) [GSS](7.z) A Spreadsheet decision tables does not convert to a DRL file correctly when a Function is being used in the RuleTable constraints

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-4962: ------------------------------------ Summary: [GSS](7.z) A Spreadsheet decision tables does not convert to a DRL file correctly when a Function is being used in the RuleTable constraints Key: DROOLS-4962 URL: https://issues.redhat.com/browse/DROOLS-4962 Project: Drools Issue Type: Bug Components: XLS Decision Table Editor Reporter: Toni Rikkola Assignee: Toni Rikkola -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4961) User / Role Permissions on package level

by Nikos Tsekouras (Jira)

Nikos Tsekouras created DROOLS-4961: --------------------------------------- Summary: User / Role Permissions on package level Key: DROOLS-4961 URL: https://issues.redhat.com/browse/DROOLS-4961 Project: Drools Issue Type: Feature Request Affects Versions: 7.31.0.Final Reporter: Nikos Tsekouras Assignee: Mario Fusco It will be amazingly helpful to have the ability to minimize the access / permissions of a user / group on package level. Within a project you can define several packages - for different purposes - and you need each team to be able to work on / view a specific package. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4960) Reference a data object from one project to another one.

by Nikos Tsekouras (Jira)

Nikos Tsekouras created DROOLS-4960: --------------------------------------- Summary: Reference a data object from one project to another one. Key: DROOLS-4960 URL: https://issues.redhat.com/browse/DROOLS-4960 Project: Drools Issue Type: Feature Request Affects Versions: 7.31.0.Final Reporter: Nikos Tsekouras Assignee: Mario Fusco Currently, nothing can be referenced from one project to another one. Using a common area to create the Data Objects etc. and reference them on several projects will be very helpful. Java-wise is like we are creating two projects and we reference the first one in the second one, in order to use some classes in our code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4959) Package name does not changes on copying of an existing package

by Nikos Tsekouras (Jira)

Nikos Tsekouras created DROOLS-4959: --------------------------------------- Summary: Package name does not changes on copying of an existing package Key: DROOLS-4959 URL: https://issues.redhat.com/browse/DROOLS-4959 Project: Drools Issue Type: Bug Affects Versions: 7.31.0.Final Reporter: Nikos Tsekouras Assignee: Mario Fusco After copying a package to a new one, all copied resources will remain referencing the existing one. This becomes a bigger issue once you use guided rules, which their source cannot be edited. Due to that, duplication alerts will be raised. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4939) Add generics to declared types

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4939?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4939. --------------------------------- Resolution: Done Implemented by https://github.com/kiegroup/drools/commit/11d9533564b410d50fd22319715de5e... > Add generics to declared types > ------------------------------ > > Key: DROOLS-4939 > URL: https://issues.redhat.com/browse/DROOLS-4939 > Project: Drools > Issue Type: Feature Request > Reporter: Edoardo Vacchi > Assignee: Mario Fusco > Priority: Major > Labels: drools-core > > add support to declare generic types (e.g. List<Foo>) in declared types > e.g. > {code} > declare Baz > List<Foo> foos > end > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4808) Upgrade JGit to 5.6.0.201912101111-r

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFCORE-4808: ----------------------------------------- Summary: Upgrade JGit to 5.6.0.201912101111-r Key: WFCORE-4808 URL: https://issues.redhat.com/browse/WFCORE-4808 Project: WildFly Core Issue Type: Component Upgrade Components: Management Affects Versions: 11.0.0.Beta7 Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Updating JGit and all its dependencies -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2436) Diagnostics: enable TCP by default

by Bela Ban (Jira)

Bela Ban created JGRP-2436: ------------------------------ Summary: Diagnostics: enable TCP by default Key: JGRP-2436 URL: https://issues.redhat.com/browse/JGRP-2436 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0, 4.2.0 Set {{diag_enable_tcp}} to true by default; a lot of deployments happen in the cloud today, and if we don't enable this, {{probe -addr ADDR}} will only retturn a response from the local member. This will open a UDP *and* TCP diagnostics socket, but if {{enable_diagnostics}} is false, then no socket will be opened -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13004) Upgrade jgroups-kubernetes to 1.0.14.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13004?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13004: ---------------------------------- Priority: Optional (was: Major) > Upgrade jgroups-kubernetes to 1.0.14.Final > ------------------------------------------ > > Key: WFLY-13004 > URL: https://issues.redhat.com/browse/WFLY-13004 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > > No functional changes. > https://github.com/jgroups-extras/jgroups-kubernetes/compare/1.0.14.Final... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13004) Upgrade jgroups-kubernetes to 1.0.14.Final

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-13004: ------------------------------------- Summary: Upgrade jgroups-kubernetes to 1.0.14.Final Key: WFLY-13004 URL: https://issues.redhat.com/browse/WFLY-13004 Project: WildFly Issue Type: Component Upgrade Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar No functional changes. https://github.com/jgroups-extras/jgroups-kubernetes/compare/1.0.14.Final... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4807) Add option to route log messages based on the current thread's class loader

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4807?page=com.atlassian.jira.plug... ] James Perkins moved EAP7-1421 to WFCORE-4807: --------------------------------------------- Project: WildFly Core (was: JBoss EAP Planning for version 7 and above) Key: WFCORE-4807 (was: EAP7-1421) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Logging (was: Logging) EAP Testing By: (was: Engineering) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.4.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Add option to route log messages based on the current thread's class loader > --------------------------------------------------------------------------- > > Key: WFCORE-4807 > URL: https://issues.redhat.com/browse/WFCORE-4807 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Currently any modules that log generally log onto the system log context. In some cases, see WFCORE-3376, loggers in modules may be created on the wrong log context. This means logs may be routed to the wrong log context. > LOGMR-264 can introduce a way to route log messages based on the log context. This would allow messages from modules to be routed to deployment specific log contexts. It would also introduce a change in behavior which is the reason for an RFE. A new attribute should be introduce to disable the new routing and allow the old behavior. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13003) Support the SameSite cookie attribute

by Stuart Douglas (Jira)

Stuart Douglas created WFLY-13003: ------------------------------------- Summary: Support the SameSite cookie attribute Key: WFLY-13003 URL: https://issues.redhat.com/browse/WFLY-13003 Project: WildFly Issue Type: Feature Request Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Flavia Rainone Chrome 80 is going to significantly change how cookies are handled, as per this notice at [1], with a bit of an explanation of what the same site attribute means at [2]. At the moment the Servlet specification has no way of setting this particular attribute, and it is not possible to configure it via container specific configuration in WildFly at present (it can only be done by writing some Undertow specific code). I propose we add a same-site-cookie-attribute predicated handler to undertow, which takes an optional cookie name regex, and the value for the attribute to set. This would allow users to configure the SameSite attribute based on cookie name, and also potentially based on any other attributes including user agent, as it sounds like some browsers may have bugs that means this might need to be set on a per user agent basis. [1] https://www.chromestatus.com/feature/5088147346030592 [2] https://web.dev/samesite-cookies-explained/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4806) Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Ginal

by James Perkins (Jira)

James Perkins created WFCORE-4806: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Ginal Key: WFCORE-4806 URL: https://issues.redhat.com/browse/WFCORE-4806 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade the {{org.jboss.logmanager:jboss-logmanager}} to 2.2.0.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4806) Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Final

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4806?page=com.atlassian.jira.plug... ] James Perkins updated WFCORE-4806: ---------------------------------- Summary: Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Final (was: Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Ginal) > Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Final > --------------------------------------------------------- > > Key: WFCORE-4806 > URL: https://issues.redhat.com/browse/WFCORE-4806 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Upgrade the {{org.jboss.logmanager:jboss-logmanager}} to 2.2.0.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4778) [DMN Designer] Multiple DRDs Support (Backlog)

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4778?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-4778: ---------------------------------------- [~uxdlc] [~porcelli] [~tirelli] FYI I raised https://issues.redhat.com/browse/KOGITO-937 to handle positioning of the Decision Navigator in different _channels_. > [DMN Designer] Multiple DRDs Support (Backlog) > ---------------------------------------------- > > Key: DROOLS-4778 > URL: https://issues.redhat.com/browse/DROOLS-4778 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs related to the Multiple DRDs Support feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12883) Add user API to handle merging @Stateful EJB instances on partition merge

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12883?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12883: -------------------------------- Description: In the event of a detected network partition, the distributed bean manager's Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a SFSB in all partitions # Allow reads from a SFSB in all partitions, but only allow writes to a SFSB if the partition contains all data owners. # Allow both reads and writes to/from a SFSB in all partitions For customers who opt for #3 (i.e. maximum availability), in the event that a SFSB is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. Something like: {code:java} public interface BeanInstanceMergePolicy<T> { T merge(T primaryPartitionBean, Iterable<T> minorityPartitionBeans); } {code} was: In the event of a detected network partition, the distributed bean manager's Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a SFSB in all partitions # Allow reads from a SFSB in all partitions, but only allow writes to a SFSB if the partition contains all data owners. # Allow both reads and writes to/from a SFSB in all partitions For customers who opt for #3 (i.e. maximum availability), in the event that a SFSB is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} > Add user API to handle merging @Stateful EJB instances on partition merge > ------------------------------------------------------------------------- > > Key: WFLY-12883 > URL: https://issues.redhat.com/browse/WFLY-12883 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > In the event of a detected network partition, the distributed bean manager's Infinispan cache behaves in one of 3 ways: > # Disallow both reads and writes from/to a SFSB in all partitions > # Allow reads from a SFSB in all partitions, but only allow writes to a SFSB if the partition contains all data owners. > # Allow both reads and writes to/from a SFSB in all partitions > For customers who opt for #3 (i.e. maximum availability), in the event that a SFSB is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. > Something like: > {code:java} > public interface BeanInstanceMergePolicy<T> { > T merge(T primaryPartitionBean, Iterable<T> minorityPartitionBeans); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13002) Add user API to handle merging @Stateful EJB instances on partition merge

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13002: ----------------------------------- Summary: Add user API to handle merging @Stateful EJB instances on partition merge Key: WFLY-13002 URL: https://issues.redhat.com/browse/WFLY-13002 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 18.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro In the event of a detected network partition, the distributed bean manager's Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a SFSB in all partitions # Allow reads from a SFSB in all partitions, but only allow writes to a SFSB if the partition contains all data owners. # Allow both reads and writes to/from a SFSB in all partitions For customers who opt for #3 (i.e. maximum availability), in the event that a SFSB is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. Something like: {code:java} public interface BeanInstanceMergePolicy<T> { T merge(T primaryPartitionBean, Iterable<T> minorityPartitionBeans); } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12883) Add user API to handle merging @Stateful EJB instances on partition merge

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12883?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12883: -------------------------------- Description: In the event of a detected network partition, the distributed bean manager's Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a SFSB in all partitions # Allow reads from a SFSB in all partitions, but only allow writes to a SFSB if the partition contains all data owners. # Allow both reads and writes to/from a SFSB in all partitions For customers who opt for #3 (i.e. maximum availability), in the event that a SFSB is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} > Add user API to handle merging @Stateful EJB instances on partition merge > ------------------------------------------------------------------------- > > Key: WFLY-12883 > URL: https://issues.redhat.com/browse/WFLY-12883 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > In the event of a detected network partition, the distributed bean manager's Infinispan cache behaves in one of 3 ways: > # Disallow both reads and writes from/to a SFSB in all partitions > # Allow reads from a SFSB in all partitions, but only allow writes to a SFSB if the partition contains all data owners. > # Allow both reads and writes to/from a SFSB in all partitions > For customers who opt for #3 (i.e. maximum availability), in the event that a SFSB is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. > Something like: > {code:java} > public interface SessionAttributeMergePolicy { > Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12882) Add user API to handle merging HttpSession attributes/metadata on partition merge

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12882?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12882: -------------------------------- Description: In the event of a detected network partition, the distributed web session manager's Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a web session in all partitions # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. # Allow both reads and writes to/from a web session in all partitions For customers who opt for #3 (i.e. maximum availability), in the event that a web session is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} was: In the event of a detected network partition, the distributed web session manager's Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a web session in all partitions # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. # Allow both reads and writes to/from a web session in all partitions For customers who opt for #3 (i.e. maximum availability), in the event that a web session is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} > Add user API to handle merging HttpSession attributes/metadata on partition merge > --------------------------------------------------------------------------------- > > Key: WFLY-12882 > URL: https://issues.redhat.com/browse/WFLY-12882 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > In the event of a detected network partition, the distributed web session manager's Infinispan cache behaves in one of 3 ways: > # Disallow both reads and writes from/to a web session in all partitions > # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. > # Allow both reads and writes to/from a web session in all partitions > For customers who opt for #3 (i.e. maximum availability), in the event that a web session is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. > Something like: > {code:java} > public interface SessionAttributeMergePolicy { > Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13001) Add user API to handle merging HttpSession attributes/metadata on partition merge

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13001: ----------------------------------- Summary: Add user API to handle merging HttpSession attributes/metadata on partition merge Key: WFLY-13001 URL: https://issues.redhat.com/browse/WFLY-13001 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 18.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro In the event of a detected network partition, the distributed web session manager's Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a web session in all partitions # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. # Allow both reads and writes to/from a web session in all partitions For customers who opt for #3 (i.e. maximum availability), in the event that a web session is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12882) Add user API to handle merging HttpSession attributes/metadata on partition merge

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12882?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12882: -------------------------------- Description: In the event of a detected network partition, the distributed web session manager's Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a web session in all partitions # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. # Allow both reads and writes to/from a web session in all partitions For customers who opt for #3 (i.e. maximum availability), in the event that a web session is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} was: In the event of a detected network partition, the distributed web session manager's Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a web session in all partitions # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. # Allow both reads and writes to/from a web session in all partitions For customers who opt for #3 (i.e. maximum availability), they need be able to provide a mechanism to resolve conflicts following partition merge, in the event that a web session is updated in both partitions. When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} > Add user API to handle merging HttpSession attributes/metadata on partition merge > --------------------------------------------------------------------------------- > > Key: WFLY-12882 > URL: https://issues.redhat.com/browse/WFLY-12882 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > In the event of a detected network partition, the distributed web session manager's Infinispan cache behaves in one of 3 ways: > # Disallow both reads and writes from/to a web session in all partitions > # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. > # Allow both reads and writes to/from a web session in all partitions > For customers who opt for #3 (i.e. maximum availability), in the event that a web session is updated in both partitions, they need be able to provide a mechanism to resolve conflicts when the partitions eventually merge. > When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. > Something like: > {code:java} > public interface SessionAttributeMergePolicy { > Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12882) Add user API to handle merging HttpSession attributes/metadata on partition merge

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12882?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12882: -------------------------------- Description: In the event of a detected network partition, the distributed web session manager's Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a web session in all partitions # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. # Allow both reads and writes to/from a web session in all partitions For customers who opt for #3 (i.e. maximum availability), they need be able to provide a mechanism to resolve conflicts following partition merge, in the event that a web session is updated in both partitions. When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} was: In the event of a detected network partition, an Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a web session in all partitions # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. # Allow both reads and writes to/from a web session in all partitions For customers who opt for #3 (i.e. maximum availability), they need be able to provide a mechanism to resolve conflicts following partition merge, in the event that a web session is updated in both partitions. When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} > Add user API to handle merging HttpSession attributes/metadata on partition merge > --------------------------------------------------------------------------------- > > Key: WFLY-12882 > URL: https://issues.redhat.com/browse/WFLY-12882 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > In the event of a detected network partition, the distributed web session manager's Infinispan cache behaves in one of 3 ways: > # Disallow both reads and writes from/to a web session in all partitions > # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. > # Allow both reads and writes to/from a web session in all partitions > For customers who opt for #3 (i.e. maximum availability), they need be able to provide a mechanism to resolve conflicts following partition merge, in the event that a web session is updated in both partitions. > When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. > Something like: > {code:java} > public interface SessionAttributeMergePolicy { > Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12882) Add user API to handle merging HttpSession attributes/metadata on partition merge

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12882?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12882: -------------------------------- Description: In the event of a detected network partition, an Infinispan cache behaves in one of 3 ways: # Disallow both reads and writes from/to a web session in all partitions # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. # Allow both reads and writes to/from a web session in all partitions For customers who opt for #3 (i.e. maximum availability), they need be able to provide a mechanism to resolve conflicts following partition merge, in the event that a web session is updated in both partitions. When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} was: When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} > Add user API to handle merging HttpSession attributes/metadata on partition merge > --------------------------------------------------------------------------------- > > Key: WFLY-12882 > URL: https://issues.redhat.com/browse/WFLY-12882 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > In the event of a detected network partition, an Infinispan cache behaves in one of 3 ways: > # Disallow both reads and writes from/to a web session in all partitions > # Allow reads from a web session in all partitions, but only allow writes to a web session if the partition contains all data owners. > # Allow both reads and writes to/from a web session in all partitions > For customers who opt for #3 (i.e. maximum availability), they need be able to provide a mechanism to resolve conflicts following partition merge, in the event that a web session is updated in both partitions. > When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. > Something like: > {code:java} > public interface SessionAttributeMergePolicy { > Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4943) Guided Decision Table Validation and Verification feature is broken

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4943?page=com.atlassian.jira.plug... ] Toni Rikkola commented on DROOLS-4943: -------------------------------------- [~jomarko] I tested locally and master has the change, but do you want to give it a try before we close the ticket? Sorry I forgot to originally link this. > Guided Decision Table Validation and Verification feature is broken > ------------------------------------------------------------------- > > Key: DROOLS-4943 > URL: https://issues.redhat.com/browse/DROOLS-4943 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2020-01-16 16-01-08.png > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12882) Add user API to handle merging HttpSession attributes/metadata on partition merge

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12882?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12882: -------------------------------- Description: When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. Something like: {code:java} public interface SessionAttributeMergePolicy { Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); } {code} was: When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. Something like: {code:java} public interface SessionAttributeMergePolicy<T>() { T prefer(String attributeName, T primaryPartitionAttribute, List<T> minorityPartitionAttributes); } {code} > Add user API to handle merging HttpSession attributes/metadata on partition merge > --------------------------------------------------------------------------------- > > Key: WFLY-12882 > URL: https://issues.redhat.com/browse/WFLY-12882 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > When partition handling of a web session cache is enabled, users need a mechanism to control how to resolve conflicting session attributes on merge. > Something like: > {code:java} > public interface SessionAttributeMergePolicy { > Object merge(String attributeName, Object primaryPartitionAttributeValue, Iterable<Object> minorityPartitionAttributeValues); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4778) [DMN Designer] Multiple DRDs Support (Backlog)

by Alexandre Bakos (Jira)

[ https://issues.redhat.com/browse/DROOLS-4778?page=com.atlassian.jira.plug... ] Alexandre Bakos commented on DROOLS-4778: ----------------------------------------- Agree with [~manstis] As correctly pointed - the need to the de-clutter left side is a channel-specific need of VSCode today, we might see this restriction in new channels as well. > [DMN Designer] Multiple DRDs Support (Backlog) > ---------------------------------------------- > > Key: DROOLS-4778 > URL: https://issues.redhat.com/browse/DROOLS-4778 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs related to the Multiple DRDs Support feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFWIP-287: -------------------------------------- I don't think we need a separate RFE as this is expected to be resolved in the next release with SR FT reimplementation – there will be RFE for the spec/impl upgrade. > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4801) RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4801?page=com.atlassian.jira.plug... ] Brian Stansberry commented on WFCORE-4801: ------------------------------------------ Hi [~nvinothkumar]. If something is fixed in the current release it is not likely to get attention, as we generally don't produce maintenance releases from old branches. > RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used > ------------------------------------------------------------------------------------- > > Key: WFCORE-4801 > URL: https://issues.redhat.com/browse/WFCORE-4801 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Management > Affects Versions: 9.0.1.Final > Reporter: Vinoth Kumar Natarajan > Priority: Major > > Heap dump analysis of services deployed in Wildfly standalone deployment show a large number of stale objects of class org.jboss.remoting3.ConnectionImpl and org.jboss.remoting3.remote.RemoteConnectionHandler. These objects are not getting garbage collected and eventually cause JVM to go out of memory. > Analysis of the heap dump indicate that, > * All org.jboss.remoting3.ConnectionImpl objects lingering around are CLOSED as the state and associated with JBOSS management endpoint. > * All org.jboss.remoting3.remote.RemoteConnectionHandler objects lingering around are associated with Remote Endpoint Name "cli-client". which is the endpoint name used by org.jboss.as.cli. > Above observations seem to indicate that JBOSS CLI commands that are executed periodically in this deployment, to monitor status of deployments, is causing these stale objects. > To confirm this observation, we have executed jboss-cli.sh a couple of times on our deployment and could see that each execution of this script is leaving nehind one instance of each of these classes. > *Wildfly version details:* > bash-4.4# ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] connect > [standalone@localhost:9990 /] version > JBoss Admin Command-line Interface > JBOSS_HOME: /ericsson/3pp/wildfly > Release: 9.0.1.Final > Product: WildFly Full 17.0.0.Final > JAVA_HOME: /usr/ > java.version: 1.8.0_222 > java.vm.vendor: IcedTea > java.vm.version: 25.222-b10 > os.name: Linux > os.version: 4.12.14-197.15-default -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4947) Test Scenario: update kie-server swagger API doc with new services

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4947?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4947: ---------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Test Scenario: update kie-server swagger API doc with new services > ------------------------------------------------------------------ > > Key: DROOLS-4947 > URL: https://issues.redhat.com/browse/DROOLS-4947 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4575?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4575: ---------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Test Scenario: unsaved changes warning appears even if file has not been changed > -------------------------------------------------------------------------------- > > Key: DROOLS-4575 > URL: https://issues.redhat.com/browse/DROOLS-4575 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus, drools-tools > > If user opens a scesim file and then close it, no confirmation message should be opened > h2. Manual Acceptance Test > - Opening and closing without changes > - Open, change data in cell, close > - Open, add column, remove column, change column binding, close > - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4418) Add enum support to Rule test scenarios

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4418?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4418: ---------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Add enum support to Rule test scenarios > --------------------------------------- > > Key: DROOLS-4418 > URL: https://issues.redhat.com/browse/DROOLS-4418 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation, drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4575?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4575: ---------------------------------- Story Points: 5 > Test Scenario: unsaved changes warning appears even if file has not been changed > -------------------------------------------------------------------------------- > > Key: DROOLS-4575 > URL: https://issues.redhat.com/browse/DROOLS-4575 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus, drools-tools > > If user opens a scesim file and then close it, no confirmation message should be opened > h2. Manual Acceptance Test > - Opening and closing without changes > - Open, change data in cell, close > - Open, add column, remove column, change column binding, close > - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4418) Add enum support to Rule test scenarios

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4418?page=com.atlassian.jira.plug... ] Daniele Zonca updated DROOLS-4418: ---------------------------------- Story Points: 3 > Add enum support to Rule test scenarios > --------------------------------------- > > Key: DROOLS-4418 > URL: https://issues.redhat.com/browse/DROOLS-4418 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation, drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4698) Adding "expression" type handling for Collection type propereties

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4698?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4698: ------------------------------- Story Points: 1 (was: 7) > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4698 > URL: https://issues.redhat.com/browse/DROOLS-4698 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screenshot from 2020-01-08 14-14-05.png, Screenshot from 2020-01-08 14-20-30.png, Screenshot from 2020-01-08 14-36-33.png, Screenshot from 2020-01-08 14-36-52.png, test urgent.scesim, urgent.dmn > > > Support is about both drools/java collections and dmn collections. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4927) Memory leak in PrometheusKieServerExtension

by Edson Tirelli (Jira)

[ https://issues.redhat.com/browse/DROOLS-4927?page=com.atlassian.jira.plug... ] Edson Tirelli commented on DROOLS-4927: --------------------------------------- [~manaRH] : [~mfusco] and [~tkobayashi] will look into it. > Memory leak in PrometheusKieServerExtension > ------------------------------------------- > > Key: DROOLS-4927 > URL: https://issues.redhat.com/browse/DROOLS-4927 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.31.0.Final > Reporter: Karel Suta > Assignee: Mario Fusco > Priority: Major > > Prometheus Kie server extensions contains support for custom metrics [1]. > These metrics are added when a new container is called [2]. > However when container is removed then these metrics stay active. Agenda event listener has container instance as a HashMap key. This container instance is quite big, causing memory leak. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4949) Blue rectangle above test scenario collection editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4949?page=com.atlassian.jira.plug... ] Jozef Marko resolved DROOLS-4949. --------------------------------- Resolution: Done > Blue rectangle above test scenario collection editor > ---------------------------------------------------- > > Key: DROOLS-4949 > URL: https://issues.redhat.com/browse/DROOLS-4949 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2020-01-17 12-30-13.png, urgent.dmn > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There appears misleading blue rectangle above the collection editor popup once when the editor has focus / is clicked. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13000) Put an end to problems with Jackson caused by jaxrs subsystem

by Dominik Derwiński (Jira)

[ https://issues.redhat.com/browse/WFLY-13000?page=com.atlassian.jira.plugi... ] Dominik Derwiński commented on WFLY-13000: ------------------------------------------ Perhaps jaxrs / resteasy module should pull by default only smallest possible subset of libraries, with all others being optional for the user to add. It's not easy to exclude implicit dependencies (and one is generally not aware of the problem until the app is deployed). > Put an end to problems with Jackson caused by jaxrs subsystem > ------------------------------------------------------------- > > Key: WFLY-13000 > URL: https://issues.redhat.com/browse/WFLY-13000 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 18.0.1.Final > Reporter: Dominik Derwiński > Assignee: Alessio Soldano > Priority: Major > > There is a serious problem with using bundled (inside ear) Jackson JSON library in version different than the one included inside WildFly. There are dozens of threads of people trying to solve this issue by manually upgrading modules in WildFly, excluding certain Jackson modules pulled by jaxrs and including them again in custom modules without exporting classes, to (finally) excluding the whole jaxrs subsystem, and using different implementation of JAXRS. Without doing so one can end with the following: > {noformat} > java.lang.NoSuchMethodError: 'com.fasterxml.jackson.core.TSFBuilder com.fasterxml.jackson.core.JsonFactory.builder()' > {noformat} > or > {noformat} > java.lang.IllegalAccessError: class com.fasterxml.jackson.core.JsonFactoryBuilder tried to access private field com.fasterxml.jackson.core.JsonFactory.DEFAULT_ROOT_VALUE_SEPARATOR (com.fasterxml.jackson.core.JsonFactoryBuilder is in unnamed module of loader 'deployment.xyz-ear-1.ear' @b6d0dc5; com.fasterxml.jackson.core.JsonFactory is in unnamed module of loader 'com.fasterxml.jackson.core.jackson-core(a)2.9.10' @68fc71cf) > {noformat} > Could this be fixed somehow by not exporting Jackson classes from jaxrs/resteasy/jackson2-provider modules? Why do they even get priority before classes from ear classloader? > Found these on the net while trying to solve my issue: > http://alloutfornoloss.com/exclude-jackson-module-wildfly/ > https://stackoverflow.com/questions/37616096/wildfly-10-how-to-use-a-newe... > https://stackoverflow.com/questions/38173460/dependency-conflict-loading-... > https://stackoverflow.com/questions/47838240/jboss-resteasy-custom-jackso... > https://stackoverflow.com/questions/56780117/unknown-conflict-causing-jav... > https://stackoverflow.com/questions/20683843/jackson-annotations-ignored-... > https://dzone.com/articles/jboss-modules-suck-it%E2%80%99s > https://forum.camunda.org/t/camunda-json-marshalling-and-jsonignore/271/18 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4927) Memory leak in PrometheusKieServerExtension

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4927?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-4927: -------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Memory leak in PrometheusKieServerExtension > ------------------------------------------- > > Key: DROOLS-4927 > URL: https://issues.redhat.com/browse/DROOLS-4927 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.31.0.Final > Reporter: Karel Suta > Assignee: Mario Fusco > Priority: Major > > Prometheus Kie server extensions contains support for custom metrics [1]. > These metrics are added when a new container is called [2]. > However when container is removed then these metrics stay active. Agenda event listener has container instance as a HashMap key. This container instance is quite big, causing memory leak. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4927) Memory leak in PrometheusKieServerExtension

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4927?page=com.atlassian.jira.plug... ] Mario Fusco reassigned DROOLS-4927: ----------------------------------- Assignee: Mario Fusco (was: Luca Molteni) > Memory leak in PrometheusKieServerExtension > ------------------------------------------- > > Key: DROOLS-4927 > URL: https://issues.redhat.com/browse/DROOLS-4927 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.31.0.Final > Reporter: Karel Suta > Assignee: Mario Fusco > Priority: Major > > Prometheus Kie server extensions contains support for custom metrics [1]. > These metrics are added when a new container is called [2]. > However when container is removed then these metrics stay active. Agenda event listener has container instance as a HashMap key. This container instance is quite big, causing memory leak. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-4746: -------------------------------------- Sprint: (was: 2020 Week 04-06 (from Jan 20)) > UX for DMN "quick test" tool > ---------------------------- > > Key: DROOLS-4746 > URL: https://issues.redhat.com/browse/DROOLS-4746 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test. > When the user run the test he can get back the results of the DMN execution. > Moreover, it would be handy to add those input/output to an existing (or new) test scenario. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4949) Blue rectangle above test scenario collection editor

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4949?page=com.atlassian.jira.plug... ] Yeser Amer reopened DROOLS-4949: -------------------------------- > Blue rectangle above test scenario collection editor > ---------------------------------------------------- > > Key: DROOLS-4949 > URL: https://issues.redhat.com/browse/DROOLS-4949 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2020-01-17 12-30-13.png, urgent.dmn > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There appears misleading blue rectangle above the collection editor popup once when the editor has focus / is clicked. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4699) Supporting long value input

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4699?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4699: ------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 44-46 (from Okt 28)) > Supporting long value input > --------------------------- > > Key: DROOLS-4699 > URL: https://issues.redhat.com/browse/DROOLS-4699 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > > Description here: > https://issues.jboss.org/browse/DROOLS-4574?focusedCommentId=13794570&pag... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12952) MP Health returns UP when checks are expected but not installed yet.

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFLY-12952?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFLY-12952: ------------------------------- Priority: Critical (was: Blocker) > MP Health returns UP when checks are expected but not installed yet. > -------------------------------------------------------------------- > > Key: WFLY-12952 > URL: https://issues.redhat.com/browse/WFLY-12952 > Project: WildFly > Issue Type: Bug > Components: MP Health > Affects Versions: 18.0.0.Final > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Critical > > MicroProfile Health 2.0 specification [link|https://github.com/eclipse/microprofile-health/blob/2.0/spec/src/mai...] says: > * A producer MUST support custom, application level health check procedures > * A producer SHOULD support reasonable out-of-the-box procedures > * A producer with no health check procedures expected or installed MUST return positive overall status (i.e. HTTP 200) > * A producer with health check procedures expected but not yet installed MUST return negative overall status (i.e. HTTP 503) > When I deploy and application with a readiness probe before WildFly is started, from my and namely OpenShift POV the health check procedure is expected from the very beginning. > _Let me note that on OpenShift starting the served should mean starting the service._ > Hence I expect negative overall status till the probe is ready and is able to provide response. > However WildFly with default setting responses with status UP: > {code:bash} > while true; do echo $(date +"%T.%3N") ; curl localhost:9990/health/ready; echo ""; done > 17:17:56.438 curl: (7) Failed to connect to localhost port 9990: Connection refused > 17:17:56.452 curl: (7) Failed to connect to localhost port 9990: Connection refused > 17:17:56.466 {"status":"UP","checks":[]} > ... > 17:18:01.121 {"status":"UP","checks":[]} > 17:18:01.133 {"status":"DOWN","checks":[{"name":"delayed-readiness","status":"DOWN"}]} > {code} > This violates (4) bullet in the specification. > WildFly provides option to set global Status when probes are not defined ([documentation|https://doc-stage.usersys.redhat.com/documentation/en-us/re...]) > Which would mean the scenario would behave according to the specification. Yet the default state violates it. > If the default value were _DOWN_ we would run into an issue if WildFly without deployment were used (for example as backup for AMQ). The status would be just DOWN: > {noformat} > 17:22:41.719 > {"status":"DOWN","checks":[]} > {noformat} > And that would violate (3) in the specification. > TCK tests do not cover the scenario well. > Is there a way to return _DOWN_ until WildFly scan a deployment and if no health check is found (thus not expected) then start to return _UP_ ? The scan should happen during MP Health initialization. > If there is no deployment, the _UP_ it is. > Setting the priority to blocker since WildFly 19 shall be EAP 7.3.0.CD19 which is supposed to run on OpenShift. With this behavior health check is not very useful because: > * OpenShift starts the service wait some time and start asking for health status > * WildFly responses _UP_ yet application helathcheck is not installed yet > * With health status _UP_ OpenShift consider a pod ready > * In this point application is installed, health status is _DOWN_ (a DB is down) however OpenShift flow is somewhere else -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4778) [DMN Designer] Multiple DRDs Support (Backlog)

by Edson Tirelli (Jira)

[ https://issues.redhat.com/browse/DROOLS-4778?page=com.atlassian.jira.plug... ] Edson Tirelli commented on DROOLS-4778: --------------------------------------- [~manstis] I agree. > [DMN Designer] Multiple DRDs Support (Backlog) > ---------------------------------------------- > > Key: DROOLS-4778 > URL: https://issues.redhat.com/browse/DROOLS-4778 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs related to the Multiple DRDs Support feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1051) Prepare document for OCP layered testing

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1051?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1051. ---------------------------------- Resolution: Done > Prepare document for OCP layered testing > ---------------------------------------- > > Key: SWSQE-1051 > URL: https://issues.redhat.com/browse/SWSQE-1051 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > We need to describe how and what will be tested during different ocp milestones. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1049) install-ocp to support OCP 4.4

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1049?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1049. ---------------------------------- Resolution: Done Jobs are updated and the latest rhcos image is uploaded to istio-dev. IPI is not working yet because of one issue on ocp side. Will file a ticket for that. > install-ocp to support OCP 4.4 > ------------------------------ > > Key: SWSQE-1049 > URL: https://issues.redhat.com/browse/SWSQE-1049 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > OCP 4.4 clusters will need to be created. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4801) RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used

by Vinoth Kumar Natarajan (Jira)

[ https://issues.redhat.com/browse/WFCORE-4801?page=com.atlassian.jira.plug... ] Vinoth Kumar Natarajan commented on WFCORE-4801: ------------------------------------------------ Further investigation shows that issue is found in *Release: 9.0.1.Final* but not seen with *Release: 10.0.3.Final*. But we are not in a position to upgrade Wildfly. Please take a look into this issue. *Test results from Release: 9.0.1.Final :* {code} $ winpty docker exec -it f370379d0044 bash [jboss@f370379d0044 ~]$ find ./ -name 'wildfly-cli*jar' ./wildfly/modules/system/layers/base/org/wildfly/client/config/main/wildfly-client-config-1.0.1.Final.jar ./wildfly/modules/system/layers/base/org/jboss/as/cli/main/wildfly-cli-9.0.1.Final.jar [jboss@f370379d0044 ~]$ jmap -histo:live 90 | grep ConnectionImpl 1859: 1 80 org.jboss.remoting3.ConnectionImpl 5691: 1 16 org.jboss.remoting3.ConnectionImpl$$Lambda$663/0x000000084098fc40 [jboss@f370379d0044 ~]$ /opt/jboss/wildfly/bin/jboss-cli.sh You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. [disconnected /] connect [standalone@localhost:9990 /] version JBoss Admin Command-line Interface JBOSS_HOME: /opt/jboss/wildfly Release: 9.0.1.Final Product: WildFly Full 17.0.0.Final JAVA_HOME: /usr/lib/jvm/java java.version: 11.0.1 java.vm.vendor: Oracle Corporation java.vm.version: 11.0.1+13-LTS os.name: Linux os.version: 4.9.184-linuxkit [standalone@localhost:9990 /] exit [jboss@f370379d0044 ~]$ jmap -histo:live 90 | grep ConnectionImpl 1152: 2 160 org.jboss.remoting3.ConnectionImpl 5681: 1 16 org.jboss.remoting3.ConnectionImpl$$Lambda$663/0x000000084098fc40 [jboss@f370379d0044 ~]$ [jboss@f370379d0044 ~]$ jmap -histo:live 90 | grep RemoteConnectionHandler 1033: 2 192 org.jboss.remoting3.remote.RemoteConnectionHandler [jboss@f370379d0044 ~]$ jmap -histo:live 90 | grep RemoteConnectionHandler 1033: 2 192 org.jboss.remoting3.remote.RemoteConnectionHandler [jboss@f370379d0044 ~]$ {code} *Test results from Release: 10.0.3.Final :* {code} $ winpty docker exec -it b3c484904468 bash [jboss@b3c484904468 ~]$ [jboss@b3c484904468 ~]$ [jboss@b3c484904468 ~]$ find ./ -name 'wildfly-cli*jar' ./wildfly/modules/system/layers/base/org/wildfly/client/config/main/wildfly-client-config-1.0.1.Final.jar ./wildfly/modules/system/layers/base/org/jboss/as/cli/main/wildfly-cli-10.0.3.Final.jar ./wildfly/modules/system/layers/base/org/jboss/as/cli/main/wildfly-cli-11.0.0.Beta8-SNAPSHOT.jar [jboss@b3c484904468 ~]$ [jboss@b3c484904468 ~]$ jmap -histo:live 91 | grep RemoteConnectionHandler [jboss@b3c484904468 ~]$ [jboss@b3c484904468 ~]$ /opt/jboss/wildfly/bin/jboss-cli.sh You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. [disconnected /] connect [standalone@localhost:9990 /] version JBoss Admin Command-line Interface JBOSS_HOME: /opt/jboss/wildfly Release: 10.0.3.Final Product: WildFly Full 18.0.1.Final JAVA_HOME: /usr/lib/jvm/java java.version: 11.0.5 java.vm.vendor: Oracle Corporation java.vm.version: 11.0.5+10-LTS os.name: Linux os.version: 4.9.184-linuxkit [standalone@localhost:9990 /] exit [jboss@b3c484904468 ~]$ [jboss@b3c484904468 ~]$ jmap -histo:live 91 | grep RemoteConnectionHandler 1515: 1 96 org.jboss.remoting3.remote.RemoteConnectionHandler [jboss@b3c484904468 ~]$ jmap -histo:live 91 | grep RemoteConnectionHandler [jboss@b3c484904468 ~]$ [jboss@b3c484904468 ~]$ jmap -histo 91 | grep RemoteConnectionHandler [jboss@b3c484904468 ~]$ exit {code} Thanks, Vinoth. > RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used > ------------------------------------------------------------------------------------- > > Key: WFCORE-4801 > URL: https://issues.redhat.com/browse/WFCORE-4801 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Management > Affects Versions: 9.0.1.Final > Reporter: Vinoth Kumar Natarajan > Priority: Major > > Heap dump analysis of services deployed in Wildfly standalone deployment show a large number of stale objects of class org.jboss.remoting3.ConnectionImpl and org.jboss.remoting3.remote.RemoteConnectionHandler. These objects are not getting garbage collected and eventually cause JVM to go out of memory. > Analysis of the heap dump indicate that, > * All org.jboss.remoting3.ConnectionImpl objects lingering around are CLOSED as the state and associated with JBOSS management endpoint. > * All org.jboss.remoting3.remote.RemoteConnectionHandler objects lingering around are associated with Remote Endpoint Name "cli-client". which is the endpoint name used by org.jboss.as.cli. > Above observations seem to indicate that JBOSS CLI commands that are executed periodically in this deployment, to monitor status of deployments, is causing these stale objects. > To confirm this observation, we have executed jboss-cli.sh a couple of times on our deployment and could see that each execution of this script is leaving nehind one instance of each of these classes. > *Wildfly version details:* > bash-4.4# ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] connect > [standalone@localhost:9990 /] version > JBoss Admin Command-line Interface > JBOSS_HOME: /ericsson/3pp/wildfly > Release: 9.0.1.Final > Product: WildFly Full 17.0.0.Final > JAVA_HOME: /usr/ > java.version: 1.8.0_222 > java.vm.vendor: IcedTea > java.vm.version: 25.222-b10 > os.name: Linux > os.version: 4.12.14-197.15-default -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4912) [DMN Designer] Data Types - Inline add action button

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4912?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4912: ------------------------------------ Story Points: 2 > [DMN Designer] Data Types - Inline add action button > ---------------------------------------------------- > > Key: DROOLS-4912 > URL: https://issues.redhat.com/browse/DROOLS-4912 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Minor > Labels: UX, drools-tools > Attachments: Screen Shot 2020-01-08 at 7.06.20 PM.png > > > Change the behavior and tooltip for the inline add icon-button (+). Currently it converts the type to Structure before adding a row below. Instead, we want it to add another row without converting the type. > Acceptance criteria: > * Tooltip: "Add row below (Ctrl + B)" > Behavior - Clicking the (+) inline add button: > * from a type defined as Structure, will add a field row below. > * from a Field row (within a Structure), will add another field row below. > * from a Simple type, such as "Person(string)", will add another row of the same type below. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4910) [DMN Designer] Data Types - Redesign placeholder screen

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4910?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4910: ------------------------------------ Sprint: 2020 Week 04-06 (from Jan 20) > [DMN Designer] Data Types - Redesign placeholder screen > ------------------------------------------------------- > > Key: DROOLS-4910 > URL: https://issues.redhat.com/browse/DROOLS-4910 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: prototype.png > > > Redesign placeholder screen: > !prototype.png|width=800! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4912) [DMN Designer] Data Types - Inline add action button

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4912?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4912: ------------------------------------ Summary: [DMN Designer] Data Types - Inline add action button (was: DMN Data type editor - inline add action button. ) > [DMN Designer] Data Types - Inline add action button > ---------------------------------------------------- > > Key: DROOLS-4912 > URL: https://issues.redhat.com/browse/DROOLS-4912 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Minor > Labels: UX, drools-tools > Attachments: Screen Shot 2020-01-08 at 7.06.20 PM.png > > > Change the behavior and tooltip for the inline add icon-button (+). Currently it converts the type to Structure before adding a row below. Instead, we want it to add another row without converting the type. > Acceptance criteria: > * Tooltip: "Add row below (Ctrl + B)" > Behavior - Clicking the (+) inline add button: > * from a type defined as Structure, will add a field row below. > * from a Field row (within a Structure), will add another field row below. > * from a Simple type, such as "Person(string)", will add another row of the same type below. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4912) DMN Data type editor - inline add action button.

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4912?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4912: ------------------------------------ Sprint: 2020 Week 04-06 (from Jan 20) > DMN Data type editor - inline add action button. > ------------------------------------------------- > > Key: DROOLS-4912 > URL: https://issues.redhat.com/browse/DROOLS-4912 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Minor > Labels: UX, drools-tools > Attachments: Screen Shot 2020-01-08 at 7.06.20 PM.png > > > Change the behavior and tooltip for the inline add icon-button (+). Currently it converts the type to Structure before adding a row below. Instead, we want it to add another row without converting the type. > Acceptance criteria: > * Tooltip: "Add row below (Ctrl + B)" > Behavior - Clicking the (+) inline add button: > * from a type defined as Structure, will add a field row below. > * from a Field row (within a Structure), will add another field row below. > * from a Simple type, such as "Person(string)", will add another row of the same type below. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4913) DMN Data type editor - inline add action button.

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4913?page=com.atlassian.jira.plug... ] Guilherme Gomes closed DROOLS-4913. ----------------------------------- Resolution: Duplicate Issue It's the same issue reported by DROOLS-4912 > DMN Data type editor - inline add action button. > ------------------------------------------------- > > Key: DROOLS-4913 > URL: https://issues.redhat.com/browse/DROOLS-4913 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Minor > Labels: UX, drools-tools > > Change the behavior and tooltip for the inline add icon-button (+). Currently it converts the type to Structure before adding a row below. Instead, we want it to add another row without converting the type. > Acceptance criteria: > *Tooltip: "Add row below (Ctrl + B)" > Behavior - Clicking the (+) inline add button: > * from a type defined as Structure, will add a field row below. > * from a Field row (within a Structure), will add a field row below. > * from a Simple type, such as "Person(string)", will add another row of the same type below. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12917) Optimize builders for JMS Client BOM

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-12917?page=com.atlassian.jira.plugi... ] Eduardo Martins updated WFLY-12917: ----------------------------------- Git Pull Request: https://github.com/wildfly/boms/pull/79 (was: https://github.com/wildfly/boms/pull/77) > Optimize builders for JMS Client BOM > ------------------------------------ > > Key: WFLY-12917 > URL: https://issues.redhat.com/browse/WFLY-12917 > Project: WildFly > Issue Type: Enhancement > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: 19.0.0.Beta1 > > > The builders for JMS Client BOM should be optimized, changing inherit exclusion mode to UNMANAGED, and removing artifacts which are just transitive dependencies of top level BOM artifacts. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4801) RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used

by Vinoth Kumar Natarajan (Jira)

[ https://issues.redhat.com/browse/WFCORE-4801?page=com.atlassian.jira.plug... ] Vinoth Kumar Natarajan updated WFCORE-4801: ------------------------------------------- Component/s: Management > RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used > ------------------------------------------------------------------------------------- > > Key: WFCORE-4801 > URL: https://issues.redhat.com/browse/WFCORE-4801 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Management > Affects Versions: 9.0.1.Final > Reporter: Vinoth Kumar Natarajan > Priority: Major > > Heap dump analysis of services deployed in Wildfly standalone deployment show a large number of stale objects of class org.jboss.remoting3.ConnectionImpl and org.jboss.remoting3.remote.RemoteConnectionHandler. These objects are not getting garbage collected and eventually cause JVM to go out of memory. > Analysis of the heap dump indicate that, > * All org.jboss.remoting3.ConnectionImpl objects lingering around are CLOSED as the state and associated with JBOSS management endpoint. > * All org.jboss.remoting3.remote.RemoteConnectionHandler objects lingering around are associated with Remote Endpoint Name "cli-client". which is the endpoint name used by org.jboss.as.cli. > Above observations seem to indicate that JBOSS CLI commands that are executed periodically in this deployment, to monitor status of deployments, is causing these stale objects. > To confirm this observation, we have executed jboss-cli.sh a couple of times on our deployment and could see that each execution of this script is leaving nehind one instance of each of these classes. > *Wildfly version details:* > bash-4.4# ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] connect > [standalone@localhost:9990 /] version > JBoss Admin Command-line Interface > JBOSS_HOME: /ericsson/3pp/wildfly > Release: 9.0.1.Final > Product: WildFly Full 17.0.0.Final > JAVA_HOME: /usr/ > java.version: 1.8.0_222 > java.vm.vendor: IcedTea > java.vm.version: 25.222-b10 > os.name: Linux > os.version: 4.12.14-197.15-default -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4801) RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used

by Vinoth Kumar Natarajan (Jira)

[ https://issues.redhat.com/browse/WFCORE-4801?page=com.atlassian.jira.plug... ] Vinoth Kumar Natarajan updated WFCORE-4801: ------------------------------------------- Component/s: CLI > RemoteConnectionHandler and ConnectionImpl objects leak when org.jboss.as.cli is used > ------------------------------------------------------------------------------------- > > Key: WFCORE-4801 > URL: https://issues.redhat.com/browse/WFCORE-4801 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Vinoth Kumar Natarajan > Priority: Major > > Heap dump analysis of services deployed in Wildfly standalone deployment show a large number of stale objects of class org.jboss.remoting3.ConnectionImpl and org.jboss.remoting3.remote.RemoteConnectionHandler. These objects are not getting garbage collected and eventually cause JVM to go out of memory. > Analysis of the heap dump indicate that, > * All org.jboss.remoting3.ConnectionImpl objects lingering around are CLOSED as the state and associated with JBOSS management endpoint. > * All org.jboss.remoting3.remote.RemoteConnectionHandler objects lingering around are associated with Remote Endpoint Name "cli-client". which is the endpoint name used by org.jboss.as.cli. > Above observations seem to indicate that JBOSS CLI commands that are executed periodically in this deployment, to monitor status of deployments, is causing these stale objects. > To confirm this observation, we have executed jboss-cli.sh a couple of times on our deployment and could see that each execution of this script is leaving nehind one instance of each of these classes. > *Wildfly version details:* > bash-4.4# ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] connect > [standalone@localhost:9990 /] version > JBoss Admin Command-line Interface > JBOSS_HOME: /ericsson/3pp/wildfly > Release: 9.0.1.Final > Product: WildFly Full 17.0.0.Final > JAVA_HOME: /usr/ > java.version: 1.8.0_222 > java.vm.vendor: IcedTea > java.vm.version: 25.222-b10 > os.name: Linux > os.version: 4.12.14-197.15-default -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 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 January 2020