[JBoss JIRA] (DROOLS-2997) [DMN Designer] Add support for DMN v1.2
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2997?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2997:
-----------------------------------
Labels: drools-tools (was: )
> [DMN Designer] Add support for DMN v1.2
> ---------------------------------------
>
> Key: DROOLS-2997
> URL: https://issues.jboss.org/browse/DROOLS-2997
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The DMN Editor needs to support DMN v1.2
> This requires enhancements to the marshalling and UI.
> More specifically we need both to support DMN v1.1 and v1.2 models and restrict the operations that can be performed by the User in the editor when handling a v1.1 model (the editor needs to support v1.2 operations).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Jan-Willem Gmelig Meyling (JIRA)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Jan-Willem Gmelig Meyling commented on WFLY-10531:
--------------------------------------------------
After some looking into WFLY-9501, I think the implementation causes an regression that does not close a JMS context at all if it the delegate is not first accessed through a method in tranaction state Active. Ie. any callee in transaction status Committing, NotActive, etc.etc. will not register the cleanUpListener (see: https://github.com/JiriOndrusek/wildfly/blob/6355f48234b1b976230c3c529d5a...) , and the context will also not be closed with the destroyal of the bean due to the removal of the PreDestroy annotation on : https://github.com/JiriOndrusek/wildfly/commit/6355f48234b1b976230c3c529d...
[~jondruse] can you please elaborate on your implementation?
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
> Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip
>
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-2997) [DMN Designer] Add support for DMN v1.2
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2997?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2997:
-----------------------------------
Sprint: 2018 Week 42-44
> [DMN Designer] Add support for DMN v1.2
> ---------------------------------------
>
> Key: DROOLS-2997
> URL: https://issues.jboss.org/browse/DROOLS-2997
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.11.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
>
> The DMN Editor needs to support DMN v1.2
> This requires enhancements to the marshalling and UI.
> More specifically we need both to support DMN v1.1 and v1.2 models and restrict the operations that can be performed by the User in the editor when handling a v1.1 model (the editor needs to support v1.2 operations).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2522:
----------------------------------------
[~uxdlc] [~tirelli] Video of _new_ palette attached.
> [DMN Designer] Palette aesthetics
> ---------------------------------
>
> Key: DROOLS-2522
> URL: https://issues.jboss.org/browse/DROOLS-2522
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: drools-tools
> Attachments: DROOLS-2522.mp4, palette.png
>
>
> The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2522:
-----------------------------------
Attachment: DROOLS-2522.mp4
> [DMN Designer] Palette aesthetics
> ---------------------------------
>
> Key: DROOLS-2522
> URL: https://issues.jboss.org/browse/DROOLS-2522
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: drools-tools
> Attachments: DROOLS-2522.mp4, palette.png
>
>
> The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (WFLY-9455) WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-9455?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated WFLY-9455:
----------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/11702
> WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions
> -------------------------------------------------------------------------------------
>
> Key: WFLY-9455
> URL: https://issues.jboss.org/browse/WFLY-9455
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Affects Versions: 11.0.0.CR1
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Fix For: 15.0.0.Alpha1
>
>
> It happens to get exception
> {code}
> ERROR [org.jboss.as.txn] (default task-12) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 0
> ERROR [org.jboss.as.txn] (default task-12) WFLYTX0001: Unable to roll back active transaction: javax.transaction.SystemException: WFTXN0032: Rollback not allowed on imported transaction
> at org.wildfly.transaction.client.LocalTransaction.rollbackAndDissociate(LocalTransaction.java:100)
> at org.wildfly.transaction.client.ContextTransactionManager.rollback(ContextTransactionManager.java:83)
> at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137)
> at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1510)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:326)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> when using XTS transactions bridged to JTA for EJB handling. This happens on change of integration layer for WFTC in WFLY11.
> The integration issues were already discussed as part of the JBTM-2853.
> Here I hit a trouble of having log filled with the exception mentioned above. This does not cause a functionality trouble but the log is ugly filled with ERRORs.
> The trouble seems to be caused by the fact that transaction is imported on ivocation of WS
> https://github.com/wildfly/wildfly/blob/master/webservices/server-integra...
> but as it was suspended in the integration code before
> https://github.com/jbosstm/narayana/blob/master/txbridge/src/main/java/or...
> now the WFTC holds the notion about the transaction even on call of
> https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java...
> and such transaction is tried to be rollback which is forbidden on WFTC for imported ones and thus at least ERROR msg is written to the log.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-2762) [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2762?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2762:
---------------------------------------
Sprint: 2018 Week 30-32, 2018 Week 36-38 (was: 2018 Week 30-32, 2018 Week 36-38, 2018 Week 39-41)
> [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2762
> URL: https://issues.jboss.org/browse/DROOLS-2762
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: DROOLS-2762.png
>
>
> The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition):
> - This component must be disabled (or hidden) when an existing/primitive data type is selected.
> h3. Acceptance test
> - User not able to add and save lines that are filled just partially (this requirement will be addressed by the https://issues.jboss.org/browse/DROOLS-3022)
> - Added top level item definition present in output data type select box immediately (x) DROOLS-2948
> - Added item definition has structure icon if added as structure (x) DROOLS-3037
> - Check added rows after reopening (x) DROOLS-3038
> - The "Add row" button must always appear to the user (e.q. a lot of item definitions present) (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-2842) [DMN Designer] Recursive item definitions
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2842?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2842:
---------------------------------------
Sprint: 2018 Week 36-38 (was: 2018 Week 36-38, 2018 Week 39-41)
> [DMN Designer] Recursive item definitions
> -----------------------------------------
>
> Key: DROOLS-2842
> URL: https://issues.jboss.org/browse/DROOLS-2842
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, recursive-structure-error.log
>
>
> Opening DMN model with recursive item definition inside causes unexpected error dialog with the attached error inside.
> h2. Acceptance test
> - Opening model with recursive item definition informs user with reasonable message and opens plain xml editor (/)
> - Edit data type in manage custom data type dialog that will lead to Recursive item definitions, save and reopen (/) but missing icon DROOLS-3037
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months