June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-40) CLI prompt is rendered at first line without clearing of screen

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFWIP-40?page=com.atlassian.jira.plugin.s... ] Jean-Francois Denise commented on WFWIP-40: ------------------------------------------- [~eduda] are you trying with the branch that contains the search feature? > CLI prompt is rendered at first line without clearing of screen > --------------------------------------------------------------- > > Key: WFWIP-40 > URL: https://issues.jboss.org/browse/WFWIP-40 > Project: WildFly WIP > Issue Type: Bug > Reporter: Erich Duda > Assignee: Marek Marusic > Labels: WFCORE-3568 > Attachments: screenshot.png > > > Type following commands. > {code} > $ ./bin/jboss-cli.sh > [disconnected /] embed-server > {code} > When I type aforementioned commands the CLI prompt is rendered at first line of terminal, but the screen is not cleared before it. See attached screenshot. > !screenshot.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-21) [Artemis 2.x upgrade] Lost message when MDB is resending messages under high load

by Martin Styk (JIRA)

[ https://issues.jboss.org/browse/WFWIP-21?page=com.atlassian.jira.plugin.s... ] Martin Styk updated WFWIP-21: ----------------------------- Component/s: Artemis > [Artemis 2.x upgrade] Lost message when MDB is resending messages under high load > --------------------------------------------------------------------------------- > > Key: WFWIP-21 > URL: https://issues.jboss.org/browse/WFWIP-21 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis, JMS > Reporter: Miroslav Novak > Assignee: Martyn Taylor > Priority: Blocker > Labels: activemq, feature-branch-blocker > > Test scenario: > * Start cluster A of nodes node-1, node-3 > * Start cluster B of nodes node-2, node-4 > * Send messages to queue on node-1 > * Deploy mdbs to servers in cluster A. This mdb reads messages from local queue, sends them to remote queue on cluster B and inserts them into database > * Deploy mdbs to servers in cluster B. This mdb reads messages from local queue and inserts them into database > * Cause CPU overload (for 5 min) on server node-2 when mdbs on cluster1 and 2 are processing mesages > * Restart failed server > * Let MDBs to process remaining messages > Pass Criteria: Number of sent message is equal number of records(lines) in database and messages in > Actual Result: > Sometimes happens that one record is missing in database which means that one message was not processed be MDB in cluster 2. > This looks like broker related regression against Artemis 1.5. > Wildfly: https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_w... (06c878a313d3cad323889d017e60fd5533204d1a) > Artemis tag 2.5.0.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-40) CLI prompt is rendered at first line without clearing of screen

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFWIP-40?page=com.atlassian.jira.plugin.s... ] Jean-Francois Denise reassigned WFWIP-40: ----------------------------------------- Assignee: Jean-Francois Denise (was: Marek Marusic) > CLI prompt is rendered at first line without clearing of screen > --------------------------------------------------------------- > > Key: WFWIP-40 > URL: https://issues.jboss.org/browse/WFWIP-40 > Project: WildFly WIP > Issue Type: Bug > Reporter: Erich Duda > Assignee: Jean-Francois Denise > Labels: WFCORE-3568 > Attachments: screenshot.png > > > Type following commands. > {code} > $ ./bin/jboss-cli.sh > [disconnected /] embed-server > {code} > When I type aforementioned commands the CLI prompt is rendered at first line of terminal, but the screen is not cleared before it. See attached screenshot. > !screenshot.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2535) Standalone Authoring - Project Explorer should show up

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2535?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2535: ----------------------------------- Sprint: 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 17-18, 2018 Week 19-22) > Standalone Authoring - Project Explorer should show up > ------------------------------------------------------ > > Key: DROOLS-2535 > URL: https://issues.jboss.org/browse/DROOLS-2535 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > When using the Workbench standalone the Project Explorer does not show up for kie-wb.war. It does work for kie-drools-wb.war -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2549) [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2549?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2549: ----------------------------------- Sprint: 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 19-22) > [DMN Designer] Add support for 'parent' to DMNModelInstrumentedBase > ------------------------------------------------------------------- > > Key: DROOLS-2549 > URL: https://issues.jboss.org/browse/DROOLS-2549 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > > {{DMNModelInstrumentedBase}} needs to support {{parent}} (like {{org.kie.dmn.model.v1_1.DMNModelInstrumentedBase}}) in order to correctly implement {{getPrefixForNamespaceURI(..)}} that is needed to set the {{QName}} prefix when setting data-types on nodes. > At the moment the {{QName}} for data-types in the UI is using the {{namespaceURI}} instead of the {{prefix}} as it is currently impossible to lookup a {{prefix}} from the {{namespaceURI}} (of the nodes' parents up to {{Definitions}}). > Changes required for this JIRA (split into sub-tasks when work starts):- > * Update XML->(kie)DMN->(ui)DMN model mapping in the marshaller > * Update the UI to set {{parent}} when adding nodes to the {{DRGElement}} and children > * Update code relating to "setting data-type" to lookup {{prefix}} for {{QName}} (/) > * When creating a new Diagram we need to set up the basic default NameSpace contexts on the {{DMNDiagram}}'s {{Defintions}} (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-18) [Artemis upgrade] Artemis creates and use NODE_MANAGER table even though HA is not configured

