[
https://issues.apache.org/jira/browse/RAMPART-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
S.Uthaiyashankar resolved RAMPART-298.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Patch applied in revision 1055819.
> Client using SymmetricBinding runs slower and slower as more requests are made
> ------------------------------------------------------------------------------
>
> Key: RAMPART-298
> URL: https://issues.apache.org/jira/browse/RAMPART-298
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Affects Versions: 1.5
> Reporter: Dennis Sosnoski
> Assignee: S.Uthaiyashankar
> Fix For: 1.6.0
>
> Attachments: axis2-symm-bug.zip, performance-comparison.pdf,
> RAMPART-298.diff, rampart-receiver.pdf
>
>
> Tests run with Axis2/Rampart client talking to an Axis2/Rampart server using
> SymmetricBinding get slower and slower as the number of requests goes up.
> Here are some typical figures:
> 100 requests - 8.0 seconds
> 200 requests - 19.1 seconds
> 300 requests - 40.9 seconds
> 400 requests - 77.0 seconds
> 500 requests - 134.4 seconds
> Since this appears to be strictly a function of the number of requests run
> using a single client, I suspect the Rampart client code is doing something
> like caching all the generated secret keys and then doing a linear search to
> find the one referenced in a response.
> To demonstrate the problem using the attached code, first edit the build
> properties to set the path to the Axis2 installation, then build using "ant"
> command, upload .aars to server, and run test using "ant run-encr". The
> number of requests can be changed in the build.properties file before each
> test run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
