-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: EAP_EWP 5.1.0
-
Fix Version/s: EAP_EWP 5.1.0
-
Component/s: Web Services
-
Labels:None
-
Environment:
Both native and cxf stack for EAP 5.1.x
-
Affects:Documentation (Ref Guide, User Guide, etc.)
Hi Aleessio.
During my perf testing I found that EAP 5.1.x have bigger problems than EAP 5.0.1 with transfering many big files without MTOM enabled.
I know that for this should be MTOM enabled, but there can be customers who don't have this enabled and haven't yet meet this problem. After updating to "tuned" 5.1 they could be unlucky and meet this problem.
I simulated 200 clients, each sending 100 requests, file size was 752K (logo-big.jpg).
On EAP 5.0.1 there was only one error response, so the ended in the right time. (http://hudson.qa.jboss.com/hudson/view/EAP51-Perf/job/eap-501-perf-ws-native-load/).
Tests on EAP 5.1.x (daily build, one week old) failed for both native and cxf stack. Server log says OutOfMemoryError: Java heap space and OutOfMemoryError: GC overhead limit exceeded. The main issue is high relative time spent in GC, which is at the end 100%. http://hudson.qa.jboss.com/hudson/view/EAP51-Perf/job/eap-510-perf-ws-native-load/6/console-cluster06/
It's not blocker as MTOM should be used in this case, but please consider some mechanism which could prevent AS crash caused by sending big files.
Test is called BigFileNoMTOMTransferTest and can be find in QA repo:
https://svn.devel.redhat.com/repos/jboss-qa/load-testing/apps/ws-test/trunk/src/test/java/org/jboss/test/ws/jaxws/benchmark/test/mtom/
