October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-222) when client is scaled down with in-doubt transactions, tx participants on server are resolved with delay

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFWIP-222?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka closed WFWIP-222. ---------------------------------- Resolution: Rejected The behaviour is expected and the transaction resolution is in hands of different component than the recovery. The transactions on the server were started but was not moved to the {{PREPARED}} state. They are in-flight stored only in memory. It's responsibility of the transaction reaper to finish them. It really does so but the reaper is not dependent on the recovery processing. The reaper roll-backs the transactions after transaction timeout is over. If the reaper is not capable to do so for the remote resources (e.g. WildFly goes down meanwhile) then the database/jms/... will roll-back the transaction after the timeout on its own (aka. prepare was not called -> no promise from the remote resource on the processing was done -> transaction timeouts after the timeout is over) > when client is scaled down with in-doubt transactions, tx participants on server are resolved with delay > -------------------------------------------------------------------------------------------------------- > > Key: WFWIP-222 > URL: https://issues.jboss.org/browse/WFWIP-222 > Project: WildFly WIP > Issue Type: Bug > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Blocker > Attachments: tx-server.log > > > this follows up on WFWIP-206 > While testing tx recovery in OpenShift I see that when client is scaled down with in-doubt transactions, tx participants on server are resolved with delay. > 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 > *testTxStatelessClientSecondPrepareJvmHalt* > JVM on client crashes in PREPARE phase of second XA resource on client. Then openshift restarts pod, but pod is immediately scaled down. Transactions on client pod are rollbacked during scale down, but on server they are rollbacked some time later. I'm not sure if it is periodic recovery or tx timeout. > server log with {{com.arjuna}} trace attached. > Feel free to reject if it is expected behavior. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-225) Environment variable to configure the initial metaspace size - need to update standalone.conf to bring CLOUD-3270 changes

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFWIP-225?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated WFWIP-225: ------------------------------ Priority: Minor (was: Major) > Environment variable to configure the initial metaspace size - need to update standalone.conf to bring CLOUD-3270 changes > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-225 > URL: https://issues.jboss.org/browse/WFWIP-225 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Minor > > In CLOUD-3270, some changes were made to be able to override jvm metaspace value but current image docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... doesn't have it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-225) Environment variable to configure the initial metaspace size - need to update standalone.conf to bring CLOUD-3270 changes

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFWIP-225?page=com.atlassian.jira.plugin.... ] Jan Blizňák commented on WFWIP-225: ----------------------------------- Ok after more precise investigation it seems that we are only missing the export at standalone.conf for GC_METASPACE_SIZE, probably here https://github.com/wildfly/wildfly-cekit-modules/blob/master/jboss/contai... The only effect of it missing there is that XX:MetaspaceSize value is read from JAVA_OPTS where the default value for this is {{JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true"}}. This results at tiny difference: with {export GC_METASPACE_SIZE=${GC_METASPACE_SIZE:-96}}: {code:java} -XX:MetaspaceSize=96m {code} without the export: {code:java} -XX:MetaspaceSize=96M {code} It broke our strict tests but this is not a big issue, just somewhat inconsistency that could be enhanced, lowering to minor priority. > Environment variable to configure the initial metaspace size - need to update standalone.conf to bring CLOUD-3270 changes > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-225 > URL: https://issues.jboss.org/browse/WFWIP-225 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Jan Blizňák > Assignee: Jean Francois Denise > Priority: Major > > In CLOUD-3270, some changes were made to be able to override jvm metaspace value but current image docker-registry.upshift.redhat.com/kwills/eap-cd-openshift-rhel8:18.0-EAP... doesn't have it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-192) Sync eap CRD with wildfly CRD

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-192?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFWIP-192: ------------------------------------ [~jmesnil] thank you, yeah that is what I have in mind. However I am lost now. How can I look now at CRD which will be used with eap operator? I mean I have a operator image 1. https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=23795227 gets me here 2. http://pkgs.devel.redhat.com/cgit/containers/jboss-eap-7-operator/commit/... 3. From here and commit message "Syncinf with hex" gets me here 4. https://github.com/jbossas/eap-operator-packaging/commit/0344c3c4e5572d9f... But in this repo there is no crd anymore. I am missing something. Or is there way to look into image itself. I cant run operator image in plain docker. > Sync eap CRD with wildfly CRD > ----------------------------- > > Key: WFWIP-192 > URL: https://issues.jboss.org/browse/WFWIP-192 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > Labels: operator > > Comparing wildfly and eap CRD revealed differences > {code} > wget https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/... -O wildfly_operator_crd > wget https://raw.githubusercontent.com/jbossas/eap-operator-packaging/prototyp... -O eap_operator_crd > diff wildfly_operator_crd eap_operator_crd > {code} > {code} > 36,37d35 > < disableHTTPRoute: > < type: boolean > 50,53d47 > < sessionAffinity: > < description: SessionAffinity defines if connections from the same client > < ip are passed to the same WildFlyServer instance/pod each time > < type: boolean > 79,82d72 > < hosts: > < items: > < type: string > < type: array > 94a85,86 > > required: > > - pods > {code} > Please sync so we can test against. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-223) disableHTTPRoute = true in runtime does not clean CR.status.hosts

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-223?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-223: ----------------------------------- fixed upstream in https://github.com/wildfly/wildfly-operator/pull/95 > disableHTTPRoute = true in runtime does not clean CR.status.hosts > ----------------------------------------------------------------- > > Key: WFWIP-223 > URL: https://issues.jboss.org/browse/WFWIP-223 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Reproducer: > # create CR > {code} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > generation: 1 > name: eap-cd > namespace: default > spec: > applicationImage: >- > brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4 > size: 1 > disableHTTPRoute: false > {code} > # Edit CR with disableHTTPRoute: true. I would expect Route object will be deleted. > {code} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > generation: 1 > name: eap-cd > namespace: default > spec: > applicationImage: >- > brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/jboss-eap-7-tech-preview/eap-cd-openshift-rhel8:17.0-4 > size: 1 > disableHTTPRoute: true > {code} > # Route object eap-cd is not deleted but status.hosts is still filled > {code:yaml} > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > creationTimestamp: '2019-10-01T17:20:34Z' > generation: 2 > name: eap-cd > namespace: mchoma > resourceVersion: '629943' > selfLink: /apis/wildfly.org/v1alpha1/namespaces/mchoma/wildflyservers/eap-cd > uid: c7535f3f-e46f-11e9-b4ad-02e6008f3048 > spec: > applicationImage: >- > image-registry.openshift-image-registry.svc:5000/eapcd-suite-builds/eap-cd-openshift-rhel8:17.0-4 > disableHTTPRoute: false > env: [] > envFrom: [] > replicas: 1 > status: > hosts: > - >- > eap-cd-route-mchoma.apps.eap-qe-cluster105.eap-qe-cluster105.fw.rhcloud.com > pods: > - name: eap-cd-0 > podIP: 10.131.0.246 > state: ACTIVE > replicas: 1 > scalingdownPods: 0 > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-196) Operator missing volumes from secrets and config maps

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-196?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-196: ----------------------------------- Fixed in upstream in https://github.com/wildfly/wildfly-operator/pull/93 and https://github.com/wildfly/wildfly-operator/pull/96 > Operator missing volumes from secrets and config maps > ------------------------------------------------------ > > Key: WFWIP-196 > URL: https://issues.jboss.org/browse/WFWIP-196 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Operator is missing way of configuring volumes from secets and config maps > - secrets > -- configuring keystore in ssl > -- configuring keystore for jgroups ASYNC encryption in jgroups (DNS_PING, KUBE_PING)) > - config map > -- Microprofile Config and reading properties from ConfigMap > -- running custom CLI script from config map (EAP7-892) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-218) server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited

