[
https://jira.jboss.org/jira/browse/JBESB-2982?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-2982.
-------------------------------
Resolution: Out of Date
The issue in 4.6 was that the bindings were not being updated by the installation but this
is now fixed and will be in the imminent 4.7 release.
juddi fails to start when ports ofther than default are specified in
Service Binding Manager
--------------------------------------------------------------------------------------------
Key: JBESB-2982
URL:
https://jira.jboss.org/jira/browse/JBESB-2982
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.6
Environment: Tested in EAP 5 and AS 5.1, the problem occurs in both when the
Service Binding Manager is used with configuration ports-01
Reporter: Brad Maxwell
juddi fails to start when ports other than default are specified such as using the
ports-01 configuration in the Service Binding Manager. It appears to just be the JNDI port
which is hard coded to 1099 in
$JBOSS_HOME/server/$SERVER_CONF/deployers/esb.deployer/esb.juddi.xml. This should be
changed to use the port injection or some other method such that the Service Binding
Manager can be used.
ERROR [STDERR] (main) javax.naming.CommunicationException: Could not obtain connection to
any of these urls: hostname: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 hostname/127.0.0.1:1099
[Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server
hostname/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection
refused]]]
ERROR [STDERR] (main) at
org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
ERROR [STDERR] (main) at
org.jnp.interfaces.NamingContext.rebind(NamingContext.java:547)
...
ERROR [STDERR] (main) Caused by: javax.naming.CommunicationException: Failed to connect
to server hostname/127.0.0.1:1099 [Root exception is
javax.naming.ServiceUnavailableException: Failed to connect to server
hostname/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection
refused]]
ERROR [STDERR] (main) at
org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
...
ERROR [STDERR] (main) Caused by: javax.naming.ServiceUnavailableException: Failed to
connect to server hostname/127.0.0.1:1099 [Root exception is java.net.ConnectException:
Connection refused]
ERROR [STDERR] (main) at
org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
ERROR [STDERR] (main) ... 69 more
ERROR [STDERR] (main) Caused by: java.net.ConnectException: Connection refused
ERROR [STDERR] (main) at java.net.PlainSocketImpl.socketConnect(Native Method)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira