[JBoss JIRA] (WFLY-13516) Create integration test scenario for transaction recovery failure of ejb remoting JBEAP-19408
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/WFLY-13516?page=com.atlassian.jira.plugi... ]
Ondrej Chaloupka updated WFLY-13516:
------------------------------------
Comment: was deleted
(was: The PR was closed as there is need first to have change of the Narayana filter priority to something else than the {USER} (https://github.com/jbosstm/narayana/blob/5.10.4.Final/rts/at/bridge/src/m...).
The issue is tracked at https://issues.redhat.com/browse/JBTM-3321.
There is needed the Narayana codebase to be changed and the component upgrade to be placed in.)
> Create integration test scenario for transaction recovery failure of ejb remoting JBEAP-19408
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-13516
> URL: https://issues.redhat.com/browse/WFLY-13516
> Project: WildFly
> Issue Type: Task
> Components: Test Suite, Transactions
> Affects Versions: 20.0.0.Beta1
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Major
>
> There was found a transaction recovery failure scenario which caused regression being filled as https://issues.redhat.com/browse/JBEAP-19408.
> The issue JBEAP-19408 causes that in case of WildFly communicating over EJB remoting to other WildFly and when there is a failure then there could be left prepared resources on the other WildFly which are never rolled-back.
> E.g. in case of database it means locked rows which could not be manipulated with until administrator comes and manually unlock them.
> The scenario which was this hit with and which should be simulated in the WildFly testsuite:
> * server A starts the transactions
> * transaction at server A enlists the an XAResource related to a future interation with server B (At server A, WFTC enlists an "ejb client resource" related to a future interaction with B)
> * server A makes the remote EJB call to server B where transaction is propagated
> * server A asks server B to prepare
> * server A creates a "ejb client resource" XAResourceRegistry file system record
> * server B prepares
> * server A crashes before it writes a transaction log
> * server A restarts (transaction recovery cycle starts)
> * server A can see no record of the transactions in the object store
> * server A uses the standard orphan detection processing
> * server A calls XAResource.recover(TMSTARTRSCAN) on "ejb client resource". It returns prepared XAResources from server B as there is XAResourceRegistry file system record on server A (related to a future interation with server B)
> * server A calls XAResource.recover(TMENDRSCAN), the recovery cycle finishes
> * server A calls another round of recovery wwith XAResource.recover(TMSTARTRSCAN) and there is the XAResourceRegistry and orphan detection rolls-back the subtransaction resources on server B
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13283) WFLYTX0001: Unable to roll back active transaction exception thrown from RTS inbound bridge
by Ondrej Chaloupka (Jira)
[ https://issues.redhat.com/browse/WFLY-13283?page=com.atlassian.jira.plugi... ]
Ondrej Chaloupka commented on WFLY-13283:
-----------------------------------------
The PR was closed as there is need first to have change of the Narayana filter priority to something else than the
{{USER}}
(https://github.com/jbosstm/narayana/blob/5.10.4.Final/rts/at/bridge/src/m...).
The issue is tracked at https://issues.redhat.com/browse/JBTM-3321.
There is needed the Narayana codebase to be changed and the component upgrade to be placed in.
> WFLYTX0001: Unable to roll back active transaction exception thrown from RTS inbound bridge
> -------------------------------------------------------------------------------------------
>
> Key: WFLY-13283
> URL: https://issues.redhat.com/browse/WFLY-13283
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 19.0.0.Final
> Reporter: Ondrej Chaloupka
> Assignee: Ondrej Chaloupka
> Priority: Major
>
> This is an integration problem of REST-AT transaction inbound bridge with WFTC client.
> It's in the same way as there was for XTS txnbridge https://issues.redhat.com/browse/WFLY-9455
> The trouble is that REST-AT bridge implementation works with Narayana transaction manager. All the calls which go to the {{javax.transaction.TransactionManager}} is integrated to Narayana transaction manager backed by {{AtomicActions}} etc.
> But WildFly is fully integrated with WFTC TransactionManager as a wrapper over the Narayana one.
> The inbound bridge manages merging the REST-AT context with JTA context. On incoming REST call the InboundBridge is started and resume a transaction:
> https://github.com/jbosstm/narayana/blob/5.10.4.Final/rts/at/bridge/src/m...
> It's implemented by `ContainerRequestFilter` which is invoked on incoming call before the method is executed:
> https://github.com/jbosstm/narayana/blob/5.10.4.Final/rts/at/bridge/src/m...
> After execution is needed the transaction would be suspended again. In current time it happens for Narayana transaction but not for the WFTC transaction
> Narayana `ContainerResponseFilter` handling:
> * https://github.com/jbosstm/narayana/blob/5.10.4.Final/rts/at/bridge/src/m...
> * https://github.com/jbosstm/narayana/blob/5.10.4.Final/rts/at/bridge/src/m...
> (btw. the same is about handling of JAX-WS XTS txnbridge: https://github.com/jbosstm/narayana/blob/5.10.4.Final/txbridge/src/main/j...)
> Now the issue is that WFLY WFTC Transaction is not suspended on the outbound. It means the EJB still think there is an active transaction. But it's only the WFTC wrapper which wraps an empty Narayana transaction. All the real business work was done, the real transaction was suspended.
> When the call leaves the EJB there is a action which ensures no transaction leaves the EJB method (https://github.com/wildfly/wildfly/blob/19.0.0.Final/transactions/src/mai...). When there is some active context it's rolled-back. So WFTC Transaction rollback is called but as the WFTC holds an empty wrapper the rollback finishes with exception server log message[1].
> [1]
> {quote}
> ERROR [org.jboss.as.txn] (default task-1) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 0
> ERROR [org.jboss.as.txn] (default task-1) WFLYTX0001: Unable to roll back active transaction: javax.transaction.SystemException: WFTXN0032: Rollback not allowed on imported transaction
> at org.wildfly.transaction.client.LocalTransaction.rollbackAndDissociate(LocalTransaction.java:105)
> at org.wildfly.transaction.client.ContextTransactionManager.rollback(ContextTransactionManager.java:83)
> at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137)
> at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1543)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:249)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:78)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:99)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:376)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748)
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13514) Huge memory leak in WildFly
by Matěj Novotný (Jira)
[ https://issues.redhat.com/browse/WFLY-13514?page=com.atlassian.jira.plugi... ]
Matěj Novotný commented on WFLY-13514:
--------------------------------------
[~flavia.rainone] [~konbk] Yeah, that's the issue. Just verified it by reverting that commit, then building undertow, wfly core, wfly itself and testing the reproducer.
> Huge memory leak in WildFly
> ---------------------------
>
> Key: WFLY-13514
> URL: https://issues.redhat.com/browse/WFLY-13514
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JSF, Web (Undertow)
> Affects Versions: 18.0.1.Final, 19.1.0.Final, 20.0.0.Beta1
> Reporter: Konrad Bak
> Assignee: Flavia Rainone
> Priority: Critical
>
> https://github.com/konbk/bug-report-wildfly-oome
> The project shows a huge memory leak introduced in recent WildFly versions that can crash a real-world Java EE application in a matter of hours.
> When a JSF page contains any component bound to page variable, all CDI beans (regardless of scope) used on that page stay in memory.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5333) Allow to customize rule names in guided decision table editor
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5333?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5333:
--------------------------------
Description:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected
- Guided Rules are not affected
- bxms-qe-tests internal are updated
- Firefox
- Chrome
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
- Help in the changed wizard page
was:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected
- Guided Rules are not affected
- bxms-qe-tests internal are updated
- Firefox
- Chrome
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
> Allow to customize rule names in guided decision table editor
> -------------------------------------------------------------
>
> Key: DROOLS-5333
> URL: https://issues.redhat.com/browse/DROOLS-5333
> Project: Drools
> Issue Type: Feature Request
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
> h3. Check to be done during manual review
> - Guided Rule Templates are not affected
> - Guided Rules are not affected
> - bxms-qe-tests internal are updated
> - Firefox
> - Chrome
> - Create new table, Put value, Save and reopen, Remove value, Save and reopen
> - Open existing table (Pricing loans)
> - Create scesim file to check execution is not affetced
> - GDST to XLS conversion
> - Help in the changed wizard page
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5333) Allow to customize rule names in guided decision table editor
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5333?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5333:
--------------------------------
Description:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected
- Guided Rules are not affected
- bxms-qe-tests internal are updated
- Firefox
- Chrome
- Create new table, Put value, Save and reopen, Remove value, Save and reopen
- Open existing table (Pricing loans)
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
was:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected
- Guided Rules are not affected
- bxms-qe-tests internal are updated
- Firefox
- Chrome
- Put value, Save and reopen
- Remove value, Save and reopen
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
> Allow to customize rule names in guided decision table editor
> -------------------------------------------------------------
>
> Key: DROOLS-5333
> URL: https://issues.redhat.com/browse/DROOLS-5333
> Project: Drools
> Issue Type: Feature Request
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
> h3. Check to be done during manual review
> - Guided Rule Templates are not affected
> - Guided Rules are not affected
> - bxms-qe-tests internal are updated
> - Firefox
> - Chrome
> - Create new table, Put value, Save and reopen, Remove value, Save and reopen
> - Open existing table (Pricing loans)
> - Create scesim file to check execution is not affetced
> - GDST to XLS conversion
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5333) Allow to customize rule names in guided decision table editor
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5333?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5333:
--------------------------------
Description:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected
- Guided Rules are not affected
- bxms-qe-tests internal are updated
- Firefox
- Chrome
- Put value, Save and reopen
- Remove value, Save and reopen
- Create scesim file to check execution is not affetced
- GDST to XLS conversion
was:
Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
h3. Check to be done during manual review
- Guided Rule Templates are not affected
- Guided Rules are not affected
- bxms-qe-tests internal are updated
- Firefox
- Chrome
- Put value, Save and reopen
- Remove value, Save and reopen
- Create scesim file to check execution is not affetced
> Allow to customize rule names in guided decision table editor
> -------------------------------------------------------------
>
> Key: DROOLS-5333
> URL: https://issues.redhat.com/browse/DROOLS-5333
> Project: Drools
> Issue Type: Feature Request
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> Add a column into the GDST where you can set the rule name for the rule that is generated from that row.
> h3. Check to be done during manual review
> - Guided Rule Templates are not affected
> - Guided Rules are not affected
> - bxms-qe-tests internal are updated
> - Firefox
> - Chrome
> - Put value, Save and reopen
> - Remove value, Save and reopen
> - Create scesim file to check execution is not affetced
> - GDST to XLS conversion
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5385) Drools Workbench Scenario Simulation Editor - Kogito Client module compilation error in Jenkins
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5385?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5385:
--------------------------------
Affects Version/s: 7.39.0.Final
> Drools Workbench Scenario Simulation Editor - Kogito Client module compilation error in Jenkins
> ------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5385
> URL: https://issues.redhat.com/browse/DROOLS-5385
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.39.0.Final
> Reporter: nibu baby
> Assignee: Mario Fusco
> Priority: Major
> Labels: drools-tools
>
> Drools Workbench Scenario Simulation Editor - Kogito Client module compilation fails with following error in Jenkins master nightly base line jobs
> {code:java}
> @ drools-wb-scenario-simulation-editor-kogito-client ---
> 16:40:14 [INFO] Compiling 11 source files to /home/hudson/hudson_workspace/workspace/BxMS/RHPAM-master-nightly/baseline/blessed-community-tests-bcentral-baseline/tests/s/drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-client/target/test-classes
> 16:40:15 [INFO] -------------------------------------------------------------
> 16:40:15 [ERROR] COMPILATION ERROR :
> 16:40:15 [INFO] -------------------------------------------------------------
> 16:40:15 [ERROR] /home/hudson/hudson_workspace/workspace/BxMS/RHPAM-master-nightly/baseline/blessed-community-tests-bcentral-baseline/tests/s/drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-client/src/test/java/org/drools/workbench/screens/scenariosimulation/kogito/client/editor/ScenarioSimulationEditorKogitoWrapperTest.java:[24,78] package org.drools.workbench.scenariosimulation.kogito.marshaller.js.callbacks does not exist
> 16:40:15 [ERROR] /home/hudson/hudson_workspace/workspace/BxMS/RHPAM-master-nightly/baseline/blessed-community-tests-bcentral-baseline/tests/s/drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-client/src/test/java/org/drools/workbench/screens/scenariosimulation/kogito/client/converters/JSInteropApiConverterTest.java:[33,74] package org.drools.workbench.scenariosimulation.kogito.marshaller.js.model does not exist
> 16:40:15 [ERROR] /home/hudson/hudson_workspace/workspace/BxMS/RHPAM-master-nightly/baseline/blessed-community-tests-bcentral-baseline/tests/s/drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-client/src/test/java/org/drools/workbench/screens/scenariosimulation/kogito/client/converters/JSInteropApiConverterTest.java:[34,74] package org.drools.workbench.scenariosimulation.kogito.marshaller.js.model does not exist
> 16:40:15 [ERROR] /home/hudson/hudson_workspace/workspace/BxMS/RHPAM-master-nightly/baseline/blessed-community-tests-bcentral-baseline/tests/s/drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-client/src/test/java/org/drools/workbench/screens/scenariosimulation/kogito/client/converters/JSInteropApiConverterTest.java:[35,74] package org.drools.workbench.scenariosimulation.kogito.marshaller.js.model does not exist
> 16:40:15 [ERROR] /home/hudson/hudson_workspace/workspace/BxMS/RHPAM-master-nightly/baseline/blessed-community-tests-bcentral-baseline/tests/s/drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-client/src/test/java/org/drools/workbench/screens/scenariosimulation/kogito/client/converters/JSInteropApiConverterTest.java:[36,74] package org.drools.workbench.scenariosimulation.kogito.marshaller.js.model does not exist
> 16:40:15 [ERROR] /home/hudson/hudson_workspace/workspace/BxMS/RHPAM-master-nightly/baseline/blessed-community-tests-bcentral-baseline/tests/s/drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-client/src/test/java/org/drools/workbench/screens/scenariosimulation/kogito/client/converters/JSInteropApiConverterTest.java:[37,74] package org.drools.workbench.scenariosimulation.kogito.marshaller.js.model does not exist
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month