January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5871) The default redirect port for the 8080 connector is current 8433. Should be 8443 instead.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5871?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-5871: --------------------------------------- Are there any reports of this issue causing any actual problem other than a strange value in a read of the connector resource? The way the integration of this resource is written[1] the default value isn't passed into the JBoss Web layers at all, and the org.apache.catalina.connector.Connector class' default value of 443 will be used. I've looked all the way back to the beginning of the web subsystem and this has always been the case. Given this, the proper fix here may be to remove the default value from the attribute definition altogether. That will result in consistent behavior with between EAP 6.0 and EAP 6.1 and with earlier AS 7.x releases. [1] https://github.com/jbossas/jboss-as/blob/master/web/src/main/java/org/jbo... > The default redirect port for the 8080 connector is current 8433. Should be 8443 instead. > ------------------------------------------------------------------------------------------ > > Key: AS7-5871 > URL: https://issues.jboss.org/browse/AS7-5871 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.3.Final (EAP) > Reporter: Wolf-Dieter Fink > Assignee: Brian Stansberry > Fix For: 7.2.0.Alpha1 > > > The default redirect port for the 8080 connector is 8433. Seems that this is wrong as socket-bindings use 8443 (and former releases also) > [standalone@localhost:9999 /] /subsystem=web/connector=http:read-resource > { > "outcome" => "success", > "result" => { > ..., > "name" => "http", > "protocol" => "HTTP/1.1", > "redirect-port" => 8433, > "scheme" => "http", > "secure" => false, > "socket-binding" => "http", > "ssl" => undefined, > "virtual-server" => undefined > } > } > The pre-configured "https" socket binding conversely is 8443: > [standalone@localhost:9999 socket-binding=https] /socket-binding-group=standard-sockets/socket-binding=https:read-resource > { > "outcome" => "success", > "result" => { > "client-mappings" => undefined, > "fixed-port" => false, > "interface" => undefined, > "multicast-address" => undefined, > "multicast-port" => undefined, > "name" => "https", > "port" => 8443 > } > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-4293) Support property expansion in redirect-port attribute of the web system's connector

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-4293?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4293: ---------------------------------- Fix Version/s: 7.2.0.Alpha1 > Support property expansion in redirect-port attribute of the web system's connector > ----------------------------------------------------------------------------------- > > Key: AS7-4293 > URL: https://issues.jboss.org/browse/AS7-4293 > Project: Application Server 7 > Issue Type: Sub-task > Components: Web > Affects Versions: 7.1.1.Final > Environment: Standalone JBoss AS 7 on RHEL Linux and Windows 7 Enterprise x64 > Reporter: Sven-Jørgen Karlsen > Assignee: Tomaz Cerar > Priority: Optional > Fix For: 7.2.0.Alpha1 > > Attachments: 04_fix_as_4293.patch > > > The connector element of the web subsystem doesn't support property expansion, forcing you to hardwire the port > number. E.g., writing: > ... > <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host"> > <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" > redirect-port="${jboss.web.https.port}"/> > ... > causes a NumberFormatException. Runtime properties for this attribute was supported in previous versions. > Another problem is that there is no predefined property with the above name. > An alternative solution is to allow a reference to a socket binding groups in the attribute value, as discussed in > http://community.jboss.org/thread/176339 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6127) allow expressions in the web subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6127?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6127: ---------------------------------- Fix Version/s: (was: 7.2.0.CR1) > allow expressions in the web subsystem > -------------------------------------- > > Key: AS7-6127 > URL: https://issues.jboss.org/browse/AS7-6127 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management, Web > Affects Versions: 7.1.3.Final (EAP) > Reporter: Emanuel Muckenhuber > Assignee: Tomaz Cerar > Fix For: 7.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-5663) CLONE - System properties are currently unusable for setting a connector's proxy-name

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5663?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5663: ---------------------------------- Fix Version/s: 7.2.0.Alpha1 (was: 7.2.0.CR1) > CLONE - System properties are currently unusable for setting a connector's proxy-name > ------------------------------------------------------------------------------------- > > Key: AS7-5663 > URL: https://issues.jboss.org/browse/AS7-5663 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management, Web > Affects Versions: 7.1.1.Final > Environment: -JBoss Enterprise Application Platform (EAP) 6.0.0 > Reporter: Aaron Ogburn > Assignee: Tomaz Cerar > Fix For: 7.2.0.Alpha1 > > > A connector's proxy-name cannot be set through system properties currently in the web subsystem: > ==domain.xml== > <subsystem xmlns="urn:jbossomain:web:1.1" default-virtual-server="default-host" instance-id="${jboss.node.name}" > native="false"> > <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" proxy-name="${jboss.proxy.name}"/> > The property is never parsed though and > request.getServerName() just returns ${jboss.node.name}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6280) Support expressions in socket-binding client mappings

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6280: ------------------------------------- Summary: Support expressions in socket-binding client mappings Key: AS7-6280 URL: https://issues.jboss.org/browse/AS7-6280 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 The client-mappings attribute doesn't support expressions in the complex list elements. Also, convert the AttributeDefinition to ObjectListAttributeDefinition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6279) Misspelled system property FRAMEWORK_VENDOR "org.osgi.vendor.framework"

