[Mono-bugs] [Bug 54148][Maj] New - Problem accessing axis Web Service

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 10 Feb 2004 10:31:47 -0500 (EST)


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 p.kullmann@arenae.ch.

http://bugzilla.ximian.com/show_bug.cgi?id=54148

--- shadow/54148	2004-02-10 10:31:47.000000000 -0500
+++ shadow/54148.tmp.10574	2004-02-10 10:31:47.000000000 -0500
@@ -0,0 +1,49 @@
+Bug#: 54148
+Product: Mono/Class Libraries
+Version: unspecified
+OS: other
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: Sys.Web.Services
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: p.kullmann@arenae.ch               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Problem accessing axis Web Service
+
+(This could be related to Bug 51893 and possibly to Bug 51846).
+
+The following happens in Mono 0.30 on Redhat 9 (Install from RPMs). 
+
+I have a simple web service hosted on axis/tomcat that returns a string. I
+call the service through a generated proxy class (generated by mono wsdl).
+The problem is, sometimes it works and sometimes it doesn't. If it doesn't
+work, I get the following exception:
+
+Unhandled Exception: System.Xml.XmlException: Document element did not appear.
+in <0x00262> System.Xml.XmlTextReader:Read ()
+in <0x00097> System.Xml.XmlReader:MoveToContent ()
+in <0x00013> System.Web.Services.Protocols.WebServiceHelper:ReadSoapMessage
+(System.Xml.XmlTextReader,System.Web.Services.Protocols.SoapTypeStubInfo,System.Web.Services.Description.SoapBindingUse,System.Xml.Serialization.XmlSerializer,object&,System.Web.Services.Protocols.SoapHeaderCollection&)
+in <0x00264>
+System.Web.Services.Protocols.SoapHttpClientProtocol:ReceiveResponse
+(System.Net.WebResponse,System.Web.Services.Protocols.SoapClientMessage,System.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,System.Web.Services.Protocols.SoapExtension[])
+in <0x0021f> System.Web.Services.Protocols.SoapHttpClientProtocol:Invoke
+(string,object[])
+in <0x0006b> (wrapper remoting-invoke-with-check)
+System.Web.Services.Protocols.SoapHttpClientProtocol:Invoke (string,object[])
+in <0x00036> .ProgressWrapperService:Test ()
+in <0x000d5> .Test:Main (string[])
+
+The same code works with MS .net.
+ 
+I can't deploy the web service to the public, but I will attach two
+ethereal capture files, one for a call that went ok and one for a failure.