Brando These issues impact the throughput you can achieve - for example if you are retrieving an array of complex types (which we are). The fix to this appears to reduce the time taken to retrieve data by a factor of 4-5. Even on a notebook PC our database query retrieves 1000 records in a couple of seconds however on a faster multicore server with SSD it takes over 20 seconds to get 1000 records through the WS API.
The problem is apparently resolved in 1.6.2 and 1.7.0, so if you are planning to move to 1.6 and are concerned about performance then I¹d suggest using 1.6.2, which hopefully (!!!) will be available soon Regards Alan On 11/17/11 1:52 PM, "brando.argue...@gdc4s.com" <brando.argue...@gdc4s.com> wrote: > Alan, > What are #5119, #4878 and #4524? > We¹re migrating from 1.5.1 to Axis 1.6 and performance is one of our main > concerns. > > Thank You. > Brando > > > From: Alan Clark [mailto:alan.d.cl...@telchemy.com] > Sent: Thursday, November 17, 2011 1:47 PM > To: java-user@axis.apache.org > Subject: Expected release date for 1.6.2 ?? > > > Our application (using 1.6.1) is being severely performance limited by the > caching problems reported in #5119, #4878 and #4524. We understand that these > are resolved in 1.6.2 however would very much appreciate knowing when this > would be available. We would also be quite happy to test this release (or > pre-release) and provide feedback if that would be useful. > > Thanks > > Alan >
