Unable to start Glassfish 3.1 even though port not occupied

Question

I\'m having trouble starting Glassfish 3.1 on a newly setup Debian \"Squeeze\" server. This is a testing server that has been setup and the Glassfish i

Answer 1

Recently (only applicable on Amazon Web Services-AWS), I found that launching a server into VPC requires quite a bit of extra configuration (once off) to get started. A key clue:

 nslookup `hostname`

should work. If it doesn't work, that's likely to be the reason.

You can either: 1) launch a server into EC2-classic 2) configure your VPC / host to be able to run the command above successfully.

Hope that helps.