Setting options.setCallTransportCleanup(true) and options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE) did not solve my problem. Still the same Exception.
But I think I may have discovered an other thing which may be important: Currently I create a new RPCServiceClient instance in every loop. If I create the RPCServiceClient only once and then reuse the same instance in every loop I managed to make 5000 and 10000 calls in a row. Unfortunately the system architecture which calls the service can not be changed easily to reuse the RPCServiceClient instance. So the problem still exists. Pär: maybe you can tell me how your scenario - which works for you - is. Do you create a new Axis2 service instance for every call to the service or do you create the service once and then call it multiple times? Thanks - Marc ________________________________ > From: [EMAIL PROTECTED] > To: [email protected] > Subject: RE: [Axis2] BindException calling RPCServiceClient very frequently > Date: Thu, 29 Nov 2007 11:38:22 +0100 > > Hi! > > I solved the problem with: > > > > Options options = stub._getServiceClient().getOptions(); > > options.setCallTransportCleanup(true); > > options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE); > > /Pär > > > > > > >> Date: Thu, 29 Nov 2007 11:15:42 +0530 >> From: [EMAIL PROTECTED] >> To: [email protected] >> Subject: Re: [Axis2] BindException calling RPCServiceClient very frequently >> >> Marc Nädele wrote: >>> Hi all, >>> >>> I am now searching for a solution to this problem for many weeks without >>> success. >>> >>> I have a very simple RPCServiceClient similar to the one described in the >>> Axis2 POJO Web Services example [1]. If I call this client very frequently >>> in a loop (e.g. 5000 times) I eventually get a BindException when calling >>> the service. Client OS is Windows XP SP2. Axis2 version is 1.3. >>> >>> In the meanwhile I know that the sockets used for the connections are not >>> closed fast enough and if the maximum user sockets under Windows of 5000 is >>> reached I get those exceptions. >>> >>>>From the threads in this mailing list ([2] and [3]) I already got a good >>>>understanding about the cause of the problem and what the solution for an >>>>asynchronous web service (as described in the JIRA issue #2593 [4]) can be. >>> >>> But I am not able to transfer this knowledge to my RPCServiceClient. All >>> attempts I made failed. The proposed solution desribed in [4] using the >>> AsyncService2Test.java test case as an example seems not to work for a >>> RPCServiceClient . So is it not possible to get a solution for a >>> RPCServiceClient? >>> >>> Does anyone have an idea how I can solve this problem for a >>> RPCServiceClient? Any hints are welcome! >>> >> Did you try client.cleanupTransport() ? >> >> Thanks >> Deepal >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > ________________________________ > Connect to the next generation of MSN Messenger Get it now! _________________________________________________________________ Die neue Version vom Windows Live Messenger ist da! http://get.live.com/messenger/overview --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
