[
https://jira.jboss.org/jira/browse/JBESB-2947?page=com.atlassian.jira.plu...
]
David Ward closed JBESB-2947.
-----------------------------
Resolution: Done
Committed revision 29963. (trunk)
I changed the SPI usage inside InternalSOAPProxyWsdlLoader to use the JBossWS
endpoint's ServerEndpointMetaData.getServiceMetaData().getWsdlLocation(). An
openStream() is still made on that URL, but it's a *file* URL, not an *http* URL. The
file URL is the temp file made by JBossWS and put in
server/default/data/.../3453434343.wsdl. This way we're not dependent on Tomcat's
Connector to be accepting traffic yet.
InternalSOAPProxyWsdlLoader hangs on ESB restart
------------------------------------------------
Key: JBESB-2947
URL:
https://jira.jboss.org/jira/browse/JBESB-2947
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7
Tom F. and I noticed a problem with the InternalSOAPProxyWsdlLoader's use of
JBossWS's internal SPI, where it is *still* using an http URLConnection
under-the-hood. This is an issue since on restart, Tomcat's http connector is not be
available yet. This causes the main thread of the boot-up to hang.
--
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