January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4899) DMN demo extended builtin function for runtime

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4899?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-4899: ----------------------------------- Summary: DMN demo extended builtin function for runtime (was: DMN extended builtin function for runtime) > DMN demo extended builtin function for runtime > ---------------------------------------------- > > Key: DROOLS-4899 > URL: https://issues.redhat.com/browse/DROOLS-4899 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4899) DMN extended builtin function for runtime

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4899?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-4899: ----------------------------------- Issue Type: Task (was: Feature Request) > DMN extended builtin function for runtime > ----------------------------------------- > > Key: DROOLS-4899 > URL: https://issues.redhat.com/browse/DROOLS-4899 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12923) EjbJaccConfigurator has unused methodIdentifier after WFLY-12794 changes

by Rostislav Svoboda (Jira)

Rostislav Svoboda created WFLY-12923: ---------------------------------------- Summary: EjbJaccConfigurator has unused methodIdentifier after WFLY-12794 changes Key: WFLY-12923 URL: https://issues.redhat.com/browse/WFLY-12923 Project: WildFly Issue Type: Bug Components: EJB Reporter: Rostislav Svoboda Assignee: Rostislav Svoboda EjbJaccConfigurator has unused {{methodIdentifier}} and few unnecessary {{MethodIdentifier.getIdentifierForMethod}} calls after WFLY-12794 changes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12826) Switch to GAV-based locations for feature-pack dependencies

by Oleksiy Lubyanskyy (Jira)

[ https://issues.redhat.com/browse/WFLY-12826?page=com.atlassian.jira.plugi... ] Oleksiy Lubyanskyy updated WFLY-12826: -------------------------------------- Description: Currently feature-pack dependencies are using FPL format to point to the dependency feature-packs. Galleon 4.2.1.Final and WFGP 4.2.2.Final support generation of the feature-pack dependency locations in GAV format. As a consequence, provisioning in offline mode does not require all the transitive feature-pack configs in the provision goal configuration. > Switch to GAV-based locations for feature-pack dependencies > ----------------------------------------------------------- > > Key: WFLY-12826 > URL: https://issues.redhat.com/browse/WFLY-12826 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Jean Francois Denise > Assignee: Oleksiy Lubyanskyy > Priority: Major > > Currently feature-pack dependencies are using FPL format to point to the dependency feature-packs. Galleon 4.2.1.Final and WFGP 4.2.2.Final support generation of the feature-pack dependency locations in GAV format. As a consequence, provisioning in offline mode does not require all the transitive feature-pack configs in the provision goal configuration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12826) Switch to GAV-based locations for feature-pack dependencies

by Oleksiy Lubyanskyy (Jira)

[ https://issues.redhat.com/browse/WFLY-12826?page=com.atlassian.jira.plugi... ] Oleksiy Lubyanskyy updated WFLY-12826: -------------------------------------- Summary: Switch to GAV-based locations for feature-pack dependencies (was: Upgrade galleon to 4.2.1.Final, galleon-plugins to 4.2.2.Final) > Switch to GAV-based locations for feature-pack dependencies > ----------------------------------------------------------- > > Key: WFLY-12826 > URL: https://issues.redhat.com/browse/WFLY-12826 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Jean Francois Denise > Assignee: Oleksiy Lubyanskyy > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

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

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-12922?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka updated WFLY-12922: ------------------------------------ Affects Version/s: 18.0.0.Final > server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-12922 > URL: https://issues.redhat.com/browse/WFLY-12922 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Affects Versions: 18.0.0.Final > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 19.0.0.Beta1 > > > 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, 4 months

1
0
0 / 0

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

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-12922?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka resolved WFLY-12922. ------------------------------------- Resolution: Done Caused by WFTC-77, resolved by component upgrade WFLY-12910 > server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-12922 > URL: https://issues.redhat.com/browse/WFLY-12922 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Affects Versions: 18.0.0.Final > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 19.0.0.Beta1 > > > 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, 4 months

1
0
0 / 0

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

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-12922?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka updated WFLY-12922: ------------------------------------ Fix Version/s: 19.0.0.Beta1 > server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-12922 > URL: https://issues.redhat.com/browse/WFLY-12922 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Affects Versions: 18.0.0.Final > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 19.0.0.Beta1 > > > 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, 4 months

1
0
0 / 0

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

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-12922?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka moved WFWIP-218 to WFLY-12922: ----------------------------------------------- Project: WildFly (was: WildFly WIP) Key: WFLY-12922 (was: WFWIP-218) Component/s: EJB Transactions (was: OpenShift) > server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-12922 > URL: https://issues.redhat.com/browse/WFLY-12922 > Project: WildFly > Issue Type: Bug > Components: EJB, Transactions > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Major > > 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, 4 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 Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFWIP-218?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka commented on WFWIP-218: ---------------------------------------- [~brian.stansberry] that's right. I'm moving this to WFLY. It sounds to me as the correct place. > 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.redhat.com/browse/WFWIP-218 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Major > > 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, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2020