Details
-
Type:
Task
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 1.0.3
-
Fix Version/s: 2.0
-
Component/s: Analysis, Version Compatibility
-
Labels:None
-
Rice Module:KIM
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
Description
Rice currently defaults to java serialization for remoting... instead of SOAP. This is primarily due to performance reason.
One issue with using serialization is that switching JVM's could cause differences in the way objects are serialized. ex. Java 5 client connecting to java 6 server.
We need to run some speed tests to see which is faster, soap or searial for remoted services.
For this particular case we upgrading the recipe sample app to spring 1.0.3 (snapshot) and tested that against the standalone server.
We created a simple servlet inside the sample app. All this servlet does is take in a request param to switch the underlying service call to use serialization or soap remoting.
Our test calls the identityService.lookupEntityInfo with an empty map. This will return a relatively large payload.
We're testing:
Soap vs Java Serialization
Oracle vs MySql
Soap Security On/off
Attachments
Activity
To turn off security on the soap service, this goes in the config file:
<param name="kim.soapExposedService.jaxws.security">false</param>
re-assigning this back to you to determine next action or if I or someone else need to do anything further.
Probably all I need to do here to follow up is to ensure our results our documented and accessible somewhere. I'll probably get to that here in the next few weeks.
I'm going to close this issue out. I think this plus the linked spreadsheet serve as documentation for the research done here.
Closing since these items are now in the release notes.
There seems to be very little difference in speed between java serialization and soap.