Mailing-List: contact c-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <c-dev@axis.apache.org>
Message-ID: <154993.110961277802469932.JavaMail.jira@thor>
Date: Tue, 29 Jun 2010 05:07:49 -0400 (EDT)
From: "Damitha Kumarage (JIRA)" <jira@apache.org>
To: c-dev@axis.apache.org
Subject: [jira] Updated: (AXIS2C-1326) Improvment to Axis2/C client side
 thread pool
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AXIS2C-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Damitha Kumarage updated AXIS2C-1326:
-------------------------------------

    Fix Version/s: Next Version

> Improvment to Axis2/C client side thread pool
> ---------------------------------------------
>
>                 Key: AXIS2C-1326
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1326
>             Project: Axis2-C
>          Issue Type: Improvement
>          Components: core/clientapi
>            Reporter: Damitha Kumarage
>             Fix For: Next Version
>
>
> Currently Axis2/C client engine don't make use of the thread pool facility even if we pass one.
> It just request threads from the thread pool and may exhaust all available threads until
> blocking the main thread at some point waiting for new thread which is not what
> the user desire by passing a thread pool. This limitation could be addressed by not requesting
> threads from the passed thread pool but instead passing the job to the thread pool(probably thread
> method and data). Then the thread pool handle the jobs without never blocking the main thread.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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