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]
