Acess Jboss from outside the server

Hi - I created a ec2 server in amazon and host my application there.
Its working I mean
http://localhost:8082/testapplication 
link is working but when I try to access this outside the environment it's not working
I tried using the IPaddress
http://11.11.111.111:8082/testapplication 
I am using Jboss 7.1.1

so what changes should i make in jboss to make this available outside the server.

Thanks,
shragiAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Anthony CarterCommented:
Two things to check:

1) The EC2 firewall has been opened on the port you are running JBoss (or you are using an apache httpd proxy and open port 80).
2) That JBoss is started to listen on all NICs.  By default it only listens on 127.0.0.1.  You have to start it with -b 0.0.0.0 (prior to 7.x) to listen to all NICS (or specify which NIC to listen on).  For 7.0 have a look here:

https://developer.jboss.org/thread/168789?_sscc=t
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
shragiAuthor Commented:
Hi Anthony - I am using standalone.bat to start the server
so I updated the standalone.xml as below
<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:0.0.0.0}"/>
        </interface>
    </interfaces>

removed all 127.0.0.1 to 0.0.0.0

coming to EC2 I edited scurity group as below
Type = All traffic
Protocol: All
port: All
source: 0.0.0.0/0

Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Servers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.