axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <>
Subject [jira] Resolved: (AXIS-2362) Re-use of MultiThreadedConnectionManager in CommonsHTTPSender
Date Sat, 13 May 2006 04:17:09 GMT
     [ ]
Jarek Gawor resolved AXIS-2362:

    Resolution: Fixed

The CommonsHTTPSender was updated to reuse the MultiThreadedConnectionManager.

> Re-use of MultiThreadedConnectionManager in CommonsHTTPSender
> -------------------------------------------------------------
>          Key: AXIS-2362
>          URL:
>      Project: Apache Axis
>         Type: Bug

>   Components: Basic Architecture
>     Versions: 1.2, 1.2.1
>     Reporter: Amanda Hopgood

> When using CommonsHTTPSender then a new MultiThreadedConnectionManager is created for
each instance. This means that the MultiThreadedConnectionManager is unique per Service object,
and this is preventing our connections being re-used. The MultiThreadedConnectionManager should
be able to be shared between different HTTPClient objects, and this request is to alter CommonsHTTPSender
so that a single instance of MultiThreadedConnectionManager is created and used by many instances
of CommonsHTTPSender.
> In our application we have a Service object per calling thread, and so with the current
implementation there is one MultiThreadedConnectionManager per thread, and so we are getting
more connections then we really desire.
> The reason we have a Service object per calling thread, was because we have seen ConcurrentModificationExceptions
if we perform load tests whilst sharing Service objects over threads, i.e.
> java.util.ConcurrentModificationException
> at java.util.WeakHashMap$HashIterator.nextEntry(
> at java.util.WeakHashMap$
> at 
> org.apache.axis.attachments.ManagedMemoryDataSource.delete(
> org.apache.axis.attachments.AttachmentsImpl.writeContentToStream(

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message