1 Reply Latest reply on Jan 31, 2012 11:39 AM by Peter Johnson

    Cannot access JBoss 7.0.2 Web Interfaces (TCP port 8080, 9990) on Linux

    Michael Peoples Newbie

      I have just completed a fresh installation of JBoss 7.0.2 on a Linux Centos 5 server.  I start the server at the command line (problem occurs in both standalone and domain modes) and JBoss starts without errors.

       

      When I attempt, from my local Windows workstation, to access the Welcome screen at TCP port 8080 or the management console at port 9990, the connection fails.

       

      I have confirmed that the processes are listening at those ports (netstat -anop | grep 8080 or netstat -anop | grep 9990).

       

      I have confirmed that the Linux firewall (iptables) is set to allow access to these ports.  I have confirmed that I can access other applications (e.g., Apache, Webmin) at their respective ports.

       

      On the localhost, I can telnet to port 8080 and it connects.  I have also tried to telnet from another host on the same subnet to eliminate the possibility of an upstream firewall blocking the connection (there are none to my knowledge). This fails.

       

      Are there additional configuration changes necessary to allow external access to these interfaces?  I have searched through the documentation, but there isn't even a mention of a firewalls or network access restrictions.

       

      Any help would be very much appreciated.

       

      Thanks.

       

      Following are the initial messages shown when JBoss is started in standalone mode:

       

      =========================================================================

       

        JBoss Bootstrap Environment

       

        JBOSS_HOME: /opt/jboss

       

        JAVA: /usr/java/latest/bin/java

       

        JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

       

      =========================================================================

       

      10:56:42,354 INFO  [org.jboss.modules] JBoss Modules version 1.0.2.GA

      10:56:42,881 INFO  [org.jboss.msc] JBoss MSC version 1.0.1.GA

      10:56:43,010 INFO  [org.jboss.as] JBoss AS 7.0.2.Final "Arc" starting

      10:56:44,918 WARN  [org.jboss.as] No security realm defined for native management service, all access will be unrestricted.

      10:56:45,188 INFO  [org.jboss.as] creating http management service using network interface (management) port (9990)

      10:56:45,192 WARN  [org.jboss.as] No security realm defined for http management service, all access will be unrestricted.

      10:56:45,213 INFO  [org.jboss.as.logging] Removing bootstrap log handlers

      10:56:45,272 INFO  [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)

      10:56:45,305 INFO  [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.

      10:56:45,532 INFO  [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Activating Naming Subsystem

      10:56:45,567 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service

      10:56:45,582 INFO  [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Activating OSGi Subsystem

      10:56:45,637 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.2.0.Beta2

      10:56:45,638 INFO  [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem

      10:56:45,661 INFO  [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.0.Beta3

      10:56:45,703 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.0.Beta3

      10:56:46,204 INFO  [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-4) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/jdk1.6.0_30/jre/lib/i386/server:/usr/java/jdk1.6.0_30/jre/lib/i386:/usr/java/jdk1.6.0_30/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib

      10:56:46,293 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) Listening on /127.0.0.1:9999

      10:56:46,295 INFO  [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem

      10:56:46,555 INFO  [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1) Starting remote JMX connector

      10:56:46,601 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080

      10:56:46,954 INFO  [org.jboss.as.connector] (MSC service thread 1-2) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)

      10:56:47,080 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) Bound data source [java:jboss/datasources/ExampleDS]

      10:56:47,849 INFO  [org.jboss.as.deployment] (MSC service thread 1-4) Started FileSystemDeploymentService for directory /opt/jboss/standalone/deployments

      10:56:47,924 INFO  [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final "Arc" started in 6045ms - Started 93 of 148 services (55 services are passive or on-demand)