October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (REMJMX-117) Upgrade to WildFly Elytron 1.1.0.Beta10

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-117?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated REMJMX-117: ------------------------------------ Description: Also add jboss threads 2.2.1.Final to test scope. > Upgrade to WildFly Elytron 1.1.0.Beta10 > --------------------------------------- > > Key: REMJMX-117 > URL: https://issues.jboss.org/browse/REMJMX-117 > Project: Remoting JMX > Issue Type: Component Upgrade > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha2 > > > Also add jboss threads 2.2.1.Final to test scope. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-117) Upgrade to WildFly Elytron 1.1.0.Beta10

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-117: --------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Beta10 Key: REMJMX-117 URL: https://issues.jboss.org/browse/REMJMX-117 Project: Remoting JMX Issue Type: Component Upgrade Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-116) Upgrade to XNIO 3.4.0.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-116?page=com.atlassian.jira.plugin... ] Darran Lofthouse resolved REMJMX-116. ------------------------------------- Resolution: Done > Upgrade to XNIO 3.4.0.Final > --------------------------- > > Key: REMJMX-116 > URL: https://issues.jboss.org/browse/REMJMX-116 > Project: Remoting JMX > Issue Type: Component Upgrade > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-116) Upgrade to XNIO 3.4.0.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-116: --------------------------------------- Summary: Upgrade to XNIO 3.4.0.Final Key: REMJMX-116 URL: https://issues.jboss.org/browse/REMJMX-116 Project: Remoting JMX Issue Type: Component Upgrade Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-115) Release Remoting JMX 3.0.0.Alpha2

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-115: --------------------------------------- Summary: Release Remoting JMX 3.0.0.Alpha2 Key: REMJMX-115 URL: https://issues.jboss.org/browse/REMJMX-115 Project: Remoting JMX Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-114) Actually make use of the provided callback handler in RemotingConnector or set up the callback handler appropriately if it hasn't been provided

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-114?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated REMJMX-114: ------------------------------------ Fix Version/s: 3.0.0.Alpha2 > Actually make use of the provided callback handler in RemotingConnector or set up the callback handler appropriately if it hasn't been provided > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: REMJMX-114 > URL: https://issues.jboss.org/browse/REMJMX-114 > Project: Remoting JMX > Issue Type: Bug > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 3.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7267) [Proxy] No failover on empty response from node

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7267?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-6311 to WFLY-7267: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7267 (was: JBEAP-6311) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Web (Undertow)) Affects Version/s: (was: 7.0.1.GA) (was: 7.0.2.GA) (was: 7.1.0.DR4) > [Proxy] No failover on empty response from node > ----------------------------------------------- > > Key: WFLY-7267 > URL: https://issues.jboss.org/browse/WFLY-7267 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > Undertow balancer do not recognizes empty response as an error. > Can happen when JVM got killed when handling request (System.exit()) > {code} > @Override > public void failed(final HttpServerExchange exchange) { > final long time = System.currentTimeMillis(); > if (tries++ < maxRetryAttempts) { > ... > {code} > Undertow make curl hang. > Apache httpd correctly recognizes empty response as error and starts fail over method. If unsuccessful, 50x is returned in response. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-114) Actually make use of the provided callback handler in RemotingConnector or set up the callback handler appropriately if it hasn't been provided

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/REMJMX-114?page=com.atlassian.jira.plugin... ] Farah Juma updated REMJMX-114: ------------------------------ Git Pull Request: https://github.com/jbossas/remoting-jmx/pull/23 > Actually make use of the provided callback handler in RemotingConnector or set up the callback handler appropriately if it hasn't been provided > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: REMJMX-114 > URL: https://issues.jboss.org/browse/REMJMX-114 > Project: Remoting JMX > Issue Type: Bug > Reporter: Farah Juma > Assignee: Farah Juma > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-114) Actually make use of the provided callback handler in RemotingConnector or set up the callback handler appropriately if it hasn't been provided

by Farah Juma (JIRA)

Farah Juma created REMJMX-114: --------------------------------- Summary: Actually make use of the provided callback handler in RemotingConnector or set up the callback handler appropriately if it hasn't been provided Key: REMJMX-114 URL: https://issues.jboss.org/browse/REMJMX-114 Project: Remoting JMX Issue Type: Bug Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7031) Redirect Port Fails to Redirect to 3rd Party HTTP Port

by Joe Carder (JIRA)

[ https://issues.jboss.org/browse/WFLY-7031?page=com.atlassian.jira.plugin.... ] Joe Carder commented on WFLY-7031: ---------------------------------- Hi, Just curious if any additional information is needed for this issue? Thank you. > Redirect Port Fails to Redirect to 3rd Party HTTP Port > ------------------------------------------------------ > > Key: WFLY-7031 > URL: https://issues.jboss.org/browse/WFLY-7031 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR1 > Reporter: Joe Carder > Assignee: Stuart Douglas > Priority: Minor > > When setting a redirect socket to port not opened by Wildfly (IE: a port opened by Apache HTTPD or IIS), Wildfly throws the following exception: > ERROR [io.undertow.request] (default task-2) UT005001: An exception occurred processing the request: java.lang.IllegalStateException: UT010053: No confidential port is available to redirect the current request. > With the redirect socket to a port opened by JBoss, it works as expected. I'm not 100% sure this is a bug, or functional decision made for Wildfly 10 and is working as expected. However, in Previous Widlfly version (Widlfly 8) it was possible to set the redirect port to a third party service without out issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 October 2016