[
https://issues.jboss.org/browse/WFWIP-218?page=com.atlassian.jira.plugin....
]
Martin Simka edited comment on WFWIP-218 at 10/1/19 10:06 AM:
--------------------------------------------------------------
[~ochaloup] sorry for multiple edits and possible spam. I wanted to report multiple issues
in single jira, but I changed my mind later.
was (Author: simkam):
[~ochaloup] so for multiple edits and possible spam. I wanted to report multiple issues in
single jira, but I changed my mind later.
server scale down keeps data in client's data/ejb-xa-recovery and
transactions on client aren't commited
--------------------------------------------------------------------------------------------------------
Key: WFWIP-218
URL:
https://issues.jboss.org/browse/WFWIP-218
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Martin Simka
Assignee: Ondrej Chaloupka
Priority: Blocker
this follows up on WFWIP-206
While testing tx recovery in OpenShift I see that scale down of pod that has transaction
in-doubt on it isn't successful
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
*testTxStatelessServerSecondCommitThrowRmFail*
ejb server XA resource 2 fails with {{XAException(XAException.XAER_RMFAIL)}}
Then the test calls scale down (size from 1 to 0) on tx-server pod. Server scale down
completes but sometimes there some records left in
{{<JBOSS_HOME>/standalone/data/ejb-xa-recovery}} on tx-client and transactions on
client aren't commited.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)