[Mono-bugs] [Bug 59081][Nor] New - MONO Beta 1 Web Service bug parsing integer string?
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Tue, 25 May 2004 21:08:04 -0400 (EDT)
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by davidandrewtaylor@hotmail.com.
http://bugzilla.ximian.com/show_bug.cgi?id=59081
--- shadow/59081 2004-05-25 21:08:04.000000000 -0400
+++ shadow/59081.tmp.3848 2004-05-25 21:08:04.000000000 -0400
@@ -0,0 +1,119 @@
+Bug#: 59081
+Product: Mono: Class Libraries
+Version: unspecified
+OS: Red Hat 9.0
+OS Details:
+Status: NEW
+Resolution:
+Severity: 002 Two hours
+Priority: Normal
+Component: Sys.Web.Services
+AssignedTo: mono-bugs@ximian.com
+ReportedBy: davidandrewtaylor@hotmail.com
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL:
+Cc:
+Summary: MONO Beta 1 Web Service bug parsing integer string?
+
+Description of Problem:
+System.Format exception when calling web service. Please note that due
+to the number of bugs impacting me in the MONO Beta 1 Web Services stack
+(and the HTTP Chunked encoding bug), I cannot be 100% sure this isnt one
+of the other bugs. I will re-test this when Beta2 comes out.
+
+Sadly this web service is not yet exposed through our firewall, but I
+have included a TCPDump. Note that the first 2 requests/responses in the
+TCPDump failed due to other MONO bugs I have posted. So please look at
+the very end of the TCPDump because ONLY the last web service call is
+relevant to this bug report (and produced the exception shown).
+
+I have attached:
+a) TcpDump
+b) Test case (which you will not be able to run because it is behind our
+firewall)
+c) XML Response returned from the server in case that helps.
+
+Steps to reproduce the problem:
+1. Call web service
+Actual Results:
+System.FormatException: Input string was not in the correct format.
+in <0x000e8> System.Int32:Parse
+(string,System.Globalization.NumberStyles,System.IFormatProvider)
+in <0x00013> System.Int32:Parse (string,System.IFormatProvider)
+in <0x00017> System.Xml.XmlConvert:ToInt32 (string)
+in <0x00294> System.Xml.Serialization.XmlCustomFormatter:FromXmlString
+(System.Xml.Serialization.TypeData,string)
+in <0x00098>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:GetValueFromXml
+String
+(string,System.Xml.Serialization.TypeData,System.Xml.Serialization.XmlType
+Mapping)
+in <0x0015f>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadPrimitiveVa
+lue (System.Xml.Serialization.XmlTypeMapElementInfo)
+in <0x00097>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadObjectEleme
+nt (System.Xml.Serialization.XmlTypeMapElementInfo)
+in <0x022a0>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadMembers
+(System.Xml.Serialization.ClassMap,object,bool,bool)
+in <0x00057>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadClassInstan
+ceMembers (System.Xml.Serialization.XmlTypeMapping,object)
+in <0x00207>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadClassInstan
+ce (System.Xml.Serialization.XmlTypeMapping,bool,bool)
+in <0x00064>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadObject
+(System.Xml.Serialization.XmlTypeMapping,bool,bool)
+in <0x00021> ReaderCallbackInfo:ReadObject ()
+in <0x00041> (wrapper delegate-invoke)
+System.MulticastDelegate:invoke_object ()
+in <0x00264>
+System.Xml.Serialization.XmlSerializationReader:ReadReferencedElement
+(string,string)
+in <0x00068>
+System.Xml.Serialization.XmlSerializationReader:ReadReferencedElement ()
+in <0x00051>
+System.Xml.Serialization.XmlSerializationReader:ReadReferencedElements ()
+in <0x00355>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadMessage
+(System.Xml.Serialization.XmlMembersMapping)
+in <0x000f2>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadRoot ()
+in <0x00086> System.Xml.Serialization.XmlSerializer:Deserialize
+(System.Xml.Serialization.XmlSerializationReader)
+in <0x00056> System.Xml.Serialization.XmlSerializer:Deserialize
+(System.Xml.XmlReader)
+in <0x000fd>
+System.Web.Services.Protocols.WebServiceHelper:ReadSoapMessage
+(System.Xml.XmlTextReader,System.Web.Services.Protocols.SoapTypeStubInfo,S
+ystem.Web.Services.Description.SoapBindingUse,System.Xml.Serialization.Xml
+Serializer,object&,System.Web.Services.Protocols.SoapHeaderCollection&)
+in <0x00335>
+System.Web.Services.Protocols.SoapHttpClientProtocol:ReceiveResponse
+(System.Net.WebResponse,System.Web.Services.Protocols.SoapClientMessage,Sy
+stem.Web.Services.Protocols.SoapExtension[])
+in <0x0007d> (wrapper remoting-invoke-with-check)
+System.Web.Services.Protocols.SoapHttpClientProtocol:ReceiveResponse
+(System.Net.WebResponse,System.Web.Services.Protocols.SoapClientMessage,Sy
+stem.Web.Services.Protocols.SoapExtension[])
+in <0x002ce> System.Web.Services.Protocols.SoapHttpClientProtocol:Invoke
+(string,object[])
+in <0x00056>
+NotificationService.DomainNameMonitoringService.DomainNameMonitoringWSServ
+ice:getAllTriggers (string)
+in <0x00058> (wrapper remoting-invoke-with-check)
+NotificationService.DomainNameMonitoringService.DomainNameMonitoringWSServ
+ice:getAllTriggers (string)
+....etc
+
+Expected Results:
+Should have printed the number of items returned.
+
+How often does this happen?
+Seems to happen whenever I can get through other MONO Beta 1 bugs to get
+to this point; ie I need to run the test case a few times due to a
+problem MONO has with chunked encoding. When I get past the chunked
+encoding problem I get this problem ;-)