[JBoss JIRA] (WFLY-12194) Add a testcase that checks remote client transaction afinity in case of falied server
by Ondrej Chaloupka (Jira)
Ondrej Chaloupka created WFLY-12194:
---------------------------------------
Summary: Add a testcase that checks remote client transaction afinity in case of falied server
Key: WFLY-12194
URL: https://issues.jboss.org/browse/WFLY-12194
Project: WildFly
Issue Type: Enhancement
Components: Test Suite
Affects Versions: 17.0.0.Final
Reporter: Ondrej Chaloupka
Assignee: Ondrej Chaloupka
The remote client transaction affinity is not well covered in testsuite.
Particularly, it would be good to test what happens when a transaction starts on a standalone client. The call goes to a stateless bean. There are two servers started in server that the client can choose. The client starts transaction, calls the bean and then the server fails. Will be the next call to bean fails correctly? (as it could be expected as the affinity points to the non-existent server, despite the fact there is another server deploying the same stateless bean)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12194) Add a testcase that checks remote client transaction afinity in case of failed server
by Ondrej Chaloupka (Jira)
[ https://issues.jboss.org/browse/WFLY-12194?page=com.atlassian.jira.plugin... ]
Ondrej Chaloupka updated WFLY-12194:
------------------------------------
Summary: Add a testcase that checks remote client transaction afinity in case of failed server (was: Add a testcase that checks remote client transaction afinity in case of falied server)
> Add a testcase that checks remote client transaction afinity in case of failed server
> -------------------------------------------------------------------------------------
>
> Key: WFLY-12194
> URL: https://issues.jboss.org/browse/WFLY-12194
> Project: WildFly
> Issue Type: Enhancement
> Components: Test Suite
> Affects Versions: 17.0.0.Final
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Major
>
> The remote client transaction affinity is not well covered in testsuite.
> Particularly, it would be good to test what happens when a transaction starts on a standalone client. The call goes to a stateless bean. There are two servers started in server that the client can choose. The client starts transaction, calls the bean and then the server fails. Will be the next call to bean fails correctly? (as it could be expected as the affinity points to the non-existent server, despite the fact there is another server deploying the same stateless bean)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4156) Compilation requires PMML Document and Model but passes even if just Document is present
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-4156?page=com.atlassian.jira.plugi... ]
Matteo Mortari updated DROOLS-4156:
-----------------------------------
Sprint: 2019 Week 23-25
> Compilation requires PMML Document and Model but passes even if just Document is present
> ----------------------------------------------------------------------------------------
>
> Key: DROOLS-4156
> URL: https://issues.jboss.org/browse/DROOLS-4156
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Reporter: Jozef Marko
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: doc-no-model.png, no-doc-no-model.png
>
>
> This issue was revealed as part of DROOLS-4042 review.
> - Please create function invocation like shown below:
> -- !no-doc-no-model.png|thumbnail!
> - Please notice *no* Document and *no* Model are provided
> - Save the asset and notice the alerts panel has message about required both Document and Model
> - Now provide the Document and save the asset
> - The previously shown message is completely gone, I would expect message about still missing Model
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4154) kie-dmn-core: PMMLInfo NPE when model has null output
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-4154?page=com.atlassian.jira.plugi... ]
Matteo Mortari updated DROOLS-4154:
-----------------------------------
Sprint: 2019 Week 23-25
> kie-dmn-core: PMMLInfo NPE when model has null output
> -----------------------------------------------------
>
> Key: DROOLS-4154
> URL: https://issues.jboss.org/browse/DROOLS-4154
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.23.0.Final
> Reporter: Michael Anstis
> Assignee: Matteo Mortari
> Priority: Major
> Attachments: model-2.pmml, model-3.pmml, model-4.pmml, model.pmml
>
>
> During testing of the WB changes for PMML support [~jomarko] found the example PMML files referenced by our KIE documentation failed to have a number of models listed against their document definition.
> On examination {{PMMLInfo.from(..)}} throws a NPE if the PMML model lacks an _output_ (see L#57 that throws the NPE if the model has a {{null}} _output_). I've attached the files [~jomarko] used for his testing.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months