You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Glen Daniels <gl...@thoughtcraft.com> on 2009/10/06 06:49:44 UTC
[VOTE] [axis2] Release Axis2 1.5.1 (take 2)
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
Re: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi all:
I'm currently seeing some build failures with Rampart and 1.5.1, which I'd
like to resolve before actually putting this out. :(
4350 does also seem pretty serious, and it's clearly a regression, so I'm
good with fixing that in 1.5.1 as well.
As such, I'm going to try and look into these items and re-spin the release
next week. Argh. Sorry for the inconvenience.
Thanks,
--Glen
Pétur Runólfsson wrote:
> Hi,
>
> May I suggest that http://issues.apache.org/jira/browse/AXIS2-4350 be fixed before the release?
>
> The effect of this bug is that web services that use ADB and use a wsdl provided by the user (not generated on the server) simply don't work at all. The fix is simple, and can be found in a comment on the issue.
>
> http://issues.apache.org/jira/browse/AXIS2-4471 seems to be a duplicate of this bug.
>
> Regards,
>
> Pétur Runólfsson
> ________________________________________
> From: Glen Daniels [glen@thoughtcraft.com]
> Sent: Wednesday, October 07, 2009 13:36
> To: axis-dev@ws.apache.org
> Subject: Re: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
>
> Ping! Please VOTE... or comment?
>
> --G
>
> Glen Daniels wrote:
>> 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
>>
>
> The content of this e-mail, together with any of its attachments, is for the exclusive and confidential use of the named addressee(s) and it may contain legally privileged and confidential information and/or copyrighted material. Any other distribution, use or reproduction without the sender's prior consent is unauthorized and strictly prohibited. If you have by coincidence, mistake or without specific authorization received this e-mail in error, please notify the sender by e-mail immediately, uphold strict confidentiality and neither read, copy, transfer, disseminate, disclose nor otherwise make use of its content in any way and delete the material from your computer.
>
> The content of the e-mail and its attachments is the liability of the individual sender, if it does not relate to the affairs of Betware.
> Betware does not assume any civil or criminal liability should the e-mail or it´s attachments be virus infected.
RE: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
Posted by Pétur Runólfsson <pe...@betware.com>.
Hi,
May I suggest that http://issues.apache.org/jira/browse/AXIS2-4350 be fixed before the release?
The effect of this bug is that web services that use ADB and use a wsdl provided by the user (not generated on the server) simply don't work at all. The fix is simple, and can be found in a comment on the issue.
http://issues.apache.org/jira/browse/AXIS2-4471 seems to be a duplicate of this bug.
Regards,
Pétur Runólfsson
________________________________________
From: Glen Daniels [glen@thoughtcraft.com]
Sent: Wednesday, October 07, 2009 13:36
To: axis-dev@ws.apache.org
Subject: Re: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
Ping! Please VOTE... or comment?
--G
Glen Daniels wrote:
> 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
>
The content of this e-mail, together with any of its attachments, is for the exclusive and confidential use of the named addressee(s) and it may contain legally privileged and confidential information and/or copyrighted material. Any other distribution, use or reproduction without the sender's prior consent is unauthorized and strictly prohibited. If you have by coincidence, mistake or without specific authorization received this e-mail in error, please notify the sender by e-mail immediately, uphold strict confidentiality and neither read, copy, transfer, disseminate, disclose nor otherwise make use of its content in any way and delete the material from your computer.
The content of the e-mail and its attachments is the liability of the individual sender, if it does not relate to the affairs of Betware.
Betware does not assume any civil or criminal liability should the e-mail or it´s attachments be virus infected.
Re: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
Posted by Anthony Elder <an...@uk.ibm.com>.
+1 from me.
...ant
Glen Daniels <gl...@thoughtcraft.com>
07/10/2009 14:36
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
Ping! Please VOTE... or comment?
--G
Glen Daniels wrote:
> 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
>
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Ping! Please VOTE... or comment?
--G
Glen Daniels wrote:
> 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
>
Re: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
Posted by Andreas Veithen <an...@gmail.com>.
+1
Andreas
On Thu, Oct 8, 2009 at 00:28, Nandana Mihindukulasooriya
<na...@gmail.com> wrote:
> +1
>
> regards,
> Nandana
>
> On Wed, Oct 7, 2009 at 5:17 PM, Amila Suriarachchi
> <am...@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 <de...@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/
>
Re: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
+1
regards,
Nandana
On Wed, Oct 7, 2009 at 5:17 PM, Amila Suriarachchi <
amilasuriarachchi@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 <de...@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/<http://people.apache.org/%7Egdaniels/stagingRepo/org/apache/axis2/distribution/1.5.1/>
>> >
>> > And the M2 repository with everything is at:
>> >
>> > http://people.apache.org/~gdaniels/stagingRepo<http://people.apache.org/%7Egdaniels/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/
>
Re: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
Posted by Amila Suriarachchi <am...@gmail.com>.
+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 <de...@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/<http://people.apache.org/%7Egdaniels/stagingRepo/org/apache/axis2/distribution/1.5.1/>
> >
> > And the M2 repository with everything is at:
> >
> > http://people.apache.org/~gdaniels/stagingRepo<http://people.apache.org/%7Egdaniels/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/
Re: [VOTE] [axis2] Release Axis2 1.5.1 (take 2)
Posted by Deepal jayasinghe <de...@gmail.com>.
+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