January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1383) Domain Managent - Ensure current authenticated user is associated with current request / thread and is retrievable.

by Darran Lofthouse (JIRA)

Domain Managent - Ensure current authenticated user is associated with current request / thread and is retrievable. ------------------------------------------------------------------------------------------------------------------- Key: AS7-1383 URL: https://issues.jboss.org/browse/AS7-1383 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 Initially for audit but also for other purposes the current user needs to be identifiable for the request being processed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
4
0 / 0

[JBoss JIRA] (AS7-3311) Add option to use Http11Protocol even if Http11AprProtocol can be used

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-3311: -------------------------------------- Summary: Add option to use Http11Protocol even if Http11AprProtocol can be used Key: AS7-3311 URL: https://issues.jboss.org/browse/AS7-3311 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.1.0.Beta1b Reporter: Rostislav Svoboda Assignee: Remy Maucherat Fix For: 7.1.0.Final Currently if APR is installed on machine and can be used by AS7 (AprLifecycleListener.isAprInitialized()) Http11AprProtocol is set as protocol handler. Please introduce option to force usage of Http11Protocol instead of Http11AprProtocol. On machines with apr installed we are not able to work with java based implementation. Possible place for code change: - org.apache.catalina.connector.Connector -- setProtocol -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
3
0 / 0

[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-3042: ---------------------------------- Fix Version/s: 7.1.0.Final Priority: Major (was: Blocker) I have re-opened to double check what is happening here. However do please not that the redirection is intended as a convenience for a new out of the box installation, it is not intended for redirecting requests received from the public interface so in this scenario it currently sounds more likely that a displayed error is going to be the correct outcome rather than a successful redirect. > IPv6: Invalid redirect to Admin console (wrong IP address) > ---------------------------------------------------------- > > Key: AS7-3042 > URL: https://issues.jboss.org/browse/AS7-3042 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Web > Affects Versions: 7.1.0.Beta1b > Reporter: Pavel Janousek > Assignee: Darran Lofthouse > Fix For: 7.1.0.Final > > > This issue is some derivation from AS7-3040. Lets imagine starting server like this: > {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code} > So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990. > This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse edited comment on AS7-3042 at 1/16/12 6:07 AM: ---------------------------------------------------------------- I have re-opened to double check what is happening here. However do please note that the redirection is intended as a convenience for a new out of the box installation, it is not intended for redirecting requests received from the public interface so in this scenario it currently sounds more likely that a displayed error is going to be the correct outcome rather than a successful redirect. was (Author: dlofthouse): I have re-opened to double check what is happening here. However do please not that the redirection is intended as a convenience for a new out of the box installation, it is not intended for redirecting requests received from the public interface so in this scenario it currently sounds more likely that a displayed error is going to be the correct outcome rather than a successful redirect. > IPv6: Invalid redirect to Admin console (wrong IP address) > ---------------------------------------------------------- > > Key: AS7-3042 > URL: https://issues.jboss.org/browse/AS7-3042 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Web > Affects Versions: 7.1.0.Beta1b > Reporter: Pavel Janousek > Assignee: Darran Lofthouse > Fix For: 7.1.0.Final > > > This issue is some derivation from AS7-3040. Lets imagine starting server like this: > {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code} > So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990. > This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reopened AS7-3042: ----------------------------------- > IPv6: Invalid redirect to Admin console (wrong IP address) > ---------------------------------------------------------- > > Key: AS7-3042 > URL: https://issues.jboss.org/browse/AS7-3042 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Web > Affects Versions: 7.1.0.Beta1b > Reporter: Pavel Janousek > Assignee: Darran Lofthouse > Priority: Blocker > > This issue is some derivation from AS7-3040. Lets imagine starting server like this: > {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code} > So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990. > This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3042) IPv6: Invalid redirect to Admin console (wrong IP address)

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-3042?page=com.atlassian.jira.plugin.s... ] Heiko Braun reassigned AS7-3042: -------------------------------- Assignee: Darran Lofthouse (was: Heiko Braun) > IPv6: Invalid redirect to Admin console (wrong IP address) > ---------------------------------------------------------- > > Key: AS7-3042 > URL: https://issues.jboss.org/browse/AS7-3042 > Project: Application Server 7 > Issue Type: Bug > Components: Console, Web > Affects Versions: 7.1.0.Beta1b > Reporter: Pavel Janousek > Assignee: Darran Lofthouse > Priority: Blocker > > This issue is some derivation from AS7-3040. Lets imagine starting server like this: > {code}./standalone.sh -Djava.net.preferIPv4Stack=false -Djboss.bind.address=::1{code} > So by default the admin/management is bound to _::ffff:127.0.0.1:9990_ and _::ffff:127.0.0.1:9999_, but it isn't accessible from Web WelcomePage at _::1:8080_ because the URL is specified as: {code}<a href="/console">{code} and so the next request is http://[::1]:8080/console which redirect requester to http://[::1]:9990, but there isn't any console because it is here - http://[::ffff:127.0.0.1]:9990. > This is not good as it could lead to integration issues between components (X trying to connect to Y on ::1; Y listening on ::ffff:127.0.0.1). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1415) NakreceiverWindow: replace ReadWriteLock with ReentrantLock

