Announcement Announcement Module
No announcement yet.
Exception due to bean creation failure on startup Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Exception due to bean creation failure on startup

    I am having the following exception on startup of JBoss occur on JBoss 4.0.5 using Spring 2.0.8 at the point where Spring attempts to instantiate a remote JMS cue by JNDI lookup:

    2009-08-20 21:30:13,527 DEBUG [org.jnp.interfaces.NamingContext] Failed to connect to
    javax.naming.CommunicationException: Failed to connect to server [Root exception i
    s javax.naming.ServiceUnavailableException: Failed to connect to server [Root exce
    ption is Connection refused]]
    	at org.jnp.interfaces.NamingContext.getServer(
    	at org.jnp.interfaces.NamingContext.checkRef(
    	at org.jnp.interfaces.NamingContext.lookup(
    	at org.jnp.interfaces.NamingContext.lookup(
    	at javax.naming.InitialContext.lookup(
    	at org.springframework.jndi.JndiTemplate$1.doInContext(
    	at org.springframework.jndi.JndiTemplate.execute(
    	at org.springframework.jndi.JndiTemplate.lookup(
    	at org.springframework.jndi.JndiTemplate.lookup(
    	at org.springframework.jndi.JndiLocatorSupport.lookup(
    	at org.springframework.jndi.JndiObjectLocator.lookup(
    	at org.springframework.jndi.JndiObjectFactoryBean.lookupWithFallback(
    	at org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(
    The remote resource can't be found because the machine happens to be restarting at the same time as the machine the error happens on. Is there a way to configure Spring's JNDI facilities to retry this lookup for a particular number of times over a particular duration so that it would be able to capture the remote machine when it came back up?

  • #2
    I think this post may prove instructive