10 Replies Latest reply: Nov 7, 2011 8:08 AM by Radoslav Husar RSS

JBoss AS 7: starts but can't connect (Linux, remote)

Karsten Wutzke Expert

This is my first time installing a server on a remote webspace, so beware. (I know it could turn out to be a non-JBAS question in the end.)

 

I've installed a JRE, put JBoss AS 7 into some dir, and executed standalone.sh. The server starts up regularly:

 

user@vz227:/usr/local/jbossas7/standalone/configuration# ../../bin/standalone.sh
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /usr/local/jbossas7

  JAVA: /usr/lib/jvm/java-6-sun-1.6.0.22/bin/java

  JAVA_OPTS: -server -Xms128m -Xmx256m -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

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

04:28:39,135 INFO  [org.jboss.modules] JBoss Modules version 1.0.1.GA
04:28:39,556 INFO  [org.jboss.msc] JBoss MSC version 1.0.0.GA
04:28:39,652 INFO  [org.jboss.as] JBoss AS 7.0.0.Final "Lightning" starting
04:28:40,875 INFO  [org.jboss.as] creating http management service using network interface (management) port (9990) securePort (-1)
04:28:40,893 INFO  [org.jboss.as.logging] Removing bootstrap log handlers
04:28:40,918 INFO  [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
04:28:40,936 INFO  [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
04:28:41,183 INFO  [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
04:28:41,198 INFO  [org.jboss.as.naming] (MSC service thread 1-1) Starting Naming Service
04:28:41,210 INFO  [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
04:28:41,250 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
04:28:41,263 INFO  [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
04:28:41,279 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
04:28:41,291 INFO  [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
04:28:41,691 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/lib/jvm/java-6-sun-1.6.0.22/jre/lib/i386/server:/usr/lib/jvm/java-6-sun-1.6.0.22/jre/lib/i386:/usr/lib/jvm/java-6-sun-1.6.0.22/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
04:28:41,732 INFO  [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-4) Starting remote JMX connector
04:28:41,734 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) Listening on /127.0.0.1:9999
04:28:41,761 INFO  [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
04:28:41,857 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
04:28:42,261 INFO  [org.jboss.as.connector] (MSC service thread 1-3) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.CR2)
04:28:42,349 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) Bound data source [java:jboss/datasources/ExampleDS]
04:28:42,899 INFO  [org.jboss.as.deployment] (MSC service thread 1-1) Started FileSystemDeploymentService for directory /usr/local/jbossas7/standalone/deployments
04:28:42,919 INFO  [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final "Lightning" started in 4236ms - Started 92 of 147 services (55 services are passive or on-demand)

 

 

As you can see from the trace I have the default datasource hooked up, ExampleDS. Port is 8080, all unchanged. In Windows localhost environments this usually suffices to get a connection to the server via http://localhost:8080/.

 

However, when I enter my domain name and/or IP address plus port 8080 I can't connect. Must be something missing in my Linux configuration. But what? Might there be a service not listening to the port? How do I find out? Does the standalone.xml need something I haven't set?

 

What would a Windows user not know to configure on a remote Linux machine (running in a regular virtual server env)?

 

Karsten

 

PS: this is a standard JBoss AS 7 install, no cluster or anything.