This one has been a real pain in the neck. Every now and then our
application fails with the following message

<message>
************** Exception Text **************
System.Net.WebException: The request failed with HTTP status 502: Bad
Gateway.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
Message message, WebResponse response, Stream responseStream)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at FileManager.Proxy.CheckoutWebService.Checkout(String who, Boolean force)
at GridEditor.MainForm.OnCheckout()
at GridEditor.MainForm._toolbar_ButtonClick(Object sender,
ToolBarButtonClickEventArgs e)
at System.Windows.Forms.ToolBar.OnButtonClick(ToolBarButtonClickEventArgs e)
</message>

This is the proxy code with the offending method:
<src>
//--------------------------------------------------------------------------
----
// <autogenerated>
//     This code was generated by a tool.
//     Runtime Version: 1.0.3705.288
//
//     Changes to this file may cause incorrect behavior and will be lost if
//     the code is regenerated.
// </autogenerated>
//--------------------------------------------------------------------------
----

//
// This source code was auto-generated by wsdl, Version=1.0.3705.288.
//
namespace FileManager.Proxy {
    using System.Diagnostics;
    using System.Xml.Serialization;
    using System;
    using System.Web.Services.Protocols;
    using System.ComponentModel;
    using System.Web.Services;


    /// <remarks/>
    [System.Diagnostics.DebuggerStepThroughAttribute()]
    [System.ComponentModel.DesignerCategoryAttribute("code")]

[System.Web.Services.WebServiceBindingAttribute(Name="CheckoutWebServiceSoap
", Namespace="http://www.rederecord.com.br/checkout";)]
    public class CheckoutWebService :
System.Web.Services.Protocols.SoapHttpClientProtocol {

        /// <remarks/>
        public CheckoutWebService() {
            this.Url = "http://127.0.0.1/webservice.aspx";;
        }

  public CheckoutWebService(string url)
  {
   this.Url = url;
  }

        /// <remarks/>

[System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://www.reder
ecord.com.br/checkout/Checkout",
RequestNamespace="http://www.rederecord.com.br/checkout";,
ResponseNamespace="http://www.rederecord.com.br/checkout";,
Use=System.Web.Services.Description.SoapBindingUse.Literal,
ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Wrapped)]
        public DocumentVersion Checkout(string who, bool force) {
            object[] results = this.Invoke("Checkout", new object[] {
                        who,
                        force});
            return ((DocumentVersion)(results[0]));
        }
}


    /// <remarks/>

[System.Xml.Serialization.XmlTypeAttribute(Namespace="http://www.rederecord.
com.br/checkout")]
    public class DocumentVersion {

        /// <remarks/>
        public long Version;

        /// <remarks/>

[System.Xml.Serialization.XmlElementAttribute(DataType="base64Binary")]
        public System.Byte[] Data;
    }
}
</src>

The error only occurs in Windows 98. OS upgrades are not an option right
now. :-)

Anyone has seen this before? Any clues for what might be causing it?

We are kinda lost here.

Thanks in advance for any help!
Rodrigo

Reply via email to