by Martin Styk (JIRA)

[ https://issues.jboss.org/browse/WFWIP-18?page=com.atlassian.jira.plugin.s... ] Martin Styk updated WFWIP-18: ----------------------------- Component/s: Artemis (was: JMS) > [Artemis upgrade] Artemis creates and use NODE_MANAGER table even though HA is not configured > --------------------------------------------------------------------------------------------- > > Key: WFWIP-18 > URL: https://issues.jboss.org/browse/WFWIP-18 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > Labels: activemq, feature-branch-blocker > Attachments: standalone-full-ha.xml > > > If Artemis is not configured to use HA then it should not create and use journal-node-manager-store-table table which is normally used by live/backup pair. > Problem here is that especially if 2 servers are started and are using the database then administrator logically does not set journal-node-manager-store-table as HA is not used. However in the moment when both of the servers are started they use default values and both of them start to use the same table (default is NODE_MANAGER) then one of them fail with: > {code} > 09:20:03,246 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ221034: Waiting 60000 milliseconds to obtain live lock > 09:21:03,517 ERROR [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ224000: Failure in initialisation: java.lang.Exception: timed out waiting for lock > at org.apache.activemq.artemis.core.server.impl.jdbc.JdbcNodeManager.lock(JdbcNodeManager.java:240) [artemis-server-2.5.0.jar:2.5.0] > at org.apache.activemq.artemis.core.server.impl.jdbc.JdbcNodeManager.startLiveNode(JdbcNodeManager.java:346) [artemis-server-2.5.0.jar:2.5.0] > at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:65) [artemis-server-2.5.0.jar:2.5.0] > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:522) [artemis-server-2.5.0.jar:2.5.0] > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:461) [artemis-server-2.5.0.jar:2.5.0] > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:376) [artemis-jms-server-2.5.0.jar:2.5.0] > at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:205) [wildfly-messaging-activemq-13.0.0.Alpha1-SNAPSHOT.jar:13.0.0.Alpha1-SNAPSHOT] > at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:64) [wildfly-messaging-activemq-13.0.0.Alpha1-SNAPSHOT.jar:13.0.0.Alpha1-SNAPSHOT] > at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:99) [wildfly-messaging-activemq-13.0.0.Alpha1-SNAPSHOT.jar:13.0.0.Alpha1-SNAPSHOT] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_131] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131] > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131] > at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] > 09:21:03,520 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service jboss.messaging-activemq.default.jms.manager: org.jboss.msc.service.StartException in service jboss.messaging-activemq.default.jms.manager: java.lang.Exception: timed out waiting for lock > at org.wildfly.extension.messaging.activemq.jms.JMSService.lambda$doStart$0(JMSService.java:141) [wildfly-messaging-activemq-13.0.0.Alpha1-SNAPSHOT.jar:13.0.0.Alpha1-SNAPSHOT] > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.callActivationFailureListeners(ActiveMQServerImpl.java:1908) [artemis-server-2.5.0.jar:2.5.0] > at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:82) [artemis-server-2.5.0.jar:2.5.0] > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:522) [artemis-server-2.5.0.jar:2.5.0] > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:461) [artemis-server-2.5.0.jar:2.5.0] > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:376) [artemis-jms-server-2.5.0.jar:2.5.0] > at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:205) [wildfly-messaging-activemq-13.0.0.Alpha1-SNAPSHOT.jar:13.0.0.Alpha1-SNAPSHOT] > at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:64) [wildfly-messaging-activemq-13.0.0.Alpha1-SNAPSHOT.jar:13.0.0.Alpha1-SNAPSHOT] > at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:99) [wildfly-messaging-activemq-13.0.0.Alpha1-SNAPSHOT.jar:13.0.0.Alpha1-SNAPSHOT] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_131] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_131] > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131] > at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.1.Final.jar:2.3.1.Final] > Caused by: java.lang.Exception: timed out waiting for lock > at org.apache.activemq.artemis.core.server.impl.jdbc.JdbcNodeManager.lock(JdbcNodeManager.java:240) [artemis-server-2.5.0.jar:2.5.0] > at org.apache.activemq.artemis.core.server.impl.jdbc.JdbcNodeManager.startLiveNode(JdbcNodeManager.java:346) [artemis-server-2.5.0.jar:2.5.0] > at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:65) [artemis-server-2.5.0.jar:2.5.0] > ... 14 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2425) [DMN Designer] Undo of relation column deletion is not proper

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2425?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2425: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22) > [DMN Designer] Undo of relation column deletion is not proper > ------------------------------------------------------------- > > Key: DROOLS-2425 > URL: https://issues.jboss.org/browse/DROOLS-2425 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Attachments: Screenshot from 2018-03-27 12-12-05.png, Screenshot from 2018-03-27 12-14-47.png, Screenshot from 2018-03-27 12-14-55.png > > > This issue was spotted during DROOLS-2392 review. > In special cases undo of delete relation column is not proper. > h2. Acceptance test > # Steps to reproduce fixed (/) > # Deletion is undone properly > ## Deletion of con. entry (/) > ## Deletion of Dec. table row (/) > ## Deletion of Dec. table column (x) > ## Deletion of Relation column > ## Deletion of Relation row > ## Deletion of Function parameter > # Clear of expression type is undone properly -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2317) FEEL Syntax error on function(bkm) containing `for` keyword

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2317?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2317: ----------------------------------- Sprint: 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 17-18, 2018 Week 19-22) > FEEL Syntax error on function(bkm) containing `for` keyword > ----------------------------------------------------------- > > Key: DROOLS-2317 > URL: https://issues.jboss.org/browse/DROOLS-2317 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Fedor Gavrilov > Attachments: Dynamic composition.dmn > > > Attached model > {code:java} > Error compiling FEEL expression 'for item in Order.items return Federal Tax for Item( item )' for name 'Calculate Federal Taxes' on node 'Calculate Federal Taxes': syntax error near 'for' > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2454) [DMN Designer] Decision content not visible after reopen

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2454?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2454: ----------------------------------- Sprint: 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 13-14, 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22) > [DMN Designer] Decision content not visible after reopen > -------------------------------------------------------- > > Key: DROOLS-2454 > URL: https://issues.jboss.org/browse/DROOLS-2454 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Fix For: 7.8.0.Final > > Attachments: Screenshot from 2018-04-05 14-35-20.png, Screenshot from 2018-04-05 14-35-52.png > > > If the decision with bigger context table is reopened, its content is not visible. > h2. Acceptance test > In each scenario, width of columns don't have to be same as before closing, however each column should has some minimal/default width. > # Steps to reproduce fixed > # Define top level as Literal expression, reopen > # Define top level as Decision table, add columns, reopen > # Define top level as Relation, add columns, reopen > # Define top level as Invocation, specify complex parameters, reopen > # Define top level as Function, add a lot of parameters, reopen > # Define top level as Context, recursively add more Contexts, reopen -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2476) Promote Profile in public kie dmn API

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2476?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2476: ----------------------------------- Sprint: 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22, 2018 Week 23-24 (was: 2018 Week 15-16, 2018 Week 17-18, 2018 Week 19-22) > Promote Profile in public kie dmn API > ------------------------------------- > > Key: DROOLS-2476 > URL: https://issues.jboss.org/browse/DROOLS-2476 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Minor > > # Promote DMNProfile and FEELProfile in public kie dmn api > # Have DMNRuntime to expose getProfiles (read-only method) > # Change jBPM as from: https://github.com/mswiderski/jbpm/blob/ff5dd337e5d57c49eb15277a05c3563c1... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2018