by Tomasz Adamski (Jira)

[ https://issues.jboss.org/browse/WFWIP-218?page=com.atlassian.jira.plugin.... ] Tomasz Adamski commented on WFWIP-218: -------------------------------------- The problem is this issue is as follows: 1. transaction log on on server is cleared correctly 2. server's stateful-set is scaled down (pod referenced by client disappears) 3. client checks in-doubt resource but cannot connect to the server In OpenShift environment with wildfly-operator, we can be sure that if the server's stateful-set was scaled down correctly then it logs must have been cleared. As a result, client records can be discarded. This is not true in general (bare-metal) where the server may go down and still have records in the log. in the context of above I would propose: 1. workaround - provide the customer with a manual procedure (if connection error to the server's pod occurs but the pod was scaled down correctly remove log records). This is not elegant, but this is an emergency and I don't expect it to be used often. 2. solution - if operating within OpenShift client cannot connect to one of the server's pods, client checks with OpenShift API whether the server's pod was scaled down. If it was, the record can be discarded. I would suggest downgrading this issue with provided workaround and later work on the target solution (which would require OpenShift integration and has to be researched). > 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-187) Changes to PVC are not reflected in Operator

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-187?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-187: ----------------------------------- Resizing a in-use PVC requires to enable the feature https://kubernetes.io/docs/concepts/storage/persistent-volumes/#resizing-... I don't think there is anything else to do on the operator side about it. > Changes to PVC are not reflected in Operator > -------------------------------------------- > > Key: WFWIP-187 > URL: https://issues.jboss.org/browse/WFWIP-187 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > Labels: operator > > Any chnages (adding, removing or updating) made to PVC after WildFlyServer CR was created are not reflected in underlying PVC kubernetes object. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12595) Upgrade IronJacamar to 1.4.18.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFLY-12595?page=com.atlassian.jira.plugin... ] Ivo Studensky reassigned WFLY-12595: ------------------------------------ Assignee: Ivo Studensky (was: Stefano Maestri) > Upgrade IronJacamar to 1.4.18.Final > ----------------------------------- > > Key: WFLY-12595 > URL: https://issues.jboss.org/browse/WFLY-12595 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-224) Redundant template eap-cd-chained-build-s2i.json

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-224?page=com.atlassian.jira.plugin.... ] Jean Francois Denise resolved WFWIP-224. ---------------------------------------- Resolution: Done Template remove from https://github.com/wildfly/temp-openshift-image > Redundant template eap-cd-chained-build-s2i.json > ------------------------------------------------ > > Key: WFWIP-224 > URL: https://issues.jboss.org/browse/WFWIP-224 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Nikoleta Ziakova > Assignee: Jean Francois Denise > Priority: Major > > The [chained-build|https://github.com/wildfly/temp-openshift-image/blob/EAP7-1...] template was added with old feature design when chained build was not possible to be added to the existing templates. Now the existing templates contain chained build so this new template has become redundant. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019