[
https://issues.jboss.org/browse/AS7-1341?page=com.atlassian.jira.plugin.s...
]
Andre Dietisheim commented on AS7-1341:
---------------------------------------
The management port seems configured correctly:
{xml}
<management-interfaces>
<native-interface interface="management" port="9999"/>
<http-interface interface="management" port="9990"/>
</management-interfaces>
{xml}
Nevertheless, if I try to substitute the 0.0.0.0:9990 by the proper ec2 address:
ec2-107-20-15-112.compute-1.amazonaws.com:9990/console
I get redirected to
http://ec2-107-20-15-112.compute-1.amazonaws.com/:9990/console which
is not valid either.
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