[JBoss JIRA] (WFLY-12484) Make org.picketlink.trust.jbossws.handler.SMALHandler supports SAAJ1.4
by Carlo de Wolf (Jira)
[ https://issues.jboss.org/browse/WFLY-12484?page=com.atlassian.jira.plugin... ]
Carlo de Wolf commented on WFLY-12484:
--------------------------------------
The original error can be reproduced by overriding jaxb & saaj.
{noformat}
org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it.
{noformat}
> Make org.picketlink.trust.jbossws.handler.SMALHandler supports SAAJ1.4
> ----------------------------------------------------------------------
>
> Key: WFLY-12484
> URL: https://issues.jboss.org/browse/WFLY-12484
> Project: WildFly
> Issue Type: Task
> Components: Web Services
> Affects Versions: 17.0.1.Final
> Reporter: Jim Ma
> Assignee: Jim Ma
> Priority: Major
> Fix For: 18.0.0.Final
>
> Attachments: 0001-Upgrade-jaxb-saaj.patch
>
>
> To support SAAJ 1.4, Picketlink SMALHandler needs get DOM Element with CXF's DOMUtils to append/remove element from soap message.
> This handler now fails
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFWIP-205) tx recovery intermittently fails after jvm crash
by Ondrej Chaloupka (Jira)
[ https://issues.jboss.org/browse/WFWIP-205?page=com.atlassian.jira.plugin.... ]
Ondrej Chaloupka commented on WFWIP-205:
----------------------------------------
[~simkam] I see. It seems there could be a testsuite misconfiguration that I forgot about (blame on me) With help of [~tomekadamski] I tracked down that it could help if you change the {{standalone-openshift.xml}} configuration to use not the {{loadbalancer}} service but the {{headless}} service.
{{<remote-destination host="tx-server-1.tx-server-loadbalancer" port="8080"/>}} => {{<remote-destination host="tx-server-1.tx-server-headless" port="8080"/>}}
> tx recovery intermittently fails after jvm crash
> ------------------------------------------------
>
> Key: WFWIP-205
> URL: https://issues.jboss.org/browse/WFWIP-205
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Environment: image:
> {noformat}
> docker-registry.engineering.redhat.com/ochaloup/wildfly18-snapshot:190909...
> {noformat}
> operator:
> {noformat}
> docker-registry.engineering.redhat.com/jbossqe-eap/wildfly-operator:EAP7-...
> {noformat}
> operator built from https://github.com/ochaloup/wildfly-operator/tree/issue70-statefulset-hea..., head 8925e7f64b6fc02b4694da63d93c0a8ce03a566d)
> Reporter: Martin Simka
> Assignee: Ondrej Chaloupka
> Priority: Blocker
> Attachments: tx-client-0.log, tx-server-0.log, tx-server-1.log, wildfly-operator-668fd79fb5-8chs8.log
>
>
> While testing tx recovery in OpenShift I see that recovery after JVM crash intermittently fails
> Scenario:
> *ejb client* (app tx-client, pod tx-client-0):
> * EJB business method
> ** lookup remote EJB
> ** enlist XA resource 1 to transaction
> ** enlist XA resource 2 to transaction
> ** call remote EJB
> *ejb server* (app tx-server, pod tx-server-0):
> * EJB business method
> ** enlist XA resource 1 to transaction
> ** enlist XA resource 2 to transaction
> ejb server XA resource 2 crashes JVM in commit method phase.
> Test waits until crashed pod is restarted, then forces periodic recovery twice and then checks that transaction log store is empty. But it is not empty.
> Attached are logs from client and server pods.
> It seems that it can be partially mitigated by clearing openshift namespace before test ({{oc delete all --all}}). But it makes it just less frequent.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4522) Add an "expression" property for every complex type in Scenario Testing
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4522?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4522:
--------------------------------
Attachment: can-be-suspended-expression.webm
> Add an "expression" property for every complex type in Scenario Testing
> -----------------------------------------------------------------------
>
> Key: DROOLS-4522
> URL: https://issues.jboss.org/browse/DROOLS-4522
> Project: Drools
> Issue Type: Feature Request
> Components: Scenario Simulation and Testing
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Fix For: 7.6.0.Final
>
> Attachments: can-be-suspended-expression.webm
>
>
> Basically, with the changes introduced in this PR, every complex type object in Scenario has an additional property ("expression") where it will be possible to add expression logic to the referred object (fact). At the moment, the changes involve only front-end side.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4542) Executable model compilation fails with map modification in action
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4542?page=com.atlassian.jira.plugi... ]
Mario Fusco reassigned DROOLS-4542:
-----------------------------------
Assignee: Luca Molteni (was: Mario Fusco)
> Executable model compilation fails with map modification in action
> ------------------------------------------------------------------
>
> Key: DROOLS-4542
> URL: https://issues.jboss.org/browse/DROOLS-4542
> Project: Drools
> Issue Type: Bug
> Components: core engine, executable model
> Affects Versions: 7.24.0.Final, 7.27.0.Final
> Environment: - 7.24.0.Final and later version
> - building executable model
> - dialect "mvel"
> Reporter: Hiroko Miura
> Assignee: Luca Molteni
> Priority: Major
> Labels: support
> Attachments: generateModel-build-error.zip
>
>
> The following expression on update of Map in RHS causes an error when building executable model.
> * Pattern1
> {noformat}
> m.mapVal["rule1"] = "value1";
> {noformat}
> * Error1 (NPE)
> {noformat}
> [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.24.0.Final:generateModel (default-generateModel) on project build-error: Execution default-generateModel of goal org.kie:kie-maven-plugin:7.24.0.Final:generateModel failed.: NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.kie:kie-maven-plugin:7.24.0.Final:generateModel (default-generateModel) on project build-error: Execution default-generateModel of goal org.kie:kie-maven-plugin:7.24.0.Final:generateModel failed.
> {noformat}
> or
> * Pattern2
> {noformat}
> m.getMapVal().put( "rule2", "value2" );
> {noformat}
> * Error2
> {noformat}
> [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.24.0.Final:generateModel (default-generateModel) on project build-error: A type incompatibility occurred while executing org.kie:kie-maven-plugin:7.24.0.Final:generateModel: sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl cannot be cast to java.lang.Class
> {noformat}
> This does not happen with 7.23.0.Final.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4536) Test scenarios fails with default values
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-4536?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-4536:
--------------------------------
Description:
In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass.
The issue is always reproducible.
h2. Acceptance test
- Default empty text (/)
- Default int zero (x), (/) passed in re-review
- Default double zero (x), (/) passed in re-review
- Default boolean true (/)
was:
In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass.
The issue is always reproducible.
h2. Acceptance test
- Default empty text (/)
- Default int zero (x)
- Default double zero (x)
- Default boolean true (/)
> Test scenarios fails with default values
> ----------------------------------------
>
> Key: DROOLS-4536
> URL: https://issues.jboss.org/browse/DROOLS-4536
> Project: Drools
> Issue Type: Bug
> Components: Test Scenarios Editor
> Affects Versions: 7.25.0.Final
> Reporter: Sudhish Nair
> Assignee: Toni Rikkola
> Priority: Minor
> Labels: drools-tools, support
> Attachments: Screenshot from 2019-09-16 12-34-12.png, latestjbpmfailed.png, latestjbpmpassed.png, sample.drl
>
>
> In test scenarios (Legacy test scenario) expect section, if we don't edit the default numeric values in expect section then test scenario fails, but if we edit and enter the same value it passes, sometimes we have to type a different value, run the test, then retype 0/0.0 for it to pass.
> The issue is always reproducible.
> h2. Acceptance test
> - Default empty text (/)
> - Default int zero (x), (/) passed in re-review
> - Default double zero (x), (/) passed in re-review
> - Default boolean true (/)
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months