Win a copy of Murach's MySQL this week in the JDBC and Relational Databases forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

Can't Launch JBoss 7.1.1 on Amazon AWS Windows Server2008R2 for Remote Access

Ranch Hand
Posts: 72
Eclipse IDE Firefox Browser Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

I have an AWS (T2-small) Instance that is running Windows Server2008R2. I have installed JBoss 7.1.1 (from and am able to launch it with "standalone.bat". In this case I am able to access the server with a local browser @ http://localhost:8080 and http://localhost:9990.

However, if I try to launch the server for remote access with "standalone.bat -b=PublicIPAddressOfTheAWSInstance" an attempt to reach to reach the server from a remote system using http://PublicIPAddressOfTheAWSInstance:8080 results in a "Timeout" and we don't connect. Further, using a local browser:
http://localhost:8080 still connects
http://PublicIPAddressOfTheAWSInstance:8080 does not connect
http://localhost:9990 no longer connects
http://PublicIPAddressOfTheAWSInstance:9990 does not connect

What may be an important hint is that I see the following error in the console log:
11:48:54,459 INFO [] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]
11:48:54,475 INFO [] (MSC service thread1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-as-7
.1.1.Final\standalone\deployments11:49:00,403 INFO [] (Controller Boot Thread) JBAS014774
: Service status reportJBAS014777: Services which failed to start: service org.jboss.msc.service.StartException in service JBAS015810: failed to resolve interface public

11:49:00,419 INFO [] (Controller Boot Thread) JBAS015954: Admin console is not enabled
11:49:00,419 ERROR [] (Controller Boot Thread) JBAS015875: JBoss AS7.1.1.Final "Brontes" started (with errors) in 9142ms - Started 119 of 214 services (44 services failed or missing dependencies, 49 services are passive or on-demand)

>>> Note the error: JBAS015810: failed to resolve interface public.

Additional info: The AWS Instance is deployed in the default VPC and an AWS Security Group is defined to permit access to PublicIPAddressOfTheAWSInstance from all IP addresses using TCP on 8080. Also, the Windows Firewall is disabled.

I am guessing that "interface public" failing to resolve is related to why I can't get remote access.

Note that if I launch with "standalone.bat -b=" EVERYTHING WORKS! There is no error in the log and remote access is available. However, using is not advisable for production.

Can anyone help me understand why this is failing if I specify the AWS Public address?

Thank you.
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic