I ended up using JAX-WS RI 2.1.1 which worked very well for that purpose with no workarounds....I was able to run test calling thousands of service methods which in turn instantiated a ws client on each call to the 2nd web service and it ran just fine.
A side benefit was that the wsdl my POJO's produce was much cleaner especially in the nillable/minOccurs areas with JAX-WS than with Axis2. I would have preferred to stay with Axis2, because the generation procedures and creating of server skeleton stubs and configuration of services is much cleaner/simpler in Axis2 that JAX-WS in my opinion. (the big thing being that Axis2 gives you your stubbed out implementation class for the server for free..but JAX-WS does not as far as I can determine so far...what's up with that :(...) Incidentally I did try using both a singleton client as well as a pool of clients with Axis2 1.4 as well thinking the same thing you thought, but no avail. However I don't think I tried RC-1..was it even out 4 months ago or so?. Perhaps the noise about this problem did generate a fix in that upgrade. Perhaps I should try again with RC1. You mentioned you tried RC1 with a pool of 2nd service proxy stubs to use and it worked, but did you try RC1 without stub pools at all, or did that not work. I'd be interested to see if you didn't even have to pool your 2nd service proxies with RC1... Perhaps I can update my teammates with some new info regarding Axis2 if this RC works as you say, which would be good... Chris -----Original Message----- From: David Rees [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2008 5:13 PM To: [email protected] Subject: Re: Axis2 Webservice called from another websiervice On Thu, Aug 7, 2008 at 4:36 AM, Chris Richmond <[EMAIL PROTECTED]> wrote: > in short..there are MAJOR in memory collisions taking > place whereas the Axis2 stack gets confused. All in all, it was a > miserable failure for using one service calling another, which is > practically SOP in the WS world and I've done it with every other WS stack > I've used. In the end I had to retool my middleware layer to use another WS > stack. Out of curiosity, what WS stack did you end up using? > If you ever successfully get Axis2 webservice calling another webservice > working and working at production levels, I'd love to hear how you did it. My first attempt to do so using Axis2 1.4 resulted in a very fast memory leak which caused the app server to go OOM after handling a couple dozen requests. However, after upgrading to 1.4-RC1 and using a pool of Stubs for the client WS calls, everything appears to be functioning OK. -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
