2007/11/6, Simon Laws <[EMAIL PROTECTED]>: > Hi Giorgio > > Am just applying your patch to make repeated @OneWay invocations work to the > tunk and it's looking good as I'm getting a clean build and the new onway > itest now runs. (Am just updating your workpool demo to trunk level as well > - more in this later) In the mean time I'm interested in understanding what > was actually going wrong with the axis binding. Looking at the changes you > made there are two main things. > > First, setting UseSeparateListener and AUTO_RELEASE_CONNECTION on the > operation client And setting max number operation for host. I followed Axis Integrations tests:
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/async/AsyncService2Test.java http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/async/AsyncService2Test.java because in the Axis2 Ml was debated the use of async call. > Second, creating an HTTPClient if one doesn't already exist, > > So, looking at this, it seems that Axis2 was not cleaning up connections > properly after a request and that the default HTTP client was not configured > correctly.. It was long debated on Axis2 ml, that Axis2 and Asynchronous operations in several operation. Did you specifically observe what was going on under the covers > to cause the problem? No. I didn't debug well the axis code, because i saw this AXIS JIRA: http://issues.apache.org/jira/browse/AXIS2-935 In the patch that i provided there's a problem, in SCA 1.0 my node SCANodeImpl is different from yours...i found that the application didn't clean up. I corrected it in SCANodeImpl, when it calls stop I have: public void stop() throws ActivationException { // stop the components // remove contributions // Stop the node nodeRuntime.stop(); //managementRuntime.stop(); // Cleanup the top level composite nodeComposite = null; // remove the manager objects // go out and remove this node from the wider domain if (isStandalone == false){ try { domainManager.removeNode(domainUri, nodeUri); } catch(Exception ex) { logger.log(Level.SEVERE, "Can't connect to domain manager at: " + domainUrl); throw new ActivationException(ex); } } ---> this line if (managementRuntime!=null) managementRuntime.stop(); } In this way a node exits correctly. BTW Your transformer graph is cool: the shortest path and giving weight to edges is nice :). I still use Tuscany SCA 1.0, because a lot is changed in node management in SCA 1.0.1. I have the complete workpool ready and its job module binding now. Now I have to create an autonomic manager for the workpool :). I issue the JIRA for contributing. Cheers, Giorgio. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
