Petals BC SOAP

Web-service client pooling does not work correctly

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 4.1
  • Fix Version/s: 4.2.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    As described here: http://amilachinthaka.blogspot.fr/2010/01/improving-axis2-http-transport-client.html, the pool of web-service client is constrained by the number of requests authorized by MultiThreadedHttpConnectionManager. Now we can execute more than 2 web-service requests on the same external server of web-services.

    So the web-service client pooling MUST be reviewed to retrieve performances available with the BC Soap 4.0.x

    Show
    As described here: http://amilachinthaka.blogspot.fr/2010/01/improving-axis2-http-transport-client.html, the pool of web-service client is constrained by the number of requests authorized by MultiThreadedHttpConnectionManager. Now we can execute more than 2 web-service requests on the same external server of web-services. So the web-service client pooling MUST be reviewed to retrieve performances available with the BC Soap 4.0.x
  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Tue, 15 May 2012 - 17:17:06 +0200

In previous version, the max number of web-service clients is defined by the max size of the message exchange processor thread pool.
To prevent unneeded resources consumption, the max number of web-service clients should be customizable:

  • parameter location: component JBI descriptor
  • parameter name: "ws-clients-pool-size-max",
  • default value: value of the parameter "cdk:processor-max-pool-size".
Show
Christophe DENEUX added a comment - Tue, 15 May 2012 - 17:17:06 +0200 In previous version, the max number of web-service clients is defined by the max size of the message exchange processor thread pool. To prevent unneeded resources consumption, the max number of web-service clients should be customizable:
  • parameter location: component JBI descriptor
  • parameter name: "ws-clients-pool-size-max",
  • default value: value of the parameter "cdk:processor-max-pool-size".
Hide
Permalink
Christophe DENEUX added a comment - Fri, 18 May 2012 - 12:13:17 +0200

Fixed in trunk

Show
Christophe DENEUX added a comment - Fri, 18 May 2012 - 12:13:17 +0200 Fixed in trunk
Hide
Permalink
Christophe DENEUX added a comment - Wed, 13 Jun 2012 - 17:26:02 +0200 - edited

Reopen because a regression was introduced. No more timeout is managed in provide mode. Thanks to the continuous integration !

Show
Christophe DENEUX added a comment - Wed, 13 Jun 2012 - 17:26:02 +0200 - edited Reopen because a regression was introduced. No more timeout is managed in provide mode. Thanks to the continuous integration !
Hide
Permalink
Christophe DENEUX added a comment - Wed, 13 Jun 2012 - 17:51:08 +0200

Fixed in trunk

Show
Christophe DENEUX added a comment - Wed, 13 Jun 2012 - 17:51:08 +0200 Fixed in trunk

People

Dates

  • Created:
    Tue, 24 Apr 2012 - 17:27:12 +0200
    Updated:
    Wed, 13 Jun 2012 - 17:51:08 +0200
    Resolved:
    Wed, 13 Jun 2012 - 17:51:08 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.