[JBoss JIRA] (DROOLS-3185) [DMN Designer] Change Literal Expression to Decision Table
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3185?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3185:
--------------------------------
Description:
When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns.
h2. Manual Acceptance Test
Check steps to reproduce, while InputData node has data type
- Built in type (/)
- Custom type that has constraint
- Custom type that is collection
- Custom type that is recursive
- Multiple InputData nodes
- -Multiple input nodes, mixed InputData and Decision- doesn't work, not supported
was:
When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns.
h2. Manual Acceptance Test
Check steps to reproduce, while InputData node has data type
- Built in type
- Custom type that has constraint
- Custom type that is collection
- Custom type that is recursive
- Multiple InputData nodes
- -Multiple input nodes, mixed InputData and Decision- doesn't work, not supported
> [DMN Designer] Change Literal Expression to Decision Table
> ----------------------------------------------------------
>
> Key: DROOLS-3185
> URL: https://issues.jboss.org/browse/DROOLS-3185
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-25 14-40-06.png, screenshot-1.png
>
>
> When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns.
> h2. Manual Acceptance Test
> Check steps to reproduce, while InputData node has data type
> - Built in type (/)
> - Custom type that has constraint
> - Custom type that is collection
> - Custom type that is recursive
> - Multiple InputData nodes
> - -Multiple input nodes, mixed InputData and Decision- doesn't work, not supported
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3185) [DMN Designer] Change Literal Expression to Decision Table
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3185?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3185:
--------------------------------
Description:
When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns.
h2. Manual Acceptance Test
Check steps to reproduce, while InputData node has data type
- Built in type
- Custom type that has constraint
- Custom type that is collection
- Custom type that is recursive
- Multiple InputData nodes
- -Multiple input nodes, mixed InputData and Decision- doesn't work, not supported
was:
When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns.
h2. Manual Acceptance Test
Check steps to reproduce, while InputData node has data type
- Built in type
- Custom type that has constraint
- Custom type that is collection
- Custom type that is recursive
- Multiple InputData nodes
- Multiple input nodes, mixed InputData and Decision
> [DMN Designer] Change Literal Expression to Decision Table
> ----------------------------------------------------------
>
> Key: DROOLS-3185
> URL: https://issues.jboss.org/browse/DROOLS-3185
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
> Attachments: Screenshot from 2018-10-25 14-40-06.png, screenshot-1.png
>
>
> When user changes Decision node top level expression from literal expression to decision table, that decision table misses InputClause columns.
> h2. Manual Acceptance Test
> Check steps to reproduce, while InputData node has data type
> - Built in type
> - Custom type that has constraint
> - Custom type that is collection
> - Custom type that is recursive
> - Multiple InputData nodes
> - -Multiple input nodes, mixed InputData and Decision- doesn't work, not supported
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11062) No Multi-Release infinispan-commons-9.3.3.Final-redhat-00001.jar
by Carlo de Wolf (Jira)
[ https://issues.jboss.org/browse/WFLY-11062?page=com.atlassian.jira.plugin... ]
Carlo de Wolf updated WFLY-11062:
---------------------------------
Labels: SET- (was: )
> No Multi-Release infinispan-commons-9.3.3.Final-redhat-00001.jar
> ----------------------------------------------------------------
>
> Key: WFLY-11062
> URL: https://issues.jboss.org/browse/WFLY-11062
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.1.Final, 15.0.0.Alpha1
> Reporter: tommaso borgato
> Priority: Major
> Labels: SET-
>
> Project {{org.infinispan:infinispan-commons:9.3.3.Final}} contains classes specific for JDK-10.
> In the {{pom.xml}} file there is a {{jdk10-compile}} profile for the multi-release compilation.
> The MANIFEST in jar {{infinispan-commons-9.3.3.Final-redhat-00001.jar}} shipped with {{jboss-eap-7.2.0.CD14.CR1.zip}} does not contain line {{Multi-Release: true}}.
> Note this may be related to JBEAP-15502.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (JGRP-2311) tshark/wireshark support
by Bela Ban (Jira)
[ https://issues.jboss.org/browse/JGRP-2311?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2311:
--------------------------------
The attached tshark-convert.py file converts PCAP files into files readable by ParseMessages. It would be desirable to get rid of this intermediate step and make ParseMessages read from PCAP / stdin directly.
> tshark/wireshark support
> ------------------------
>
> Key: JGRP-2311
> URL: https://issues.jboss.org/browse/JGRP-2311
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 4.0.16
>
> Attachments: tshark-convert.py
>
>
> 1. Dump contents of wireshark/tahsrk/tcpdump-generated (PCAP) files (using {{ParseMessages}}
> 2. Do this dynamically, e.g. `tshark -Tfields -e data` | java ParseMessages
> In the second instantiation, ParseMessages would read packets from stdin.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (JGRP-2311) tshark/wireshark support
by Bela Ban (Jira)
Bela Ban created JGRP-2311:
------------------------------
Summary: tshark/wireshark support
Key: JGRP-2311
URL: https://issues.jboss.org/browse/JGRP-2311
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.0.16
1. Dump contents of wireshark/tahsrk/tcpdump-generated (PCAP) files (using {{ParseMessages}}
2. Do this dynamically, e.g. `tshark -Tfields -e data` | java ParseMessages
In the second instantiation, ParseMessages would read packets from stdin.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-9954) Too many services and dependencies created for EJBs
by Carlo de Wolf (Jira)
[ https://issues.jboss.org/browse/WFLY-9954?page=com.atlassian.jira.plugin.... ]
Carlo de Wolf reassigned WFLY-9954:
-----------------------------------
Assignee: Romain Pelisse
> Too many services and dependencies created for EJBs
> ---------------------------------------------------
>
> Key: WFLY-9954
> URL: https://issues.jboss.org/browse/WFLY-9954
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: David Lloyd
> Assignee: Romain Pelisse
> Priority: Critical
>
> If a deployment contains more than 2730 EJBs, the deployment's INSTALL phase will get a stack trace like this:
> {noformat}
> 2018-03-25 08:22:34,115 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."example.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."example.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "example.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: Too many dependencies specified (max is 16383) .......... (*1)
> at org.jboss.msc.service.ServiceBuilderImpl.doAddDependency(ServiceBuilderImpl.java:216)
> at org.jboss.msc.service.ServiceBuilderImpl.addDependenciesNoCheck(ServiceBuilderImpl.java:158)
> at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:152)
> at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:142)
> at org.jboss.as.naming.deployment.JndiNamingDependencyProcessor.deploy(JndiNamingDependencyProcessor.java:59)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> {noformat}
> The reason is that the INSTALL phase has six additional dependencies per EJB:
> * service jboss.naming.context.java.comp.example.example.<class-name>.InAppClientContainer
> * service jboss.naming.context.java.comp.example.example.<class-name>.InstanceName
> * service jboss.deployment.unit."example.jar".component.<class-name>.JndiBindingsService
> * service jboss.naming.context.java.comp.example.example.<class-name>.UserTransaction
> * service jboss.naming.context.java.comp.example.example.<class-name>.TransactionSynchronizationRegistry
> * service jboss.naming.context.java.comp.example.example.<class-name>.BeanManager
> We probably should not be creating N dependencies per deployment object since all the services of a given kind are always started together. They could be grouped at a deployment level instead.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (JGRP-2310) SubstrateVM
by Bela Ban (Jira)
Bela Ban created JGRP-2310:
------------------------------
Summary: SubstrateVM
Key: JGRP-2310
URL: https://issues.jboss.org/browse/JGRP-2310
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.0.16
Compile JGroups to run with SubstrateVM and run (e.g.) Draw with it
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months