by MN Weise (JIRA)

MN Weise created AS7-6279: ----------------------------- Summary: Misspelled system property FRAMEWORK_VENDOR "org.osgi.vendor.framework" Key: AS7-6279 URL: https://issues.jboss.org/browse/AS7-6279 Project: Application Server 7 Issue Type: Bug Components: OSGi Affects Versions: 7.1.1.Final Reporter: MN Weise Assignee: Thomas Diesler Priority: Minor JBoss AS 7 uses misspelled system property for OSGi constant FRAMEWORK_VENDOR which is not defined by OSGi spec. Reference http://www.osgi.org/javadoc/r4v43/core/org/osgi/framework/Constants.html defines for constant FRAMEWORK_VENDOR: "org.osgi.framework.vendor" Jboss uses: "org.osgi.vendor.framework" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6237) Upgrade DMR to 1.1.4

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6237?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved AS7-6237. ----------------------------------- Resolution: Duplicate Issue > Upgrade DMR to 1.1.4 > -------------------- > > Key: AS7-6237 > URL: https://issues.jboss.org/browse/AS7-6237 > Project: Application Server 7 > Issue Type: Component Upgrade > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Critical > Fix For: 7.2.0.Alpha1 > > > Pick up fix for AS7-4913. > Only critical so it doesn't get mass-pushed to 7.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6223) org.jboss.as.protocol.ProtocolChannelClient needs to support client socket bind address config

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6223?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-6223: ---------------------------------- Fix Version/s: 7.1.4.Final (EAP) > org.jboss.as.protocol.ProtocolChannelClient needs to support client socket bind address config > ---------------------------------------------------------------------------------------------- > > Key: AS7-6223 > URL: https://issues.jboss.org/browse/AS7-6223 > Project: Application Server 7 > Issue Type: Feature Request > Components: CLI, Domain Management > Affects Versions: 7.1.0.Final > Reporter: William DeCoste > Assignee: William DeCoste > Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) > > > OpenShift requires that the client socket bind address be set to the OPENSHIFT_INTENRAL_IP loopback. ProtocolChannelClient currently does not support config for the bind address. connect(..) should be calling > return endpoint.connect("remote", bindAddress, destAddress, builder.getMap(), actualHandler, sslContext); > instead of > > return endpoint.connect(uri, builder.getMap(), actualHandler, sslContext); > and expose bindAddress config -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6277) Expose mgmt client socket binding config through ModelControllerClient Factory

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6277: ------------------------------------- Summary: Expose mgmt client socket binding config through ModelControllerClient Factory Key: AS7-6277 URL: https://issues.jboss.org/browse/AS7-6277 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.3.0.Alpha1 Parent task used a secret system property to configure this to support Open Shift's immediate need, but proper configuration is needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-6278) Expose client socket binding config through CLI connect configs

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6278: ------------------------------------- Summary: Expose client socket binding config through CLI connect configs Key: AS7-6278 URL: https://issues.jboss.org/browse/AS7-6278 Project: Application Server 7 Issue Type: Sub-task Components: CLI Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 7.3.0.Alpha1 Once AS7-6277 is done, continue exposing the client bind socket config to CLI users. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 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 2013