Petals BC SOAP

Performance problem on first call

Details

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

    After the SOAP BC has been started, at the first SOAP call from outside, it will load the WSDL of the consumes, and for this, it will lock on the AxisService (there is one per Consumes).

    So if 100 messages arrives at ounce, they will all wait and it will strongly degrade performances.

    There is no need for doing so: the wsdl (and other things) can simply be loaded when the SU is deployed.

    Show
    After the SOAP BC has been started, at the first SOAP call from outside, it will load the WSDL of the consumes, and for this, it will lock on the AxisService (there is one per Consumes). So if 100 messages arrives at ounce, they will all wait and it will strongly degrade performances. There is no need for doing so: the wsdl (and other things) can simply be loaded when the SU is deployed.
  • Environment:
    -

Activity

People

Dates

  • Created:
    Fri, 11 Sep 2015 - 16:59:57 +0200
    Updated:
    Tue, 15 Sep 2015 - 17:38:26 +0200
    Resolved:
    Tue, 15 Sep 2015 - 17:38:26 +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.