July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2782) [Guided Rule] Can't be opened if constraint to bound field present

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2782: ----------------------------------- Summary: [Guided Rule] Can't be opened if constraint to bound field present Key: DROOLS-2782 URL: https://issues.jboss.org/browse/DROOLS-2782 Project: Drools Issue Type: Bug Components: Guided Rule Editor Affects Versions: 7.9.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2018-07-24 14-32-00.png {code:mvel} package com.myspace.repr; import java.lang.Number; rule "rule" dialect "mvel" when DataObject( $stringField : sFieldOne == "something" ) DataObjectTwo( sFieldTwo == $stringField ) then end {code} Assume the rdrl file above where both *sFieldOne* and *sFieldTwo* are both of *String* type. Then if you try open this rdrl file in workbench the unexpected error dialog appears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3973) Upgrade CLI to use aesh-extensions 1.6

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3973?page=com.atlassian.jira.plugi... ] Kabir Khan resolved WFCORE-3973. -------------------------------- Fix Version/s: 6.0.0.Alpha5 Resolution: Done > Upgrade CLI to use aesh-extensions 1.6 > -------------------------------------- > > Key: WFCORE-3973 > URL: https://issues.jboss.org/browse/WFCORE-3973 > Project: WildFly Core > Issue Type: Component Upgrade > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Fix For: 6.0.0.Alpha5 > > > An invalid dependency on javafx has been found in aesh-extension. It has been removed in aesh-extensions 1.6 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2781) [Guided Rule] Can't be opened if constraint to bound field present

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2781: ----------------------------------- Summary: [Guided Rule] Can't be opened if constraint to bound field present Key: DROOLS-2781 URL: https://issues.jboss.org/browse/DROOLS-2781 Project: Drools Issue Type: Bug Components: Guided Rule Editor Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2018-07-24 14-32-00.png {code:mvel} package com.myspace.repr; import java.lang.Number; rule "rule" dialect "mvel" when DataObject( $stringField : sFieldOne == "something" ) DataObjectTwo( sFieldTwo == $stringField ) then end {code} Assume the rdrl file above where both *sFieldOne* and *sFieldTwo* are both of *String* type. Then if you try open this rdrl file in workbench the unexpected error dialog appears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2781) [Guided Rule] Can't be opened if constraint to bound field present

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2781?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2781: -------------------------------- Affects Version/s: 7.9.0.Final > [Guided Rule] Can't be opened if constraint to bound field present > ------------------------------------------------------------------ > > Key: DROOLS-2781 > URL: https://issues.jboss.org/browse/DROOLS-2781 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Attachments: Screenshot from 2018-07-24 14-32-00.png > > > {code:mvel} > package com.myspace.repr; > import java.lang.Number; > rule "rule" > dialect "mvel" > when > DataObject( $stringField : sFieldOne == "something" ) > DataObjectTwo( sFieldTwo == $stringField ) > then > end > {code} > Assume the rdrl file above where both *sFieldOne* and *sFieldTwo* are both of *String* type. Then if you try open this rdrl file in workbench the unexpected error dialog appears. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2774) Select a data type from the DMN canvas

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2774?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2774: -------------------------------- Description: *Background* Persona: Business analyst or Rules practitioner Use Cases: As a user I want a means to... * Add/Create a data type * Edit an Existing data type * Select a desired data type ... from the canvas view so I can associate it with a DMN node. Functional considerations?: Any functional requirements or constraints, such as: Does the solution need to leverage any specific existing components (workbench or PF,)... was: *Background* Persona: here Use Cases: As a user I want a means to... * Add/Create a data type * Edit an Existing data type * Select a desired data type ... from the canvas view so I can associate it with a DMN node. Functional considerations?: Any functional requirements or constraints, such as: Does the solution need to leverage any specific existing components (workbench or PF,)... > Select a data type from the DMN canvas > --------------------------------------- > > Key: DROOLS-2774 > URL: https://issues.jboss.org/browse/DROOLS-2774 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: As a user I want a means to... > * Add/Create a data type > * Edit an Existing data type > * Select a desired data type ... from the canvas view so I can associate it with a DMN node. > Functional considerations?: Any functional requirements or constraints, such as: > Does the solution need to leverage any specific existing components (workbench or PF,)... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2780) Create a right panel for expression builder/cheatsheet

