[ https://jira.jboss.org/jira/browse/JBESB-3185?page=com.atlassian.jira.plu... ] Len DiMaggio updated JBESB-3185: -------------------------------- Attachment: jboss-esb.xml webservice_proxy_import.zip Quickstart files -- 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

[ https://jira.jboss.org/jira/browse/JBESB-3185?page=com.atlassian.jira.plu... ] David Ward commented on JBESB-3185: ----------------------------------- Okay, so I recreated this using SOA-P 5 CR2 and Sun JDK 1.6.0_17 on Fedora 11 (2.6.30.10-105.2.23.fc11.i686.PAE). Here's the lockup: "main" prio=10 tid=0xb6ac9000 nid=0x2ae6 runnable [0x6521e000] java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) ... - locked <0xafa0f628> (a java.io.BufferedInputStream) at org.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:77) ... at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346) at org.jboss.soa.esb.actions.soap.RemoteWsdlLoader.load(RemoteWsdlLoader.java:85) at org.jboss.soa.esb.actions.soap.AbstractWsdlContractPublisher.getWsdl(AbstractWsdlContractPublisher.java:187) at org.jboss.soa.esb.actions.soap.proxy.SOAPProxyWsdlLoader$Puller.pull(SOAPProxyWsdlLoader.java:434) at org.jboss.soa.esb.actions.soap.proxy.SOAPProxyWsdlLoader.load(SOAPProxyWsdlLoader.java:150) at org.jboss.soa.esb.actions.soap.proxy.SOAPProxy.<init>(SOAPProxy.java:147) ... at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.getActionClassInstance(ActionProcessorMethodInfo.java:355) ... at org.jboss.soa.esb.listeners.deployers.mc.EsbDeployment.start(EsbDeployment.java:122) ... at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:619) The problem is that the SOAPProxy wsdl property is set to localhost:8080: <property name="wsdl" value="http://localhost:8080/Quickstart_webservice_proxy_import_ws/wsdl/HelloWorld_....wsdl"/> , and *Tomcat is not accepting requests yet*. This is why we came up with alternate wsdl protocols - JBESB-2855. In addition to http and https, there is internal, classpath and file. (internal points to locally-deployed JBossWS web services by MBean object name). The internal wsdl uri format, when used with the wsbarrier-service.xml seen in some of the quickstarts, is supposed to make sure re-starts are smooth with the right dependencies. So in short, I don't think this JIRA is a problem. The whole "relative wsdl and schema imports" thing came out of a forum discussion where a user was pointing to an externally-hosted web service whose wsdl had relative imports. The only reason the quickstart uses localhost:8080 is for testing purposes. In real life, it would be pointed elsewhere. One thing you can do for me, however, is test changing the wsdl property (using SOA-P 5 CR2!) to a separate web server and doing a re-start. The SOAPProxy *should* fail deployment but not hang the server, so long as it's not on a Mac (that's a whole 'nother thing Jeff DeLong found - JBESB-3172 - but we don't support Mac for SOA-P so...) -- 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

[ https://jira.jboss.org/jira/browse/JBESB-3185?page=com.atlassian.jira.plu... ] David Ward commented on JBESB-3185: ----------------------------------- Minor comment on the attached logs, originally this was tested against https://svn.jboss.org/repos/labs/labs/jbossesb/trunk , although it should've been tested against https://svn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP , or - better yet - SOA-P 5 CR2. No matter, the hang still would've happened, as expected. -- 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