Hi Asankha,
From what I've seen, most of the performance problems with
Axis2/Rampart lay outside of WSS4J. Rampart could certainly do a better
job of optimizing its use of WSS4J - for example by not going through
the overhead of constructing an AXIOM DOM representation of the message
and
to a static
configuration)
thoughts?
Martin Gainty
__
please do not alter/modify or disrupt this transmission. Thank You
Date: Thu, 11 Feb 2010 22:19:08 +1300
From: d...@sosnoski.com
To: axis-dev@ws.apache.org
Subject: Re: Axis2/Rampart WS
hi Asankha,
how many messages you sent for one scenario test?
i.e for eg 500b message with 640 threads
In the very first scenario upto 640 concurrency level both have same through
put while for 1280
threads UE has a sudden increment and for 2560 other ESB has a relatively
high change. What could
Hi Amila
how many messages you sent for one scenario test?
i.e for eg 500b message with 640 threads
This depends on the concurrency, and can be found exactly by looking at
the script used to run the load test. For example, when 20 users were
being used, the iterations were 1000, while for 2560
On Thu, Feb 11, 2010 at 10:23 PM, Asankha C. Perera asan...@apache.orgwrote:
Hi Amila
how many messages you sent for one scenario test?
i.e for eg 500b message with 640 threads
This depends on the concurrency, and can be found exactly by looking at
the script used to run the load test. For
Hi Amila
In the very first scenario upto 640 concurrency level both have
same through put while for 1280 threads UE has a sudden increment
and for 2560 other ESB has a relatively high change. What could be
the reason for that?
Which set are you referring to - the
Hi Prabath,
I just tried a couple of simple tests, using the signing+encryption
policy on the server and trying different variations of policy
(including no policy) on the client with both Metro and Axis2. All the
client variations were rejected by the server in both cases, so at least
at
Hi Dennis;
Nice analysis...
Does Metro do policy based validations?
Rampart does validations at two levels - first validation at the message
level with info gathered from the message it self - and then validate
the entire message with the defined policy.
If somebody skips the second step -
