October 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5711) [DMN XML] Signavio Profile - MultiInstanceDecisionLogic: MID requirements are not linked

by Tommy Neubert (Jira)

[ https://issues.redhat.com/browse/DROOLS-5711?page=com.atlassian.jira.plug... ] Tommy Neubert commented on DROOLS-5711: --------------------------------------- [~tari_manga] Hey, i attached the pictures of the model we use in the PR. > [DMN XML] Signavio Profile - MultiInstanceDecisionLogic: MID requirements are not linked > ---------------------------------------------------------------------------------------- > > Key: DROOLS-5711 > URL: https://issues.redhat.com/browse/DROOLS-5711 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Jonas Beyer > Assignee: Matteo Mortari > Priority: Minor > Attachments: DRG.png, DecisionLogic.PNG > > > h3. Summary: > When evaluating a decision model that contains a MultiInstanceDecision, the result will often times be {{[null]}}, because the engine will not evaluate the decision dependencies of the MID first, and simply execute the MID with empty inputs instead. > h3. Details: > The statement that will cause decisions to consider their requirements during evaluation is missing for MultiInstanceDecisions: > {code:java} > compiler.linkRequirements( model, di );{code} > Inside {{org.kie.dmn.signavio.MultiInstanceDecisionLogic.MultiInstanceDecisionNodeCompiler#compileEvaluator}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5711) [DMN XML] Signavio Profile - MultiInstanceDecisionLogic: MID requirements are not linked

by Tommy Neubert (Jira)

[ https://issues.redhat.com/browse/DROOLS-5711?page=com.atlassian.jira.plug... ] Tommy Neubert updated DROOLS-5711: ---------------------------------- Attachment: DRG.png > [DMN XML] Signavio Profile - MultiInstanceDecisionLogic: MID requirements are not linked > ---------------------------------------------------------------------------------------- > > Key: DROOLS-5711 > URL: https://issues.redhat.com/browse/DROOLS-5711 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Jonas Beyer > Assignee: Matteo Mortari > Priority: Minor > Attachments: DRG.png, DecisionLogic.PNG > > > h3. Summary: > When evaluating a decision model that contains a MultiInstanceDecision, the result will often times be {{[null]}}, because the engine will not evaluate the decision dependencies of the MID first, and simply execute the MID with empty inputs instead. > h3. Details: > The statement that will cause decisions to consider their requirements during evaluation is missing for MultiInstanceDecisions: > {code:java} > compiler.linkRequirements( model, di );{code} > Inside {{org.kie.dmn.signavio.MultiInstanceDecisionLogic.MultiInstanceDecisionNodeCompiler#compileEvaluator}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5711) [DMN XML] Signavio Profile - MultiInstanceDecisionLogic: MID requirements are not linked

by Tommy Neubert (Jira)

[ https://issues.redhat.com/browse/DROOLS-5711?page=com.atlassian.jira.plug... ] Tommy Neubert updated DROOLS-5711: ---------------------------------- Attachment: DecisionLogic.PNG > [DMN XML] Signavio Profile - MultiInstanceDecisionLogic: MID requirements are not linked > ---------------------------------------------------------------------------------------- > > Key: DROOLS-5711 > URL: https://issues.redhat.com/browse/DROOLS-5711 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Jonas Beyer > Assignee: Matteo Mortari > Priority: Minor > Attachments: DRG.png, DecisionLogic.PNG > > > h3. Summary: > When evaluating a decision model that contains a MultiInstanceDecision, the result will often times be {{[null]}}, because the engine will not evaluate the decision dependencies of the MID first, and simply execute the MID with empty inputs instead. > h3. Details: > The statement that will cause decisions to consider their requirements during evaluation is missing for MultiInstanceDecisions: > {code:java} > compiler.linkRequirements( model, di );{code} > Inside {{org.kie.dmn.signavio.MultiInstanceDecisionLogic.MultiInstanceDecisionNodeCompiler#compileEvaluator}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (LOGMGR-280) SocketHandlerTests hangs on new JDKs

by Marek Kopecky (Jira)

[ https://issues.redhat.com/browse/LOGMGR-280?page=com.atlassian.jira.plugi... ] Marek Kopecky updated LOGMGR-280: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/318 > SocketHandlerTests hangs on new JDKs > ------------------------------------ > > Key: LOGMGR-280 > URL: https://issues.redhat.com/browse/LOGMGR-280 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: Marek Kopecky > Assignee: Marek Kopecky > Priority: Major > > SocketHandlerTests hangs on new JDKs > Affected test methods: > * SocketHandlerTests#testProtocolChange > * SocketHandlerTests#testTlsConfig > Test fails just on some JDK. Examples: > * test pass on Oracle JDK 11.0.6 > {noformat} > java version "11.0.6" 2020-01-14 LTS > Java(TM) SE Runtime Environment 18.9 (build 11.0.6+8-LTS) > Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.6+8-LTS, mixed mode) > {noformat} > * test pass on Open JDK 11.0.8 > {noformat} > openjdk version "11.0.8" 2020-07-14 > OpenJDK Runtime Environment 18.9 (build 11.0.8+10) > OpenJDK 64-Bit Server VM 18.9 (build 11.0.8+10, mixed mode, sharing) > {noformat} > * test fails on Oracle JDK 11.0.8 > {noformat} > java version "11.0.8" 2020-07-14 LTS > Java(TM) SE Runtime Environment 18.9 (build 11.0.8+10-LTS) > Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.8+10-LTS, mixed mode) > {noformat} > This issue is valid at least for branches 2.1 (2.1.17.Final) and master (and probably for 2.2 and 2.3 as well) > Test hangs in "SimpleServer$TcpServer.close" during "socket.close();" call. > {noformat} > org.jboss.logmanager.handlers.SimpleServer$TcpServer.close(SimpleServer.java:127) > org.jboss.logmanager.handlers.SocketHandlerTests.testProtocolChange(SocketHandlerTests.java:129) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (LOGMGR-280) SocketHandlerTests hangs on new JDKs

by Marek Kopecky (Jira)

Marek Kopecky created LOGMGR-280: ------------------------------------ Summary: SocketHandlerTests hangs on new JDKs Key: LOGMGR-280 URL: https://issues.redhat.com/browse/LOGMGR-280 Project: JBoss Log Manager Issue Type: Bug Reporter: Marek Kopecky Assignee: Marek Kopecky SocketHandlerTests hangs on new JDKs Affected test methods: * SocketHandlerTests#testProtocolChange * SocketHandlerTests#testTlsConfig Test fails just on some JDK. Examples: * test pass on Oracle JDK 11.0.6 {noformat} java version "11.0.6" 2020-01-14 LTS Java(TM) SE Runtime Environment 18.9 (build 11.0.6+8-LTS) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.6+8-LTS, mixed mode) {noformat} * test pass on Open JDK 11.0.8 {noformat} openjdk version "11.0.8" 2020-07-14 OpenJDK Runtime Environment 18.9 (build 11.0.8+10) OpenJDK 64-Bit Server VM 18.9 (build 11.0.8+10, mixed mode, sharing) {noformat} * test fails on Oracle JDK 11.0.8 {noformat} java version "11.0.8" 2020-07-14 LTS Java(TM) SE Runtime Environment 18.9 (build 11.0.8+10-LTS) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.8+10-LTS, mixed mode) {noformat} This issue is valid at least for branches 2.1 (2.1.17.Final) and master (and probably for 2.2 and 2.3 as well) Test hangs in "SimpleServer$TcpServer.close" during "socket.close();" call. {noformat} org.jboss.logmanager.handlers.SimpleServer$TcpServer.close(SimpleServer.java:127) org.jboss.logmanager.handlers.SocketHandlerTests.testProtocolChange(SocketHandlerTests.java:129) {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13954) Class not found error in Jakarta EE 9 deployment stage

by hantsy bai (Jira)

hantsy bai created WFLY-13954: --------------------------------- Summary: Class not found error in Jakarta EE 9 deployment stage Key: WFLY-13954 URL: https://issues.redhat.com/browse/WFLY-13954 Project: WildFly Issue Type: Bug Components: EE Affects Versions: 21.0.0.Beta1 Reporter: hantsy bai Assignee: Brian Stansberry When I deployed a Jakarata EE 9 applicaiton into 21, got the following exception in the deployment progress. ``` 11:05:04,558 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 4) WELD-000119: Not generating any bean definitions from com.example.GreetingResource because of underlying class loa ding error: Type jakarta.ws.rs.core.Response from [Module "deployment.jakartaee9-starter-boilerplate.war" from Service Module Loader] not found. If this is unexpected, enable DEBUG lo gging to see the full error. 11:05:04,558 WARN [org.jboss.modules.define] (Weld Thread Pool -- 2) Failed to define class com.example.JaxrsActivator in Module "deployment.jakartaee9-starter-boilerplate.war" from S ervice Module Loader: java.lang.NoClassDefFoundError: Failed to link com/example/JaxrsActivator (Module "deployment.jakartaee9-starter-boilerplate.war" from Service Module Loader): jak arta/ws/rs/core/Application at java.base/java.lang.ClassLoader.defineClass1(Native Method) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1017) at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1096) at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:424) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:555) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126) at org.jboss.modules.Module.loadModuleClass(Module.java:731) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) at org.jboss.as.weld@21.0.0.Beta1//org.jboss.as.weld.WeldModuleResourceLoader.classForName(WeldModuleResourceLoader.java:68) at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.bootstrap.AnnotatedTypeLoader.loadClass(AnnotatedTypeLoader.java:82) at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.bootstrap.AnnotatedTypeLoader.loadAnnotatedType(AnnotatedTypeLoader.java:62) at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.bootstrap.FastAnnotatedTypeLoader.loadAnnotatedType(FastAnnotatedTypeLoader.java:108) at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:87) at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.bootstrap.ConcurrentBeanDeployer$1.doWork(ConcurrentBeanDeployer.java:55) at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.bootstrap.ConcurrentBeanDeployer$1.doWork(ConcurrentBeanDeployer.java:52) at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62) at org.jboss.weld.core@3.1.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513) 11:05:04,558 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from com.example.JaxrsActivator because of underlying class loadi ng error: Type Failed to link com.example.JaxrsActivator (Module "deployment.jakartaee9-starter-boilerplate.war" from Service Module Loader): jakarta.ws.rs.core.Application not found. If this is unexpected, enable DEBUG logging to see the full error. ``` -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13953) Upgrade WildFly Arquillian to 3.0.1.Final

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-13953?page=com.atlassian.jira.plugi... ] James Perkins moved WFCORE-5154 to WFLY-13953: ---------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-13953 (was: WFCORE-5154) Component/s: Test Suite (was: Test Suite) > Upgrade WildFly Arquillian to 3.0.1.Final > ----------------------------------------- > > Key: WFLY-13953 > URL: https://issues.redhat.com/browse/WFLY-13953 > Project: WildFly > Issue Type: Component Upgrade > Components: Test Suite > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Upgrade WildFly Arquillian to 3.0.1.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5154) Upgrade WildFly Arquillian to 3.0.1.Final

by James Perkins (Jira)

James Perkins created WFCORE-5154: ------------------------------------- Summary: Upgrade WildFly Arquillian to 3.0.1.Final Key: WFCORE-5154 URL: https://issues.redhat.com/browse/WFCORE-5154 Project: WildFly Core Issue Type: Component Upgrade Components: Test Suite Reporter: James Perkins Assignee: James Perkins Upgrade WildFly Arquillian to 3.0.1.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5679) Implement kie pmml trusty integration tests

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5679?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5679. ------------------------------------ Resolution: Won't Do Integrations tests will be added inside drools-jbpmintegration in the DROOLS-5688 PR > Implement kie pmml trusty integration tests > ------------------------------------------- > > Key: DROOLS-5679 > URL: https://issues.redhat.com/browse/DROOLS-5679 > Project: Drools > Issue Type: Enhancement > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Implement full roundtrip integration tests for PMML trusty > 1) creation of kjar out of pmml files > 2) it project that uses kjar via maven > 3) it project that uses kjar via kiecontainer > 4) it project that directly declare and uses pmml files -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-2028) Resource leak in JaspiAuthenticationContext

by Ilia Vassilev (Jira)

Ilia Vassilev created ELY-2028: ---------------------------------- Summary: Resource leak in JaspiAuthenticationContext Key: ELY-2028 URL: https://issues.redhat.com/browse/ELY-2028 Project: WildFly Elytron Issue Type: Bug Components: Authentication Mechanisms Affects Versions: 1.13.1.Final Reporter: Ilia Vassilev Assignee: Ilia Vassilev AutoCloseable resource ServerAuthenticationContext not closed in org.wildfly.security.auth.jaspi.impl.JaspiAuthenticationContext.createCommonCallbackHandler() -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2020