[
https://issues.jboss.org/browse/WFWIP-205?page=com.atlassian.jira.plugin....
]
Martin Simka updated WFWIP-205:
-------------------------------
Steps to Reproduce:
it can be reproduced using test:
{code}
git clone git@gitlab.mw.lab.eng.bos.redhat.com:msimka/openshift-eap-tests.git
cd openshift-eap-tests.git
git checkout EAP7-1192_scaledown
# create file test.properties
cd test-eap
mvn clean test -P72
# run multiple times
-Dtest=EjbTxnRemotingCrashRecTest#testTxStatelessServerSecondCommitJvmHalt
-Dcheckstyle.skip -Dconsole-log-level=DEBUG
{code}
test.properties
{code}
xtf.openshift.url=https://master.all-in-one-msimka-002.dynamic.xpaas:8443
xtf.openshift.namespace=wip-namespace
xtf.bm.namespace=wip-builds-namespace
xtf.eap.72.image=docker-registry.engineering.redhat.com/ochaloup/wildfly1...
xtf.eap.72.properties.eap.imagestream.name=jboss-eap73-openshift
xtf.eap.72.version=7.2.0.GA
xtf.eap.properties.location=/opt/eap
xtf.eap.72.templates.repo=git://github.com/jboss-container-images/jboss-e...
xtf.eap.72.templates.branch=eap72,v7.3.0.GA
xtf.maven.proxy.url=http://maven.all-in-one-043.dynamic.xpaas/nexus/content/groups/public/
# this might be needed if oc login command fails, see test suite logs
#xtf.openshift.binary.path=/home/msimka/.minishift/cache/oc/v3.11.0/linux/oc
xtf.operator.image=docker-registry.engineering.redhat.com/jbossqe-eap/wil...
# specify correct path oc binary
xtf.openshift.binary.path=<oc_binary_path>
{code}
For {{master.all-in-one-msimka-002.dynamic.xpaas}} to work DNS 10.0.144.45 needs to be
used.
was:
it can be reproduced using test:
{code}
git clone git@gitlab.mw.lab.eng.bos.redhat.com:msimka/openshift-eap-tests.git
cd openshift-eap-tests.git
git checkout EAP7-1192_scaledown
# create file test.properties
cd test-eap
mvn clean test -P72
# run multiple times
-Dtest=StatefulSetCrashRecTest#testTxStatelessServerSecondCommitJvmHalt -Dcheckstyle.skip
-Dconsole-log-level=DEBUG
{code}
test.properties
{code}
xtf.openshift.url=https://master.all-in-one-msimka-002.dynamic.xpaas:8443
xtf.openshift.namespace=wip-namespace
xtf.bm.namespace=wip-builds-namespace
xtf.eap.72.image=docker-registry.engineering.redhat.com/ochaloup/wildfly1...
xtf.eap.72.properties.eap.imagestream.name=jboss-eap73-openshift
xtf.eap.72.version=7.2.0.GA
xtf.eap.properties.location=/opt/eap
xtf.eap.72.templates.repo=git://github.com/jboss-container-images/jboss-e...
xtf.eap.72.templates.branch=eap72,v7.3.0.GA
xtf.maven.proxy.url=http://maven.all-in-one-043.dynamic.xpaas/nexus/content/groups/public/
# this might be needed if oc login command fails, see test suite logs
#xtf.openshift.binary.path=/home/msimka/.minishift/cache/oc/v3.11.0/linux/oc
xtf.operator.image=docker-registry.engineering.redhat.com/jbossqe-eap/wil...
# specify correct path oc binary
xtf.openshift.binary.path=<oc_binary_path>
{code}
For {{master.all-in-one-msimka-002.dynamic.xpaas}} to work DNS 10.0.144.45 needs to be
used.
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)