[JBoss JIRA] (DROOLS-2398) [DMN Designer] Change of function discards width of parent column
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2398?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2398:
--------------------------------
Description:
Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
h2. Acceptance criteria
Recursively (to achieve 3 depth levels):
# Declare context entry
# Add 6 rows
# Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
# Configure the 6th row as Context and repeat with first step
At each depth level, check other columns width is updated when:
# Literal is
## updated, resized, cleared, removed
# Decision table is
## updated, resized, cleared, removed
# Function is
## updated, resized, cleared, removed
# Invocation is
## updated, resized, cleared, removed
# Relation is
## updated, resized, cleared, removed
# Context is
## updated, resized, cleared, removed
Column widths preserved after reopen (x)
was:
Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
h2. Acceptance criteria
Recursively (to achieve 3 depth levels):
# Declare context entry
# Add 6 rows
# Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
# Configure the 6th row as Context and repeat with first step
At each depth level, check other columns width is updated when:
# Literal is
## updated, resized, cleared, removed
# Decision table is
## updated, resized, cleared, removed
# Function is
## updated, resized, cleared, removed
# Invocation is
## updated, resized, cleared, removed
# Relation is
## updated, resized, cleared, removed
# Context is
## updated, resized, cleared, removed
> [DMN Designer] Change of function discards width of parent column
> -----------------------------------------------------------------
>
> Key: DROOLS-2398
> URL: https://issues.jboss.org/browse/DROOLS-2398
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Fix For: 7.7.0.Final
>
> Attachments: Screenshot from 2018-03-21 09-34-25.png
>
>
> Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
> h2. Acceptance criteria
> Recursively (to achieve 3 depth levels):
> # Declare context entry
> # Add 6 rows
> # Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
> # Configure the 6th row as Context and repeat with first step
> At each depth level, check other columns width is updated when:
> # Literal is
> ## updated, resized, cleared, removed
> # Decision table is
> ## updated, resized, cleared, removed
> # Function is
> ## updated, resized, cleared, removed
> # Invocation is
> ## updated, resized, cleared, removed
> # Relation is
> ## updated, resized, cleared, removed
> # Context is
> ## updated, resized, cleared, removed
> Column widths preserved after reopen (x)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2398) [DMN Designer] Change of function discards width of parent column
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2398?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2398:
--------------------------------
Description:
Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
h2. Acceptance criteria
Recursively (to achieve 3 depth levels):
# Declare context entry
# Add 6 rows
# Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
# Configure the 6th row as Context and repeat with first step
At each depth level, check other columns width is updated when:
# Literal is
## updated, resized, cleared, removed
# Decision table is
## updated, resized, cleared, removed
# Function is
## updated, resized, cleared, removed
# Invocation is
## updated, resized, cleared, removed
# Relation is
## updated, resized, cleared, removed
# Context is
## updated, resized, cleared, removed
Column widths preserved after reopen (x)
was:
Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
h2. Acceptance criteria
Recursively (to achieve 3 depth levels):
# Declare context entry
# Add 6 rows
# Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
# Configure the 6th row as Context and repeat with first step
At each depth level, check other columns width is updated when:
# Literal is
## updated, resized, cleared, removed
# Decision table is
## updated, resized, cleared, removed
# Function is
## updated, resized, cleared, removed
# Invocation is
## updated, resized, cleared, removed
# Relation is
## updated, resized, cleared, removed
# Context is
## updated, resized, cleared, removed
Column widths preserved after reopen (x)
> [DMN Designer] Change of function discards width of parent column
> -----------------------------------------------------------------
>
> Key: DROOLS-2398
> URL: https://issues.jboss.org/browse/DROOLS-2398
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Fix For: 7.7.0.Final
>
> Attachments: Screenshot from 2018-03-21 09-34-25.png
>
>
> Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
> h2. Acceptance criteria
> Recursively (to achieve 3 depth levels):
> # Declare context entry
> # Add 6 rows
> # Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
> # Configure the 6th row as Context and repeat with first step
> At each depth level, check other columns width is updated when:
> # Literal is
> ## updated, resized, cleared, removed
> # Decision table is
> ## updated, resized, cleared, removed
> # Function is
> ## updated, resized, cleared, removed
> # Invocation is
> ## updated, resized, cleared, removed
> # Relation is
> ## updated, resized, cleared, removed
> # Context is
> ## updated, resized, cleared, removed
> Column widths preserved after reopen (x)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2398) [DMN Designer] Change of function discards width of parent column
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2398?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2398:
--------------------------------
Attachment: Screenshot from 2018-03-21 09-34-25.png
> [DMN Designer] Change of function discards width of parent column
> -----------------------------------------------------------------
>
> Key: DROOLS-2398
> URL: https://issues.jboss.org/browse/DROOLS-2398
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Fix For: 7.7.0.Final
>
> Attachments: Screenshot from 2018-03-21 09-34-25.png
>
>
> Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
> h2. Acceptance criteria
> Recursively (to achieve 3 depth levels):
> # Declare context entry
> # Add 6 rows
> # Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
> # Configure the 6th row as Context and repeat with first step
> At each depth level, check other columns width is updated when:
> # Literal is
> ## updated, resized, cleared, removed
> # Decision table is
> ## updated, resized, cleared, removed
> # Function is
> ## updated, resized, cleared, removed
> # Invocation is
> ## updated, resized, cleared, removed
> # Relation is
> ## updated, resized, cleared, removed
> # Context is
> ## updated, resized, cleared, removed
> Column widths preserved after reopen (x)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10057) EJB subsystem configure max threads and core threads independently
by Richard Janík (JIRA)
Richard Janík created WFLY-10057:
------------------------------------
Summary: EJB subsystem configure max threads and core threads independently
Key: WFLY-10057
URL: https://issues.jboss.org/browse/WFLY-10057
Project: WildFly
Issue Type: Sub-task
Components: EJB
Affects Versions: 12.0.0.Final
Reporter: Richard Janík
Assignee: David Lloyd
EJB3 subsystem currently only allows setting the {{max-threads}}, not {{core-threads}}.
{noformat}
[standalone@localhost:9990 /] /subsystem=ejb3/thread-pool=default:write-attribute(name=
keepalive-time max-threads thread-factory
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2406) Remove unused ComparePair test class
by Tibor Zimányi (JIRA)
Tibor Zimányi created DROOLS-2406:
-------------------------------------
Summary: Remove unused ComparePair test class
Key: DROOLS-2406
URL: https://issues.jboss.org/browse/DROOLS-2406
Project: Drools
Issue Type: Task
Components: core engine
Affects Versions: 7.6.0.Final
Reporter: Tibor Zimányi
Assignee: Tibor Zimányi
Priority: Minor
I found out that after removal of usage from jBPM, test class ComparePair is now unused, so we can get rid of it. It's functionality can be replaced with AssertJ asserts if needed in the future similarly as here [1].
[1] https://github.com/kiegroup/jbpm/pull/1159
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2398) [DMN Designer] Change of function discards width of parent column
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2398?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2398:
--------------------------------
Description:
Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
h2. Acceptance criteria
Recursively (to achieve 3 depth levels):
# Declare context entry
# Add 6 rows
# Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
# Configure the 6th row as Context and repeat with first step
At each depth level, check other columns width is updated when:
# Literal is
## updated, resized, cleared, removed
# Decision table is
## updated, resized, cleared, removed
# Function is
## updated, resized, cleared, removed
# Invocation is
## updated, resized, cleared, removed
# Relation is
## updated, resized, cleared, removed
# Context is
## updated, resized, cleared, removed
was:Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
> [DMN Designer] Change of function discards width of parent column
> -----------------------------------------------------------------
>
> Key: DROOLS-2398
> URL: https://issues.jboss.org/browse/DROOLS-2398
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.7.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Minor
> Fix For: 7.7.0.Final
>
>
> Issue found during review of DROOLS-2368 but not sure if related, most probably not. Change of function definition discards width of parent column.
> h2. Acceptance criteria
> Recursively (to achieve 3 depth levels):
> # Declare context entry
> # Add 6 rows
> # Configure first 5 rows as: Literal, Decision Table, Function, Invocation, Relation
> # Configure the 6th row as Context and repeat with first step
> At each depth level, check other columns width is updated when:
> # Literal is
> ## updated, resized, cleared, removed
> # Decision table is
> ## updated, resized, cleared, removed
> # Function is
> ## updated, resized, cleared, removed
> # Invocation is
> ## updated, resized, cleared, removed
> # Relation is
> ## updated, resized, cleared, removed
> # Context is
> ## updated, resized, cleared, removed
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10031) Scripts throws "illegal reflective access" warning on JDK9
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFLY-10031?page=com.atlassian.jira.plugin... ]
Marek Kopecký commented on WFLY-10031:
--------------------------------------
"illegal reflective access" issue is still valid, I see xnio warnings now:
{noformat}
[mkopecky@dhcp-10-40-4-239 bin]$ ./jboss-cli.sh -c
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.xnio.nio.NioXnio$2 (jar:file:/home/mkopecky/playground/wf/wfly.18/wfly.18/modules/system/layers/base/org/jboss/xnio/nio/main/xnio-nio-3.6.2.Final.jar!/) to constructor sun.nio.ch.EPollSelectorProvider()
WARNING: Please consider reporting this to the maintainers of org.xnio.nio.NioXnio$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused
[mkopecky@dhcp-10-40-4-239 bin]$
{noformat}
> Scripts throws "illegal reflective access" warning on JDK9
> ----------------------------------------------------------
>
> Key: WFLY-10031
> URL: https://issues.jboss.org/browse/WFLY-10031
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Security
> Reporter: Marek Kopecký
> Assignee: James Perkins
> Priority: Blocker
>
> *Description of the issue:*
> Scripts throws "illegal reflective access" warning on JDK9/10/11.
> *How reproducible:*
> Always with JDK9, 10 and 11
> *Steps to Reproduce:*
> * ./jboss-cli.sh "echo test"
> * ./add-user.sh -u test4 -p Test123* -s
> * ./appclient.sh -v
> * ./wsconsume.sh
> * ./wsprovide.sh
> * ./domain.sh
> * ./standalone.sh
> *Actual results:*
> {noformat}
> [hudson@rhel7-large-9887 bin]$ java --version
> java 9.0.4
> Java(TM) SE Runtime Environment (build 9.0.4+11)
> Java HotSpot(TM) 64-Bit Server VM (build 9.0.4+11, mixed mode)
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./jboss-cli.sh "echo test"
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> test
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./add-user.sh -u test4 -p Test123* -s
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [hudson@rhel7-large-9887 bin]$ cat ../standalone/configuration/mgmt-users.properties | tail -n 1
> test4=a95aa9d159b7afe0cc9d3795061551ad
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> {noformat}
> [hudson@rhel7-large-9887 bin]$ ./appclient.sh -v
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.logmanager.LogManager$2 (jar:file:/home/hudson/hudson_workspace/workspace/early-testing-scripts-unix/9774dccf/wildfly/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.9.Final.jar!/) to constructor java.util.logging.Level$KnownLevel(java.util.logging.Level)
> WARNING: Please consider reporting this to the maintainers of org.jboss.logmanager.LogManager$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 06:11:52,205 INFO [org.jboss.modules] (main) JBoss Modules version 1.7.0.Final
> WildFly Full 13.0.0.Alpha1-SNAPSHOT (WildFly Core 4.0.0.Final)
> [hudson@rhel7-large-9887 bin]$
> {noformat}
> *Expected results:*
> No warnings
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-10055) [Artemis 2.x Upgrade] Auto-create-queue creates runtime queue without jms.queue prefix
by Martin Styk (JIRA)
[ https://issues.jboss.org/browse/WFLY-10055?page=com.atlassian.jira.plugin... ]
Martin Styk updated WFLY-10055:
-------------------------------
Steps to Reproduce:
{noformat}
git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
groovy -DEAP_ZIP_URL=<CURRENT_DIST_URL> PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
cd ../jboss-hornetq-testsuite/
mvn clean test -Dtest=AutoCreateQueueTestCase#testAutoDeleteQueueDisabled -Deap7.org.jboss.qa.hornetq.apps.clients.version=<CLIENT_VERSION> | tee log
{noformat}
Test fails at the end on attempt to get count of messages from auto created queue {{testQueue}}. It looks for {{jms.queue.testQueue}} runtime queue, however it doesn't exist.
> [Artemis 2.x Upgrade] Auto-create-queue creates runtime queue without jms.queue prefix
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-10055
> URL: https://issues.jboss.org/browse/WFLY-10055
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Martin Styk
> Assignee: Jeff Mesnil
>
> {{Auto-create-jms-queue}} feature of EAP 7.1 creates runtime queues with name pattern {{"jms.queue.<QUEUE_NAME>"}}.
> With Artemis 2.5, {{auto-create-queue}} is a successor of deprecated {{auto-create-jms-queue}} feature. {{Auto-create-queue}} creates queues with name pattern {{"<QUEUE_NAME>"}}.
> {code}
> session.createQueue("testQueue")
> --> "jms.queue.testQueue" (EAP 7.1 + Artemis 1.5, auto-create-jms-queue=true)
> --> "testQueue" (Artemis 2.5, auto-create-queue=true)
> {code}
> This feature is not supported.
> Issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months