by Daniele Zonca (JIRA)

Daniele Zonca created DROOLS-2780: ------------------------------------- Summary: Create a right panel for expression builder/cheatsheet Key: DROOLS-2780 URL: https://issues.jboss.org/browse/DROOLS-2780 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca Create a panel on the right with a tab selector and two tabs: expression builder and cheatsheet. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2779) Create a jUnit result panel to show test results

by Daniele Zonca (JIRA)

Daniele Zonca created DROOLS-2779: ------------------------------------- Summary: Create a jUnit result panel to show test results Key: DROOLS-2779 URL: https://issues.jboss.org/browse/DROOLS-2779 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca Reuse test scenario result component to show jUnit results. Convert result layout to new HTML/CSS -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10383) Multiple test failures due to Weld class init problem

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/WFLY-10383?page=com.atlassian.jira.plugin... ] Matej Novotny commented on WFLY-10383: -------------------------------------- Updating CDI API to 2.0.SP1 will resolve this. I will do that along with Weld component upgrade once we release 3.0.5 (later this week/next week). > Multiple test failures due to Weld class init problem > ----------------------------------------------------- > > Key: WFLY-10383 > URL: https://issues.jboss.org/browse/WFLY-10383 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: David Lloyd > Assignee: Martin Kouba > Priority: Critical > Labels: security-manager > > This is the upstream tracking issue for WELD-2496. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10731) core-threads of ManagedScheduledExecutorService limits number of maximal threads

by gunter zeilinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-10731?page=com.atlassian.jira.plugin... ] gunter zeilinger updated WFLY-10731: ------------------------------------ Description: After changing the default configuration: {noformat} <managed-scheduled-executor-services> - <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" keepalive-time="3000"/> + <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" long-running-tasks="true" core-threads="2" keepalive-time="3000"/> </managed-scheduled-executor-services> {noformat} only 2 (= value of core-threads) threads are used by the Scheduled Executer Service: {code:bash} $ grep ManagedScheduledExecutorService $WILDFLY/standalone/log/server.log | tail 2018-07-24 12:03:22,901 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,911 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,923 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,963 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,967 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,981 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,996 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:23,016 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:23,035 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:23,039 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. {code} I have not yet tested if the issue also effects Wildfly 13.0.0.Final ( cannot use Wildfly 13.0.0.Final because of WFLY-10531 ) was: After changing the default configuration: {noformat} <managed-scheduled-executor-services> - <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" keepalive-time="3000"/> + <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" long-running-tasks="true" core-threads="2" keepalive-time="3000"/> </managed-scheduled-executor-services> {noformat} only 2 (= value of core-threads) threads are used by the Scheduled Executer Service: {code:bash} $ grep $WILDFLY/standalone/log/server.log | tail 2018-07-24 12:03:22,901 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,911 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,923 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,963 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,967 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,981 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,996 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:23,016 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:23,035 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:23,039 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. {code} I have not yet tested if the issue also effects Wildfly 13.0.0.Final ( cannot use Wildfly 13.0.0.Final because of WFLY-10531 ) > core-threads of ManagedScheduledExecutorService limits number of maximal threads > -------------------------------------------------------------------------------- > > Key: WFLY-10731 > URL: https://issues.jboss.org/browse/WFLY-10731 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 12.0.0.Final > Reporter: gunter zeilinger > > After changing the default configuration: > {noformat} > <managed-scheduled-executor-services> > - <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" keepalive-time="3000"/> > + <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" long-running-tasks="true" core-threads="2" keepalive-time="3000"/> > </managed-scheduled-executor-services> > {noformat} > only 2 (= value of core-threads) threads are used by the Scheduled Executer Service: > {code:bash} > $ grep ManagedScheduledExecutorService $WILDFLY/standalone/log/server.log | tail > 2018-07-24 12:03:22,901 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. > 2018-07-24 12:03:22,911 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. > 2018-07-24 12:03:22,923 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. > 2018-07-24 12:03:22,963 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. > 2018-07-24 12:03:22,967 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. > 2018-07-24 12:03:22,981 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. > 2018-07-24 12:03:22,996 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. > 2018-07-24 12:03:23,016 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. > 2018-07-24 12:03:23,035 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. > 2018-07-24 12:03:23,039 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. > {code} > I have not yet tested if the issue also effects Wildfly 13.0.0.Final ( cannot use Wildfly 13.0.0.Final because of WFLY-10531 ) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10731) core-threads of ManagedScheduledExecutorService limits number of maximal threads

