October 2019 - jboss-jira - Jboss List Archives

[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: Stefano Maestri (was: Ivo Studensky) > 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: Stefano Maestri > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4596) [DMN Editor] Text format property has no any affect to Text Annotation

by Lubomír Terifaj (Jira)

[ https://issues.jboss.org/browse/DROOLS-4596?page=com.atlassian.jira.plugi... ] Lubomír Terifaj updated DROOLS-4596: ------------------------------------ Affects Version/s: 7.27.0.Final > [DMN Editor] Text format property has no any affect to Text Annotation > ---------------------------------------------------------------------- > > Key: DROOLS-4596 > URL: https://issues.jboss.org/browse/DROOLS-4596 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.27.0.Final > Reporter: Lubomír Terifaj > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > "Text format" property has no any affect to Text Annotation. > It is not clear for a user, what values can be input there. > The property is missing a tooltip or dropdown menu for possible options. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

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

by Ivo Studensky (Jira)

Ivo Studensky created WFLY-12618: ------------------------------------ Summary: Upgrade IronJacamar to 1.4.18.Final Key: WFLY-12618 URL: https://issues.jboss.org/browse/WFLY-12618 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Ivo Studensky Assignee: Ivo Studensky -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4596) [DMN Editor] Text format property has no any affect to Text Annotation

by Lubomír Terifaj (Jira)

[ https://issues.jboss.org/browse/DROOLS-4596?page=com.atlassian.jira.plugi... ] Lubomír Terifaj updated DROOLS-4596: ------------------------------------ Steps to Reproduce: # Create project in Business Central # Create DMN # Drag and drop Text Annotation to the canvas from the palette # Change *Text format* property value in Diagram properties to "text/html" was: # Create project in Business Central # Create DMN # Drag and drop Text Annotation to the canvas from the palette # Change *Text format* property value to text/html > [DMN Editor] Text format property has no any affect to Text Annotation > ---------------------------------------------------------------------- > > Key: DROOLS-4596 > URL: https://issues.jboss.org/browse/DROOLS-4596 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Lubomír Terifaj > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > "Text format" property has no any affect to Text Annotation. > It is not clear for a user, what values can be input there. > The property is missing a tooltip or dropdown menu for possible options. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

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 Martin Simka (Jira)

[ https://issues.jboss.org/browse/WFWIP-218?page=com.atlassian.jira.plugin.... ] Martin Simka commented on WFWIP-218: ------------------------------------ [~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)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4596) [DMN Editor] Text format property has no any affect to Text Annotation

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4596?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4596: -------------------------------- Tester: Jozef Marko > [DMN Editor] Text format property has no any affect to Text Annotation > ---------------------------------------------------------------------- > > Key: DROOLS-4596 > URL: https://issues.jboss.org/browse/DROOLS-4596 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Lubomír Terifaj > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > "Text format" property has no any affect to Text Annotation. > It is not clear for a user, what values can be input there. > The property is missing a tooltip or dropdown menu for possible options. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

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 Martin Simka (Jira)

[ https://issues.jboss.org/browse/WFWIP-218?page=com.atlassian.jira.plugin.... ] Martin Simka updated WFWIP-218: ------------------------------- Description: 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. was: 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 *Scenario 1 - 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 aren't commited. *Scenario 2 - EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondPrepareJvmHalt* The tx-server in JVM crashes in XA resource 2 prepare phase. Openshift then restarts server pod but it is immediately scaled down. Server scale down completes but sometimes there some records left in {{<JBOSS_HOME>/standalone/data/ejb-xa-recovery}} on tx-client. {noformat} /opt/eap/standalone/data/ejb-xa-recovery/20005_00000000000000000000ffffac11000aa3c95b225d932d5e0000001374782d636c69656e742d30_00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 {noformat} > 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)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4595) [DMN Editor] Changing Background colour of Text annotation does not affect the node on the canvas

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4595?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4595: -------------------------------- Tester: Jozef Marko > [DMN Editor] Changing Background colour of Text annotation does not affect the node on the canvas > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-4595 > URL: https://issues.jboss.org/browse/DROOLS-4595 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.27.0.Final > Reporter: Lubomír Terifaj > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Changing Background colour of Text annotation in Diagram properties panel does not affect the node on the canvas. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

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 Martin Simka (Jira)

[ https://issues.jboss.org/browse/WFWIP-218?page=com.atlassian.jira.plugin.... ] Martin Simka updated WFWIP-218: ------------------------------- Summary: server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited (was: server scale down sometimes keeps data in client's data/ejb-xa-recovery) > 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 > *Scenario 1 - 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 aren't commited. > *Scenario 2 - EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondPrepareJvmHalt* > The tx-server in JVM crashes in XA resource 2 prepare phase. Openshift then restarts server pod but it is immediately scaled down. Server scale down completes but sometimes there some records left in {{<JBOSS_HOME>/standalone/data/ejb-xa-recovery}} on tx-client. > {noformat} > /opt/eap/standalone/data/ejb-xa-recovery/20005_00000000000000000000ffffac11000aa3c95b225d932d5e0000001374782d636c69656e742d30_00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

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 Martin Simka (Jira)

[ https://issues.jboss.org/browse/WFWIP-218?page=com.atlassian.jira.plugin.... ] Martin Simka updated WFWIP-218: ------------------------------- 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 mvn clean test -P72 -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondCommitThrowRmFail -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.upshift.redhat.com/kwills/eap-cd-openshi... 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=quay.io/ochaloup/wildfly-operator:20190930 xtf.operator.resources.context= # specify correct path oc binary xtf.openshift.binary.path=<oc_binary_path> {code} 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 mvn clean test -P72 -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessClientSecondCommitThrowRmFail -Dconsole-log-level=DEBUG #or mvn clean test -P72 -Dtest=EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondCommitThrowRmFail -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.upshift.redhat.com/kwills/eap-cd-openshi... 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=quay.io/ochaloup/wildfly-operator:20190930 xtf.operator.resources.context= # specify correct path oc binary xtf.openshift.binary.path=<oc_binary_path> {code} > 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 > *Scenario 1 - 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 aren't commited. > *Scenario 2 - EjbTxnRemotingScaleDownTest#testTxStatelessServerSecondPrepareJvmHalt* > The tx-server in JVM crashes in XA resource 2 prepare phase. Openshift then restarts server pod but it is immediately scaled down. Server scale down completes but sometimes there some records left in {{<JBOSS_HOME>/standalone/data/ejb-xa-recovery}} on tx-client. > {noformat} > /opt/eap/standalone/data/ejb-xa-recovery/20005_00000000000000000000ffffac11000aa3c95b225d932d5e0000001374782d636c69656e742d30_00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019