+1 Andreas
On Thu, Oct 8, 2009 at 00:28, Nandana Mihindukulasooriya <nandana....@gmail.com> wrote: > +1 > > regards, > Nandana > > On Wed, Oct 7, 2009 at 5:17 PM, Amila Suriarachchi > <amilasuriarach...@gmail.com> wrote: >> >> +1, for release. lets finish with 1.5 :) >> >> Regarding your change, >> I think same thing can be done with the existing code in the trunk or >> earlier code in the branch by setting a following properties. >> >> MultiThreadedHttpConnectionManager multiThreadedHttpConnectionManager = >> new MultiThreadedHttpConnectionManager(); >> HttpClient httpClient = new >> HttpClient(multiThreadedHttpConnectionManager); >> >> >> configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, >> Constants.VALUE_TRUE); >> >> configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT, >> httpClient); >> >> With your change since only one Connection Manager have to use anyway, >> Then effective number of parallel connections is 2. Other threads can not >> use the connection >> manager until one thread release it calling >> serviceClient.cleanupTransport(); (even for the dual channel case it has to >> wait until 202 accepted returns) >> >> Since anyway users can achieve this using the above method, IMHO this >> change is unnecessary. So please have a proper discussion if you intended to >> do this change to trunk. >> >> thanks, >> Amila. >> >> On Wed, Oct 7, 2009 at 7:10 PM, Deepal jayasinghe <deep...@gmail.com> >> wrote >>> >>> +1 for the release. >>> >>> Thanks >>> Deepal >>> > Hi Axis Developers, >>> > >>> > After fixing the documentation and a few other small issues since the >>> > last >>> > attempt at 1.5.1, I think we're ready to try again. I've also >>> > addressed the >>> > "forced build of Axiom" issue with the CLOSE_WAIT fix - we now by >>> > default >>> > clean up the last operation context each time we build a new one inside >>> > ServiceClient. >>> > >>> > While there may still be a few things we need to address (still waiting >>> > for >>> > transports / Rampart / Sandesha for instance), I think it's important >>> > to get >>> > this out ASAP since there were clearly some serious issues with 1.5 - >>> > including the failed JavaDoc build and the persistent CLOSE_WAIT issues >>> > that >>> > are fixed in 1.5.1. >>> > >>> > As a reminder, fixes include: >>> > >>> > * Fix for the dreaded "CLOSE_WAIT" problem (JIRA issues 935, 2883, >>> > etc). >>> > We now share an instance of HTTPClient across each ConfigurationContext >>> > (i.e. >>> > each Axis2 server or ServiceClient) - connection reuse is now >>> > automatic. This >>> > means the REUSE_HTTP_CLIENT flag is no longer necessary or useful, nor >>> > is >>> > creating your own MultithreadedHttpConnectionManager. >>> > * Transport deployer is now actually functional, and >>> > getListenerManager() >>> > in ConfigurationContext now creates a new LM if there isn't one >>> > already. >>> > * Fix for AXIS2-4034, module versions now support real versions >>> > like "1.5.1" >>> > * NPE problem (see AXIS2-4114) fixed in MessageContext while >>> > retrieving >>> > policy. >>> > * Fix for JavaDoc build problem. >>> > >>> > I'd like to kick off a VOTE for the release, with the usual 72-hour >>> > window >>> > for votes. >>> > >>> > You can find the distribution files in here: >>> > >>> > >>> > http://people.apache.org/~gdaniels/stagingRepo/org/apache/axis2/distribution/1.5.1/ >>> > >>> > And the M2 repository with everything is at: >>> > >>> > http://people.apache.org/~gdaniels/stagingRepo >>> > >>> > The SVN tag is: >>> > >>> > https://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.5.1RC2 >>> > >>> > ...and I'll add a proper "v1.5.1" tag as soon as this release goes >>> > final. >>> > >>> > Please offer your VOTE (and indicate binding/non-binding). >>> > >>> > Here's my +1 (binding). >>> > >>> > Many thanks, >>> > --Glen >>> > >>> > >>> > >>> >>> >>> -- >>> Thank you! >>> >>> >>> http://blogs.deepal.org >>> http://deepal.org >>> >> >> >> >> -- >> Amila Suriarachchi >> WSO2 Inc. >> blog: http://amilachinthaka.blogspot.com/ >
