-
1. Re: Jboss AS 7.1.3 - Unable to access Web Context
jaikiran May 8, 2013 1:53 AM (in response to georgesg)http://<Server-ip-addres>:9990/mmadmin
The HTTP port is 8080 not 9990.
-
2. Re: Jboss AS 7.1.3 - Unable to access Web Context
georgesg May 8, 2013 2:29 AM (in response to jaikiran)I got it !
Just noticed the below configuration in the standalone-full.xml . So 9990 is the http port for management console, whereas for webapplications, the default http port is 8080. But still i could not access my web application using the url http://<Server-ip-address>:8080/mmadmin
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
<socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
<socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
<socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
<socket-binding name="ajp" port="8009"/>
<socket-binding name="http" port="8080"/>
<socket-binding name="https" port="8443"/>
<socket-binding name="jacorb" interface="unsecure" port="3528"/>
<socket-binding name="jacorb-ssl" interface="unsecure" port="3529"/>
<socket-binding name="messaging" port="5445"/>
<socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:231.7.7.7}" multicast-port="${jboss.messaging.group.port:9876}"/>
<socket-binding name="messaging-throughput" port="5455"/>
<socket-binding name="osgi-http" interface="management" port="8090"/>
<socket-binding name="remoting" port="4447"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
<socket-binding name="txn-status-manager" port="4713"/>
<socket-binding name="jndi" port="1099" fixed-port="false" multicast-port="1098"/>
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="25"/>
</outbound-socket-binding>
</socket-binding-group>
-
3. Re: Jboss AS 7.1.3 - Unable to access Web Context
georgesg May 8, 2013 2:37 AM (in response to georgesg)Thanks Jaikiran,
I managed to make it by changing the jboss bind address from 127.0.0.1 to 0.0.0.0 as below , since it is a web admin portal intended to be accessed outside of the hosted jboss server as well.
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:0.0.0.0}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:0.0.0.0}"/>
</interface>
<interface name="unsecure">
<inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
</interface>
</interfaces>