Resolution: Won't Fix or Usage Issue
Affects Version/s: 2.2.8 (EE only)
Fix Version/s: None
Component/s: Examples / Tutorials
MULE-3617 Async CXF loanbroker with 100 loan requests fails MULE-186 LoanBroker Example On mule-1.0-rc2 CouldNotRouteOutboundMessageException MULE-4259 NullPointerException in CxfMessageDispatcher when executing loanbroker [cxf, asynchrounous] for 100 requests MULE-4608 Loanbroker example not working MULE-3549 Loanbroker example using CXF throws exceptions MULE-5704 loanbroker-simple example's README.txt has a dead link MULE-555 LoanBroker randomly breaks Axis with IOException MULE-5017 loanbroker tests fail in 3.0-RC1 example MULE-3656 Loanbroker BPM throws NullPointerException MULE-5027 LoanBroker example: Result does not get returned to the client
Looks like the loanbroker example is taking much more time to process each request than in 2.2.7.
For example, using the ESN version with CXF asynchronous version, optino 2 (sending 1000 request)
finish without problems in 2.2.7 takes arounf 7-8 seconds, but in 2.2.8 takes around 20 seconds
and at the end of the run there is a message in the log like this one:
"Wrapper Process has not received any CPU time for 18 seconds. Extending timeouts."
Sending more than 100 request produces a restart of the instance because of the wrapper having a timeout:
"JVM requested a restart.
Wrapper Process has not received any CPU time for 31 seconds. Extending timeout
Launching a JVM..."
Same issue is present in different flavors of the example (ESN axis and ESB)
This performance degradation needs to be investigated.