Bug 830731 - Performance issue with creating external web service client
Summary: Performance issue with creating external web service client
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: riftsaw
Version: 5.3.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER5
: 5.3.0 GA
Assignee: Gary Brown
QA Contact: Ivo Bek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-11 10:11 UTC by Gary Brown
Modified: 2014-10-15 17:25 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-15 17:25:46 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RIFTSAW-497 0 Major Resolved Performance issue in WebServiceClient 2012-07-24 11:35:59 UTC

Description Gary Brown 2012-06-11 10:11:26 UTC 
Description of problem:

Performance regression has been introduced between 5.2.GA and the latest engineering build for 5.3. The area of concern identified by Tom Cunningham is the WebServiceClient.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Deploy simple invoke quickstart
2. Run 'x' tests
  
Actual results:


Expected results:


Additional info:
Comment 1 JBoss JIRA Server 2012-06-11 10:21:21 UTC 
Gary Brown <gary.pi4tech> updated the status of jira RIFTSAW-497 to Resolved
Comment 2 Gary Brown 2012-06-11 10:25:29 UTC 
Fixed for riftsaw 2.3.5.Final tag.
Comment 3 Suz 2012-07-17 00:38:01 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
There was a performance issue when creating an external web service client. Users who attempted to run a quickstart to accomplish this encountered performance problems. This was due to caching dispatcher issues. The problem has been addressed and performance should no longer be compromised in these instances.
Comment 4 Ivo Bek 2012-07-24 11:35:53 UTC 
Verified in JBoss SOA-P 5.3.0.CR1
Note You need to log in before you can comment on or make changes to this bug.