by gunter zeilinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-10731?page=com.atlassian.jira.plugin... ] gunter zeilinger updated WFLY-10731: ------------------------------------ Description: After changing the default configuration: {noformat} <managed-scheduled-executor-services> - <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" keepalive-time="3000"/> + <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" long-running-tasks="true" core-threads="2" keepalive-time="3000"/> </managed-scheduled-executor-services> {noformat} only 2 (= value of core-threads) threads are used by the Scheduled Executer Service: {code:bash} $ grep $WILDFLY/standalone/log/server.log | tail 2018-07-24 12:03:22,901 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,911 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,923 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,963 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,967 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,981 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,996 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:23,016 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:23,035 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:23,039 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. {code} I have not yet tested if the issue also effects Wildfly 13.0.0.Final ( cannot use Wildfly 13.0.0.Final because of WFLY-10531 ) was: After changing the default configuration: {noformat} <managed-scheduled-executor-services> - <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" keepalive-time="3000"/> + <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" long-running-tasks="true" core-threads="2" keepalive-time="3000"/> </managed-scheduled-executor-services> {noformat} only 2 (= value of core-threads) threads are used by the Scheduled Executer Service: {code:bash} $ grep $WILDFLY/standalone/log/server.log | tail 2018-07-24 12:03:22,901 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,911 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,923 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,963 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,967 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:22,981 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:22,996 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:23,016 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. 2018-07-24 12:03:23,035 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. 2018-07-24 12:03:23,039 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. {code} > core-threads of ManagedScheduledExecutorService limits number of maximal threads > -------------------------------------------------------------------------------- > > Key: WFLY-10731 > URL: https://issues.jboss.org/browse/WFLY-10731 > Project: WildFly > Issue Type: Bug > Components: EE > Affects Versions: 12.0.0.Final > Reporter: gunter zeilinger > > After changing the default configuration: > {noformat} > <managed-scheduled-executor-services> > - <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" hung-task-threshold="60000" keepalive-time="3000"/> > + <managed-scheduled-executor-service name="default" jndi-name="java:jboss/ee/concurrency/scheduler/default" context-service="default" long-running-tasks="true" core-threads="2" keepalive-time="3000"/> > </managed-scheduled-executor-services> > {noformat} > only 2 (= value of core-threads) threads are used by the Scheduled Executer Service: > {code:bash} > $ grep $WILDFLY/standalone/log/server.log | tail > 2018-07-24 12:03:22,901 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. > 2018-07-24 12:03:22,911 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. > 2018-07-24 12:03:22,923 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. > 2018-07-24 12:03:22,963 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. > 2018-07-24 12:03:22,967 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. > 2018-07-24 12:03:22,981 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. > 2018-07-24 12:03:22,996 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. > 2018-07-24 12:03:23,016 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. > 2018-07-24 12:03:23,035 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-2) .. > 2018-07-24 12:03:23,039 INFO [org.dcm4che3.net.Association] (EE-ManagedScheduledExecutorService-default-Thread-1) .. > {code} > I have not yet tested if the issue also effects Wildfly 13.0.0.Final ( cannot use Wildfly 13.0.0.Final because of WFLY-10531 ) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2018