by Bela Ban (JIRA)

Bela Ban created JGRP-1415: ------------------------------ Summary: NakreceiverWindow: replace ReadWriteLock with ReentrantLock Key: JGRP-1415 URL: https://issues.jboss.org/browse/JGRP-1415 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.0.3, 3.1 We have many writes, so replacing the (more complex and costly) RWL with a simple RL should help. Tested this with MPerf; performance is about the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
1
0 / 0

[JBoss JIRA] (AS7-3119) Recurring timer might executed concurrent if the duration of the timeout method will be longer than the interval

by Wolf-Dieter Fink (Created) (JIRA)

Recurring timer might executed concurrent if the duration of the timeout method will be longer than the interval ---------------------------------------------------------------------------------------------------------------- Key: AS7-3119 URL: https://issues.jboss.org/browse/AS7-3119 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.0.Beta1b Reporter: Wolf-Dieter Fink Assignee: Wolf-Dieter Fink Timer with a short interval might be called before the previous execution is finished. This concurrent execution might harm the Bean provider expectations and implementation. In previous releases (AS5 EAP5) the execution is dropped in this case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
4
0 / 0

[JBoss JIRA] (AS7-3313) CLONE - Add option to use Http11Protocol even if Http11AprProtocol can be used

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-3313: -------------------------------------- Summary: CLONE - Add option to use Http11Protocol even if Http11AprProtocol can be used Key: AS7-3313 URL: https://issues.jboss.org/browse/AS7-3313 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.1.0.Beta1b Reporter: Rostislav Svoboda Assignee: Remy Maucherat Fix For: 7.1.0.Final Currently if APR is installed on machine and can be used by AS7 (AprLifecycleListener.isAprInitialized()) Http11AprProtocol is set as protocol handler. Please introduce option to force usage of Http11Protocol instead of Http11AprProtocol. On machines with apr installed we are not able to work with java based implementation. Possible place for code change: - org.apache.catalina.connector.Connector -- setProtocol -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3312) CLONE - User insn't properly informed that APR is used

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-3312: -------------------------------------- Summary: CLONE - User insn't properly informed that APR is used Key: AS7-3312 URL: https://issues.jboss.org/browse/AS7-3312 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.0.Beta1b Reporter: Rostislav Svoboda Assignee: Remy Maucherat Fix For: 7.1.0.Final AS7 log doesn't show sufficient information that APR is used or not. Currently the only clue is that org.apache.coyote.http11.Http11AprProtocol is used instead of org.apache.coyote.http11.Http11Protocol. But it's implementation details and many users can miss that. Add log message to inform users if APR is used or not! For example APR affect https connector definition which must use openssl based keys and not keystore. And if users do not know APR is used they can be easily confused and blame AS7 as broken. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012