[JBoss JIRA] (DROOLS-5154) Set new scesim kogito modules dependency on DROOLS BOM
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5154?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-5154:
-------------------------------
Description:
Introduce the following new scesim kogito modules in DROOLS BOM of kie-parent repo:
drools-wb-scenario-simulation-editor-kogito-marshaller
drools-wb-scenario-simulation-editor-kogito-client
drools-wb-scenario-simulation-editor-kogito-webapp-common
drools-wb-scenario-simulation-editor-kogito-runtime
drools-wb-scenario-simulation-editor-kogito-testing
> Set new scesim kogito modules dependency on DROOLS BOM
> ------------------------------------------------------
>
> Key: DROOLS-5154
> URL: https://issues.redhat.com/browse/DROOLS-5154
> Project: Drools
> Issue Type: Bug
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Minor
>
> Introduce the following new scesim kogito modules in DROOLS BOM of kie-parent repo:
> drools-wb-scenario-simulation-editor-kogito-marshaller
> drools-wb-scenario-simulation-editor-kogito-client
> drools-wb-scenario-simulation-editor-kogito-webapp-common
> drools-wb-scenario-simulation-editor-kogito-runtime
> drools-wb-scenario-simulation-editor-kogito-testing
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (DROOLS-5131) [DMN Designer] Boxed List support
by Stetson Robinson (Jira)
[ https://issues.redhat.com/browse/DROOLS-5131?page=com.atlassian.jira.plug... ]
Stetson Robinson commented on DROOLS-5131:
------------------------------------------
[~manstis], ack. Thank you!
[~hmanwani], fyi ^^ This will impact DMN doc for 7.8.
> [DMN Designer] Boxed List support
> ---------------------------------
>
> Key: DROOLS-5131
> URL: https://issues.redhat.com/browse/DROOLS-5131
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.34.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> Errors when importing DMN model including the Boxed List semantic
> {{PreviewDiagramScreenActivity failed in OPEN: java.lang.RuntimeException: CDI Event exception: CommandType=CDIEvent, BeanType=org.kie.workbench.common.stunner.core.client.canvas.event.registration.CanvasElementAddedEvent, BeanReference=org.kie.workbench.common.stunner.core.client.canvas.event.registration.CanvasElementAddedEvent@cc23, FromClient=1 sent to [unavailable]}}
> We are lacking the support for "Boxed List" semantic, as described page 107 here : https://www.omg.org/spec/DMN/1.2/PDF
> See page 149, "10.5.4 List metamodel"
> The boxed list are represented by separate grid, similar to the Relation grid, however there is single column and no header cell. Other cells can be literal expressions or contexts.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (WFLY-13162) ConcurrentModificationException in WildFlyJobXmlResolver
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-13162?page=com.atlassian.jira.plugi... ]
Cheng Fang commented on WFLY-13162:
-----------------------------------
[~mletenay] too late for WildFly 19, unfortunately.
> ConcurrentModificationException in WildFlyJobXmlResolver
> --------------------------------------------------------
>
> Key: WFLY-13162
> URL: https://issues.redhat.com/browse/WFLY-13162
> Project: WildFly
> Issue Type: Bug
> Components: Batch
> Affects Versions: 18.0.1.Final, 19.0.0.Beta3, 20.0.0.Beta1
> Reporter: Hielke Hoeve
> Assignee: Cheng Fang
> Priority: Major
> Fix For: 20.0.0.Beta1
>
>
> Because of a thread unsafe construction in WildFlyJobXmlResolver I am experiencing ConcurrentModificationExceptions while starting my EAR every so often. This is because every EJB of the EAR is processed by WildFlyJobXmlResolver in paralel threads. Even if it has no jbatch dependency or dependency to a EJB which does.
> This is not reproducable for every startup as it depends on the performance of the host machine, number of ejbs in ear, number of threads and thread timing.
> I have created an example project representing our project setup with which I am able to reproduce the issue using a default wildfly build. This test project contains 1 EJB with jbatch, a number of plain EJBs, a WAR which uses the jbatch EJB and an EAR.
> See below for the exception stacktrace.
> I have made a small fix for this issue @ https://github.com/hielkehoeve/wildfly/commit/82047233621c3e5bdbd45333ca4.... The example test project can also be found there.
> {code:java}
> 08:32:30,164 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."project.ear"."project-d.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."project.ear"."project-d.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "project-d.jar" of deployment "project.ear"
> at org.jboss.as.server@10.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.util.ConcurrentModificationException
> at java.base/java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:719)
> at java.base/java.util.LinkedHashMap$LinkedKeyIterator.next(LinkedHashMap.java:741)
> at java.base/java.util.AbstractCollection.addAll(AbstractCollection.java:351)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.merge(WildFlyJobXmlResolver.java:261)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:127)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.WildFlyJobXmlResolver.forDeployment(WildFlyJobXmlResolver.java:130)
> at org.wildfly.extension.batch.jberet@18.0.0.Final//org.wildfly.extension.batch.jberet.deployment.BatchEnvironmentProcessor.deploy(BatchEnvironmentProcessor.java:78)
> at org.jboss.as.server@10.0.0.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months