Posted by: cmani2010 | May 20, 2009

Sun Glassfish ES 2.1 – Connection refused error

I was recently at a massive deployment of Sun Glassfish Enterprise server’s (2.1) in a deployment, where the topology was the Glassfish DAS, Node agents, Sun web servers distributed across Solaris Containers across multiple servers – that is horizontal and vertical scaling.

After installing the DAS and Nodeagents, we created Glassfish server instances for all Nodegents, in an app server cluster. When we tried starting the app server instances, we started getting lots of “ Connection refused exceptions” in the server logs and the servers would refuse to start. One of the clue’s, of what the problem could be was in Shalini’s blog. This led us to think, this was related to some kind of hostname issue. The problem, it seems that when you have a cluster of app server instances, there should be a hostname mapped to an IP address entry in /etc/hosts, for every app server instance participating in a cluster

So, in /etc/hosts, you should have something similar to the following:

127…. localhost
xx.xx.xx.xx servername loghost
xx.xx.xx.xx GlassfishDAS
xx.xx.xx.xx Glassfish1
xx.xx.xx.xx Glassfish2
xx.xx.xx.xx Glassfish3

This problem, may probably not arise, if you there is a DNS server. In our case, we were operating from a Data center, with newly installed servers.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s


%d bloggers like this: