The jndi.property pitfall
- Published: 09 May 2009
jboss recipe of the day
A piftall which is sometimes reported in JBoss forum is that JBoss refuses to start up correclty after an ear deployment unit has been added.
javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused]
If the problem disappear when you undeploy the ear deployment unit it is likely that you have added a jndi.properties file in the ear package.
The file jndi.properties is generally used when you connect to jBoss environment from remote resources.
#jboss JNDI properties
Adding to the Ear deployment interfers with JBoss binding process, so JBoss refuses to start-up. Get rid of it and the problem will disappear!