HTTP connection management in Axis

(New thread for discussing $subject.) So, for 1.6 it would be great if we could finalize our HTTP management stuff, and have a clean set of APIs / patterns that we can have documented and FAQ'ed. This thread can break off into sub-threads if desired, but things I think we need to get right includ

Re: svn commit: r992877 - in /axis/axis2/java/core/trunk: ./ modules/adb-codegen/test-resources/testsuite/ modules/adb-codegen/test/org/apache/axis2/schema/particlemaxoccurs/ modules/kernel/src/org/ap

Hi Jarek, On 9/17/2010 11:06 AM, Jarek Gawor wrote: > An attempt was made in the 1.5 branch to ensure connection pool is > reused between the calls but that reused HttpClient instance instead > of HttpConnectionManager instance... and you know the rest. Not to beat a dead horse :), but AFAIK Oleg

Re: svn commit: r992877 - in /axis/axis2/java/core/trunk: ./ modules/adb-codegen/test-resources/testsuite/ modules/adb-codegen/test/org/apache/axis2/schema/particlemaxoccurs/ modules/kernel/src/org/ap

On Fri, Sep 17, 2010 at 7:55 AM, Amila Suriarachchi wrote: > > >> >> See https://issues.apache.org/jira/browse/AXIS2-4751 for details. The >> thread safety problem was solved by not reusing HttpClient instance. > > As I told, this bug is reported with Axis2 1.5.1 not with trunk. hence this > issue

Re: svn commit: r992877 - in /axis/axis2/java/core/trunk: ./ modules/adb-codegen/test-resources/testsuite/ modules/adb-codegen/test/org/apache/axis2/schema/particlemaxoccurs/ modules/kernel/src/org/ap

Hi Amila, Jarek, On 9/17/2010 7:55 AM, Amila Suriarachchi wrote: > As I told, this bug is reported with Axis2 1.5.1 not with trunk. hence this > issue is not relevant. The issue isn't just 4751, Amila - the larger issues were 935, 2883, and others (search for CLOSE_WAIT). When we used the old (p

Re: svn commit: r992877 - in /axis/axis2/java/core/trunk: ./ modules/adb-codegen/test-resources/testsuite/ modules/adb-codegen/test/org/apache/axis2/schema/particlemaxoccurs/ modules/kernel/src/org/ap

On Fri, Sep 17, 2010 at 10:41 AM, Jarek Gawor wrote: > On Thu, Sep 16, 2010 at 3:47 AM, Amila Suriarachchi > wrote: > > > >> The key idea of these changes were to ensure that connection reuse is > >> done properly (in thread safe way). > > > > Can you please explain this problem with the code wi

WS- Security question

Hi, Could you please clarify why we need password digest when we can't un-digest it in the server side? I am now using policy based security but I get "*Missing wsse:Security header in request" error. What could be the possible reason?* * * *I am using