Bug 778393 (SOA-877) - WS Benchmark tests on SOA Platform show performance degradation compared to results on Tomcat
Summary: WS Benchmark tests on SOA Platform show performance degradation compared to r...
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-877
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossWS
Version: 4.2 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP03
Assignee: Jim Ma
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-26 06:42 UTC by nwallace
Modified: 2008-09-28 13:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-28 13:31:49 UTC
Type: Task


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777577 0 urgent CLOSED ESB performance bug blocking large queue backlog stress testing 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 777585 0 high CLOSED WS Benchmark tests on SOA Platform show performance degradation compared to results on Tomcat 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-877 0 None None None Never

Internal Links: 777577 777585

Description nwallace 2008-09-26 06:42:21 UTC
Date of First Response: 2008-09-28 09:31:49
project_key: SOA

Mark sais:

Once ESB 4.2.1 has GA-ed later today, our focus will turn to getting the platform out on time (17th of December). Amongst other things, one of the areas we could really do with help is on stressing the platform as a whole and checking that it does what it says it does! In HP we used to have something called a test-a-thon for each product release, where the entire middleware division would devote some time to stressing the next release of a product. How much time depended on the individuals and groups, but even a few hours often brought valuable feedback that assisted the product and QA. It would be good if you could plan with your teams some time over the next few weeks to go through the next beta of the platform, testing your own project's integration as well as others. If this works out and there's enough interest, maybe we could extend this to the individual projects.

Comment 1 nwallace 2008-09-26 06:42:21 UTC
Link: Added: This issue is related to SOA-85


Comment 2 nwallace 2008-09-26 06:42:52 UTC
Link: Added: This issue is related to SOA-93


Comment 3 nwallace 2008-09-26 06:43:28 UTC
Can we have confirmation that fixes are in place for 4.2CP03.

Comment 4 Mark Little 2008-09-28 13:31:49 UTC
EBWS is the preferred route now unless customers make specific requests.


Note You need to log in before you can comment on or make changes to this bug.