[jboss-jira] [JBoss JIRA] Commented: (AS7-1341) Link to console on startup page fails when running in EC2/limited network with any-address
David Lloyd (JIRA)
jira-events at lists.jboss.org
Tue Jul 19 10:49:25 EDT 2011
[ https://issues.jboss.org/browse/AS7-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615059#comment-12615059 ]
David Lloyd commented on AS7-1341:
----------------------------------
Using the literal IP address from an {{<interface>}} tag, or using the localAddress of a bound socket, to construct a public URL is always incorrect, at least when said address resolves to {{0.0.0.0}} or {{::}}. I thought we had a public interface detection mechanism?
> Link to console on startup page fails when running in EC2/limited network with any-address
> ------------------------------------------------------------------------------------------
>
> Key: AS7-1341
> URL: https://issues.jboss.org/browse/AS7-1341
> Project: Application Server 7
> Issue Type: Bug
> Reporter: Max Rydahl Andersen
>
> Not sure if this is supposed to work but seems it could be detected and then handled better.
> Started AS7 on an EC2 instance with:
> <interfaces>
> <interface name="management">
> <any-address/>
> </interface>
> <interface name="public">
> <any-address/>
> </interface>
> </interfaces>
> to have it actually be available from the outside.
> Then going to http://<echostname>:8080 the http://<echohostname>:8080/console link on the frontpage redirects to http://0.0.0.0:9990/console
> which doesn't resolve to anything anywhere ;)
> I would expect an error page as when the management console is not available at all or at least use the same url as the incoming request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list