Bug 779565 (SOA-1941)

Attachment: Added: server.log
Attachment: Added: esb.juddi.client.xml

This is *why* you need to use InVM when talking to the local server.  The web server (i.e. WS endpoints) are not available until after the server has started.

I know the reason *why* it does not start. IMHO the configuration should not be there. At least not with the URL's pointing to the same port and host name if it doesn't serve as some kind of example. 

The RMI configuration works.

It is there in case someone chooses to use WS to access a remote UDDI, so perhaps the only issue is the fact that it specifies ${jboss.esb.bind.address} and that any documentation on this does not say *replace*.

Perhaps it would be better to replace it with

                <custodyTransferUrl>http://REMOTE_HOST:REMOTE_PORT/juddiv3/services/custody-transfer?wsdl</custodyTransferUrl>

and fix the docs.

Perhaps it does not have to say *replace*, but changing the ${jboss.esb.bind.address} to something else is definitely a good idea.

Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]

We could probably add a comment into the JAX-WS esb.juddi.client.xml section referencing the doc section that talks about the tomcat connector problem locally for future versions.

I suspect that specifying REMOTE_HOST:REMOTE_PORT would be sufficient, as the tomcat behaviour is deliberate and is probably documented in the EAP docs.

Link: Added: This issue depends JBESB-3528

Updated the default configuration to use REMOTE_HOST:REMOTE_PORT

Kevin, you said this was resolved, or no longer an issue. Please mark resolved. Thanks.

ESB configuration was updated to remove the properties which represent the local bindings.

Verified on SOA-P ER5.

Affects: Removed: [Documentation (Ref Guide, User Guide, etc.), Release Notes] Added: [Release Notes]

Reopening to document

Release Notes Docs Status: Added: Not Yet Documented
Writer: Added: Darrin

Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3528
The PROFILE/deploy/jbossesb.sar/esb.juddi.client.xml configuration file included a commented-out example that used the JAX-WS transport to connect to the local UDDI registry.  Using this configuration caused the server to freeze at launch.   The JAX-WS transport can only be used to connect to a remote UDDI registry because the required webservice endpoints are not available until after the server has finished launching. The JAX-WS configuration example has been updated to replace the ${jboss.esb.bind.address}:8080 values with REMOTE_HOST:REMOTE_PORT.  Using this configuration requires that the settings are edited to include the correct hostname and port for the remote UDDI registry.

Release Notes Text: Removed: https://issues.jboss.org/browse/JBESB-3528
The PROFILE/deploy/jbossesb.sar/esb.juddi.client.xml configuration file included a commented-out example that used the JAX-WS transport to connect to the local UDDI registry.  Using this configuration caused the server to freeze at launch.   The JAX-WS transport can only be used to connect to a remote UDDI registry because the required webservice endpoints are not available until after the server has finished launching. The JAX-WS configuration example has been updated to replace the ${jboss.esb.bind.address}:8080 values with REMOTE_HOST:REMOTE_PORT.  Using this configuration requires that the settings are edited to include the correct hostname and port for the remote UDDI registry. Added: https://issues.jboss.org/browse/JBESB-3528
The PROFILE/deploy/jbossesb.sar/esb.juddi.client.xml configuration file included an example that used the JAX-WS transport to connect to the local UDDI registry.  Using this example configuration caused the server to freeze at launch.   The JAX-WS transport can only be used to connect to a remote UDDI registry because the required webservice endpoints are not available until after the server has finished launching. The JAX-WS configuration example has been updated to replace the ${jboss.esb.bind.address}:8080 values with REMOTE_HOST:REMOTE_PORT.  Using this configuration requires that the settings be edited to include the correct hostname and port for the remote UDDI registry.

Release Notes Text: Removed: https://issues.jboss.org/browse/JBESB-3528
The PROFILE/deploy/jbossesb.sar/esb.juddi.client.xml configuration file included an example that used the JAX-WS transport to connect to the local UDDI registry.  Using this example configuration caused the server to freeze at launch.   The JAX-WS transport can only be used to connect to a remote UDDI registry because the required webservice endpoints are not available until after the server has finished launching. The JAX-WS configuration example has been updated to replace the ${jboss.esb.bind.address}:8080 values with REMOTE_HOST:REMOTE_PORT.  Using this configuration requires that the settings be edited to include the correct hostname and port for the remote UDDI registry. Added: https://issues.jboss.org/browse/JBESB-3528
The PROFILE/deploy/jbossesb.sar/esb.juddi.client.xml configuration file included an example that used the JAX-WS transport to connect to the local UDDI registry.  Using this example configuration caused the server to freeze at launch.   The JAX-WS transport can only be used to connect to a remote UDDI registry because the required webservice endpoints are not available until after the server has finished launching. 
The JAX-WS configuration example has been updated to replace the ${jboss.esb.bind.address}:8080 values with REMOTE_HOST:REMOTE_PORT.  Using this configuration requires that the settings be edited to include the correct hostname and port for the remote UDDI registry.

have to edit release note :-(

Release Notes Text: Removed: https://issues.jboss.org/browse/JBESB-3528
The PROFILE/deploy/jbossesb.sar/esb.juddi.client.xml configuration file included an example that used the JAX-WS transport to connect to the local UDDI registry.  Using this example configuration caused the server to freeze at launch.   The JAX-WS transport can only be used to connect to a remote UDDI registry because the required webservice endpoints are not available until after the server has finished launching. 
The JAX-WS configuration example has been updated to replace the ${jboss.esb.bind.address}:8080 values with REMOTE_HOST:REMOTE_PORT.  Using this configuration requires that the settings be edited to include the correct hostname and port for the remote UDDI registry. Added: https://issues.jboss.org/browse/JBESB-3528
The PROFILE/deploy/jbossesb.sar/esb.juddi.client.xml configuration file included an example that used the JAX-WS transport to connect to the local UDDI registry.  Using this example configuration caused the server to freeze at launch.   The JAX-WS transport can only be used to connect to a remote UDDI registry because the required webservice endpoints are not available until after the server has finished launching. 

The JAX-WS configuration example has been updated to replace the ${jboss.esb.bind.address}:8080 values with REMOTE_HOST:REMOTE_PORT.  Using this configuration requires that the settings be edited to include the correct hostname and port for the remote UDDI registry.