DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8824>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8824 Axis Beta 2. Soap call method parameters are assigned to the wrong instance of the server method when the clients load is high Summary: Axis Beta 2. Soap call method parameters are assigned to the wrong instance of the server method when the clients load is high Product: Axis Version: beta-1 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: Serialization/Deserialization AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When there are a lot of clients calling the same exposed server methods (>500 in my case) some of the values for the method parameters are assign to the incorrect instance of the server method. For example I have a method called "SyncSvr.CreateSyncID(String id, String params)" where id is a 32 digit unique identifier for each client. What happens if that in an small percentage of the calls I will receive the following: 1. In one instance of the server method two 32 digit ID's concatenated. 2. In the second intance I will receive null as the ID. I started working with the Axis code and by printing messages I found out that in some cases the "BaseDeserializerFactory.getGeneralPurpose()" method returns twice the same instance of the "SimpleDeserializer" parser which is used to parse the method parameters. Because the same instance is used to parse the parameters of two different soap calls some of the parameters are assign to the wrong instance of the server method. By serializing the "BaseDeserializerFactory.getGeneralPurpose()" Axis method the problem seems to be fixed. I will be happy to provide you with more information, test cases and trace files uppon your request. My email is [EMAIL PROTECTED]
