Rohit Macherla [http://community.jboss.org/people/rohit.macherla] created the discussion "Re: Effective way of forming a WebService client" To view the discussion, visit: http://community.jboss.org/message/561523#561523 -------------------------------------------------------------- Thanks Alessio Soldano. If I may follow it up with another question, is there any way that we can cache the WSDL, since each invocation of getPort (...)  (via the JAX-WS JBossWS-Native) involves a full parse of the WSDL ? Whats happening in this case is : Many invocations of the client WebService. As it involves invoking another WebService, each of the getPort(...) calls resulted in : 1. connecting to the target WSDL location: This can be verified as the WSDL parsing fails when the target host is down. What I mean is, there is no need to connect to the target host and then download the WSDL, if we know that its not gonna change. When I say "WSDL parsing fails", I mean that there are no WSDL parsing statements in the DEBUG log and Exception is thrown before such parsing happens. 2. full parse of WSDL: I find the full WSDL printed in the DEBUG log. Probably this is followed by a conversion of XML to Java artefacts, but this is unnecessary time taking operation (in my view) since the target WSDL is the same anyway. Additionally, I find many open file descriptors accessing the WSDL in the server/<configuration>/data/wsdl/TargetWS/TargetWS001.wsdl (i.e., the WSDL created when I deploy the TargetWS. Though this seems contradictory to the point 1 listed above). Message was edited by: Rohit Macherla -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/561523#561523] Start a new discussion in JBoss Web Services at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Rohit Macherla [http://community.jboss.org/people/rohit.macherla] created the discussion "Re: Effective way of forming a WebService client" To view the discussion, visit: http://community.jboss.org/message/573991#573991 -------------------------------------------------------------- Hi Scott, I have found a quite wierd solution. Actually, I just stumbled upon it. We were using NetBeans 6.0.1 for WebService development. The major issue was that threads were not released properly and still hung around for a lot of time with the Tomcat status as : GET /TargetServiceManagement-war/TargetService?wsdl HTTP/1.1 Another important one : Target WSDL parsing happening for each time a WS is invoked. Shifting to NetBeans 6.8 has solved the issue. No other modifications were made to JBoss server. I have redeployed the code with NetBeans 6.0.1 and tested again and found that the threads still hung. But with NetBeans 6.8 code (no changes in the java files that we have written. None at all), no hung threads are noticed. Supecting that there has to be some changes in XML files, I've compared their contents and there are changes in the jax-ws.xml. There are a lot of <wsimport-options> present in the NetBeans 6.8 version code, which probably might be stopping the re-parse of full WSDL. The following are the options added in the new version jax-ws.xml :       <wsimport-options>         <wsimport-option>           <wsimport-option-name>extension</wsimport-option-name>           <wsimport-option-value>true</wsimport-option-value>         </wsimport-option>         <wsimport-option>           <wsimport-option-name>verbose</wsimport-option-name>           <wsimport-option-value>true</wsimport-option-value>         </wsimport-option>         <wsimport-option>           <wsimport-option-name>wsdlLocation</wsimport-option-name>                <wsimport-option-value> http://JBOSS:8080/war/Service?wsdl http://JBOSS:8080/war/Service?wsdl</wsimport-option-value>         </wsimport-option>         <wsimport-option>           <wsimport-option-name>xendorsed</wsimport-option-name>           <wsimport-option-value>true</wsimport-option-value>         </wsimport-option>         <wsimport-option>           <wsimport-option-name>package</wsimport-option-name>           <wsimport-option-value>SOcreation</wsimport-option-value>         </wsimport-option>         <wsimport-option>           <wsimport-option-name>target</wsimport-option-name>           <wsimport-option-value>2.1</wsimport-option-value>         </wsimport-option>       </wsimport-options> I don't know how the threads hanging thing is fixed. But its fixed with the NetBeans 6.8 version developed code. If someone knows answers to these things, please post them here. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/573991#573991] Start a new discussion in JBoss Web Services at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]