SOA-P 4.3 throws javax.naming.CommunicationException during startup if Binding Manager is configured

Solution Verified - Updated -

Issue

When I configure the ServiceBindingManager to change the value of java.naming.provider.url (e.g. jnp://${jboss.esb.bind.address}:1199), JBoss SOA-P throws javax.naming.CommunicationException during startup:

2009-10-19 19:10:26,656 ERROR [STDERR]
javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error:
javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception
is 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: Connectionrefused]]]
2009-10-19 19:10:26,658 ERROR [STDERR]  at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1562)
2009-10-19 19:10:26,658 ERROR [STDERR]  at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:487)
2009-10-19 19:10:26,658 ERROR [STDERR]  at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:480)
2009-10-19 19:10:26,659 ERROR [STDERR]  at javax.naming.InitialContext.rebind(InitialContext.java:367)
2009-10-19 19:10:26,659 ERROR [STDERR]  at org.apache.juddi.registry.rmi.JNDIRegistration.register(JNDIRegistration.java:95)
2009-10-19 19:10:26,659 ERROR [STDERR]  at org.jboss.internal.soa.esb.dependencies.JuddiRMIService.startService(JuddiRMIService.java:112)

Environment

  • JBoss SOA Platform (SOA-P)
    • 4.3.0.GA CP02

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.