Re: Sandesha 2 test case failures.

[Andreas Veithen <an...@gmail.com>]

It looks like there are still issues with Sandesha2 and the connection
handling fixes in Axis2. I'm currently unable to successfully execute
the Sandesha2 test suite with Axis2 1.5.x. One problem seems to be
that when WS-RM is enabled, the server may return a 200 response, even
if useSeparateListeners=true. In that case, nobody cleans up the
connection. Actually, if useSeparateListeners=true, then the HTTP
transport doesn't even store the HttpMethod object in the message
context, so that the connection will not be released, even if somebody
calls TransportSender#cleanup(). What I don't understand yet is why
this doesn't cause issues when using Sandesha2 with Axis2 trunk...

Andreas

On Sat, Sep 25, 2010 at 21:08, Andreas Veithen
<an...@gmail.com> wrote:
> I fixed an issue in the HTTP transport that prevented it from properly
> releasing the connection in some scenarios with 202 responses. See
> r1001279. The Sandesha2 test suite now completes successfully.
>
> Andreas
>
> On Mon, Sep 20, 2010 at 17:45, Andrew K Gatford <GA...@uk.ibm.com> wrote:
>> Hi,
>>
>> I've been investigating the unit test failures for Sandesha2.
>> I've traced the problem to an Axis2 commit
>>
>> Revision: 992877
>> Author: veithen
>> Date: 20:38:56, 05 September 2010
>> Message:
>> Attempt to solve both the CLOSE_WAIT issue and AXIS2-4751 on the trunk:
>> * Reverted r963710 (Jarek's second change for AXIS2-4751 on the trunk) to
>> get back to the correct baseline for merging r790721.
>> * Merged r790721 (CLOSE_WAIT issue) from the 1.5 branch back to the trunk.
>> This had never been done, presumably because it caused issues in Rampart
>> (that were actually due to a bug in Rampart, fixed in r992868).
>> * Merged r824340 (Another change to AbstractHTTPSender that Glen only
>> applied to the 1.5 branch) to the trunk.
>> * Merged r958718 (Jarek's original change for AXIS2-4751 on the 1.5 branch)
>> to the trunk.
>>
>> Modified :
>> /axis/axis2/java/core/trunk/modules/transport/http/src/org/apache/axis2/transport/http/AbstractHTTPSender.java
>>
>>
>> The exact problem was caused by the change to AbstractHTTPSender.
>> The uncommenting of the line
>>
>>                if (connManager == null) {
>>                     log.trace("Making new ConnectionManager");
>>                     connManager = new MultiThreadedHttpConnectionManager();
>>
>> //configContext.setProperty(HTTPConstants.MULTITHREAD_HTTP_CONNECTION_MANAGER,
>>                     //                          connManager);
>>                 }
>>
>> I commented the line out again as above and the sandesha2 tests pass again.
>> This may require a change to the RMScenariosTest but need some advice on
>> what to do - or to comment out the line above again.
>>
>> Any suggestions ?
>>
>> Andrew Gatford
>> WebSphere Development Manager
>>
>> IBM United Kingdom Limited,
>> MP211, Hursley Park, Winchester, SO21 2JN
>> Telephone :
>> Internal (7) 245743
>> External 01962 815743
>> Internet : gatfora@uk.ibm.com
>>
>>
>> ________________________________
>>
>> 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
>>
>>
>>
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org