March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10150) EJB race condition can cause client to be in awaitResponse while server is done

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10150?page=com.atlassian.jira.plugin... ] Lin Gao reassigned WFLY-10150: ------------------------------ Assignee: David Lloyd > EJB race condition can cause client to be in awaitResponse while server is done > ------------------------------------------------------------------------------- > > Key: WFLY-10150 > URL: https://issues.jboss.org/browse/WFLY-10150 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Lin Gao > Assignee: David Lloyd > Labels: downstream_dependency > > With a client jboss server1 that has a client servlet that invokes a remote EJB on jboss server2 configured using server to server config in the standalone.xml/domain.xml outbound remoting connection, the client side can get stuck in awaitResponse while the server side has finished processing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10150) EJB race condition can cause client to be in awaitResponse while server is done

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10150?page=com.atlassian.jira.plugin... ] Lin Gao updated WFLY-10150: --------------------------- Labels: downstream_dependency (was: ) > EJB race condition can cause client to be in awaitResponse while server is done > ------------------------------------------------------------------------------- > > Key: WFLY-10150 > URL: https://issues.jboss.org/browse/WFLY-10150 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Lin Gao > Assignee: David Lloyd > Labels: downstream_dependency > > With a client jboss server1 that has a client servlet that invokes a remote EJB on jboss server2 configured using server to server config in the standalone.xml/domain.xml outbound remoting connection, the client side can get stuck in awaitResponse while the server side has finished processing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10150) EJB race condition can cause client to be in awaitResponse while server is done

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10150?page=com.atlassian.jira.plugin... ] Lin Gao reassigned WFLY-10150: ------------------------------ Assignee: (was: JBoss SET) > EJB race condition can cause client to be in awaitResponse while server is done > ------------------------------------------------------------------------------- > > Key: WFLY-10150 > URL: https://issues.jboss.org/browse/WFLY-10150 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Lin Gao > > With a client jboss server1 that has a client servlet that invokes a remote EJB on jboss server2 configured using server to server config in the standalone.xml/domain.xml outbound remoting connection, the client side can get stuck in awaitResponse while the server side has finished processing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10150) EJB race condition can cause client to be in awaitResponse while server is done

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10150?page=com.atlassian.jira.plugin... ] Lin Gao updated WFLY-10150: --------------------------- Forum Reference: (was: http://post-office.corp.redhat.com/archives/jboss-support-eap6/2018-March...) > EJB race condition can cause client to be in awaitResponse while server is done > ------------------------------------------------------------------------------- > > Key: WFLY-10150 > URL: https://issues.jboss.org/browse/WFLY-10150 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Lin Gao > > With a client jboss server1 that has a client servlet that invokes a remote EJB on jboss server2 configured using server to server config in the standalone.xml/domain.xml outbound remoting connection, the client side can get stuck in awaitResponse while the server side has finished processing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10150) EJB race condition can cause client to be in awaitResponse while server is done

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10150?page=com.atlassian.jira.plugin... ] Lin Gao updated WFLY-10150: --------------------------- > EJB race condition can cause client to be in awaitResponse while server is done > ------------------------------------------------------------------------------- > > Key: WFLY-10150 > URL: https://issues.jboss.org/browse/WFLY-10150 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Lin Gao > > With a client jboss server1 that has a client servlet that invokes a remote EJB on jboss server2 configured using server to server config in the standalone.xml/domain.xml outbound remoting connection, the client side can get stuck in awaitResponse while the server side has finished processing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10150) EJB race condition can cause client to be in awaitResponse while server is done

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10150?page=com.atlassian.jira.plugin... ] Lin Gao moved JBEAP-14527 to WFLY-10150: ---------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-10150 (was: JBEAP-14527) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB (was: EJB) Affects Version/s: (was: 7.1.1.GA) Fix Version/s: (was: 7.1.3.GA) > EJB race condition can cause client to be in awaitResponse while server is done > ------------------------------------------------------------------------------- > > Key: WFLY-10150 > URL: https://issues.jboss.org/browse/WFLY-10150 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Lin Gao > Assignee: JBoss SET > > With a client jboss server1 that has a client servlet that invokes a remote EJB on jboss server2 configured using server to server config in the standalone.xml/domain.xml outbound remoting connection, the client side can get stuck in awaitResponse while the server side has finished processing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-109) Allocate OpenShift and Jenkins resources for Jaeger performance testing

by Kevin Earls (JIRA)

Kevin Earls created SWSQE-109: --------------------------------- Summary: Allocate OpenShift and Jenkins resources for Jaeger performance testing Key: SWSQE-109 URL: https://issues.jboss.org/browse/SWSQE-109 Project: Kiali QE Issue Type: QE Task Reporter: Kevin Earls Assignee: Michael Foley This JIRA is to track what I've mentioned in a few of the Infrastructure team meetings, the need for OpenShift and Jenkins resources to run Jaeger performance tests. Initial requirements for this are for something similar to what we've been using on the CNCF CI OpenShift, which is an "Intel E3-1240 v3" with 32g of memory and 250g of ssd. Longer term this will need to grow, although I don't really have any idea at this point what requirements will be. Perhaps Jaeger testing and Kiali/Istio testing can use the same resources. As this is required for performance testing whatever resources we use will need to be isolated from other OpenShift users so that test results are repeatable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3723) Add HostExcludeResourceDefinition.KnownRelease items for WildFly 11 and 12

by Chao Wang (JIRA)

Chao Wang created WFCORE-3723: --------------------------------- Summary: Add HostExcludeResourceDefinition.KnownRelease items for WildFly 11 and 12 Key: WFCORE-3723 URL: https://issues.jboss.org/browse/WFCORE-3723 Project: WildFly Core Issue Type: Task Components: Domain Management Affects Versions: 5.0.0.Alpha2 Reporter: Chao Wang Assignee: Chao Wang -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2439) Manage empty relation cell as null

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2439: -------------------------------------- Summary: Manage empty relation cell as null Key: DROOLS-2439 URL: https://issues.jboss.org/browse/DROOLS-2439 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Attachments: image-2018-03-30-09-38-46-944.png In a relation containing empty cell !image-2018-03-30-09-38-46-944.png! manage empty cell as {{null}} expression -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10149) Introduce a maximum-timeout management model attribute

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/WFLY-10149?page=com.atlassian.jira.plugin... ] Amos Feng updated WFLY-10149: ----------------------------- Issue Type: Feature Request (was: Enhancement) > Introduce a maximum-timeout management model attribute > ------------------------------------------------------ > > Key: WFLY-10149 > URL: https://issues.jboss.org/browse/WFLY-10149 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Reporter: Amos Feng > Assignee: Amos Feng > > some resources may fail with a timeout value of Integer.MAX_VALUE for various reasons, so a lower "maximum" (such as one year) might be better. The purpose of the suggestion of the maximum timeout attribute would be to make this value configurable (also in the event where someone programmatically sets a timeout which might be problematic), -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 March 2018