July 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3368) Reverse proxy configuration should use outbound-socket-binding

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-3368?page=com.atlassian.jira.plugin.... ] Tomaz Cerar edited comment on WFLY-3368 at 7/28/14 5:06 PM: ------------------------------------------------------------ @matt Would something like this cover your scenarios: {code:xml} <reverse-proxy name="reverse-proxy" connections-per-thread="30"> <host name="localhost" scheme="ajp" path="/sub-resource"outbound-socket-binding-ref="ajp-remote" instance-id="myRoute"/> </reverse-proxy> {code} and later in config you have {code:xml} <outbound-socket-binding name="ajp-remote"> <remote-destination host="localhost" port="8009"/> </outbound-socket-binding> {code} was (Author: ctomc): @matt Would something like this cover your scenarios: {code:xml} <reverse-proxy name="reverse-proxy" connections-per-thread="30"> <host name="localhost" scheme="ajp" outbound-socket-binding-ref="ajp-remote" instance-id="myRoute"/> </reverse-proxy> {code} and later in config you have {code:xml} <outbound-socket-binding name="ajp-remote"> <remote-destination host="localhost" port="8009"/> </outbound-socket-binding> {code} > Reverse proxy configuration should use outbound-socket-binding > -------------------------------------------------------------- > > Key: WFLY-3368 > URL: https://issues.jboss.org/browse/WFLY-3368 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Final > Reporter: Matt Wringe > Assignee: Tomaz Cerar > Fix For: 9.0.0.Beta1 > > > The reverse proxy configuration in standalone.xml requires a string value and will not accept variables like most of the other options. > for example, something like this should be valid, but its currently not: > {code:xml} > <handlers> > <reverse-proxy name="reverse-proxy" connections-per-thread="30"> > <host name="${myURL}" instance-id="myRoute"/> > </reverse-proxy> > <handlers> > {code} > Here you need to specify the name as something like "http://127.5.183.1:8080" -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3256) IronJacamar 1.1.7.Final

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-3256?page=com.atlassian.jira.plugin.... ] Jesper Pedersen updated WFLY-3256: ---------------------------------- Summary: IronJacamar 1.1.7.Final (was: IronJacamar 1.1.6.Final) Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/6262) Affects Version/s: 8.1.0.Final (was: 8.0.0.Final) (was: 8.1.0.CR1) (was: 8.1.0.CR2) Description: (was: When idle-timeout is configured idle remover thread can consume 100% of cpu. See forum thread for more details.) > IronJacamar 1.1.7.Final > ----------------------- > > Key: WFLY-3256 > URL: https://issues.jboss.org/browse/WFLY-3256 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.1.0.Final > Reporter: Tomaz Cerar > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 8.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3256) IronJacamar 1.1.6.Final

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-3256?page=com.atlassian.jira.plugin.... ] Jesper Pedersen reopened WFLY-3256: ----------------------------------- > IronJacamar 1.1.6.Final > ----------------------- > > Key: WFLY-3256 > URL: https://issues.jboss.org/browse/WFLY-3256 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.1.0.Final > Reporter: Tomaz Cerar > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 8.2.0.CR1 > > > When idle-timeout is configured idle remover thread can consume 100% of cpu. > See forum thread for more details. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1199) Guard against ISE in TransactionSynchronizer

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1199?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1199. ------------------------------------ Resolution: Done > Guard against ISE in TransactionSynchronizer > -------------------------------------------- > > Key: JBJCA-1199 > URL: https://issues.jboss.org/browse/JBJCA-1199 > Project: IronJacamar > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 1.0.26.Final, 1.1.6.Final, 1.2.0.Beta3 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2900) Performance issue with Xalan transformer and very large text nodes

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2900?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2900: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.2.0.CR1) > Performance issue with Xalan transformer and very large text nodes > ------------------------------------------------------------------ > > Key: WFLY-2900 > URL: https://issues.jboss.org/browse/WFLY-2900 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XML Frameworks > Reporter: Kyle Lape > Assignee: Jason Greene > Priority: Blocker > Fix For: 9.0.0.CR1 > > > It has been observed that when using the {{Transfomer}} to convert a {{StreamSource}} to {{DOMResult}}, the performance of Transform gets worse as the size of the > character data increases. If you have a 50MB text blob in XML, this will take a very long time to finish. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2900) Performance issue with Xalan transformer and very large text nodes

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2900?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-2900: ------------------------------------ I have reverted the xalan patch, which I suspect causes regressions: https://github.com/jboss/xalan-j/pull/3 The likely regression is here: https://bugzilla.redhat.com/show_bug.cgi?id=1087991 > Performance issue with Xalan transformer and very large text nodes > ------------------------------------------------------------------ > > Key: WFLY-2900 > URL: https://issues.jboss.org/browse/WFLY-2900 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XML Frameworks > Reporter: Kyle Lape > Assignee: Jason Greene > Priority: Blocker > Fix For: 8.2.0.CR1 > > > It has been observed that when using the {{Transfomer}} to convert a {{StreamSource}} to {{DOMResult}}, the performance of Transform gets worse as the size of the > character data increases. If you have a 50MB text blob in XML, this will take a very long time to finish. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1200) CachedConnectionManager should only lock if needed

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1200?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1200. ------------------------------------ Resolution: Done > CachedConnectionManager should only lock if needed > -------------------------------------------------- > > Key: JBJCA-1200 > URL: https://issues.jboss.org/browse/JBJCA-1200 > Project: IronJacamar > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core > Affects Versions: 1.0.26.Final, 1.1.6.Final, 1.2.0.Beta3 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1200) CachedConnectionManager should only lock if needed

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1200: -------------------------------------- Summary: CachedConnectionManager should only lock if needed Key: JBJCA-1200 URL: https://issues.jboss.org/browse/JBJCA-1200 Project: IronJacamar Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Affects Versions: 1.2.0.Beta3, 1.1.6.Final, 1.0.26.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Critical Fix For: 1.0.27.Final, 1.1.7.Final, 1.2.0.Beta4 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3681) General Schema Sync with EAP

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-3681: -------------------------------------- Summary: General Schema Sync with EAP Key: WFLY-3681 URL: https://issues.jboss.org/browse/WFLY-3681 Project: WildFly Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 9.0.0.CR1 This may actually be more about pushing some changes to EAP, new schemas are being tracked by individual issues but for the remaining schemas where cosmetic changes have been made or corrections to default values and min/max occurs we need to sync with EAP. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-31) The JBoss Modules schemas are missing from the build

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-31: -------------------------------------- Summary: The JBoss Modules schemas are missing from the build Key: WFCORE-31 URL: https://issues.jboss.org/browse/WFCORE-31 Project: WildFly Core Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Stuart Douglas Fix For: 1.0.0.Alpha4 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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 July 2014