J
jim
If our database goes offline, our C# Web Service will throw a
System.Web.Services.Protocols.SoapException even when the database has
returned. As a result, unless we restart IIS, our C# Web Service
never comes back up.
(We're using Oracle as the database -- however, that shouldn't
matter.)
Anyone else seen this issue and can suggest a good solution?
Please reply...
Jim
System.Web.Services.Protocols.SoapException even when the database has
returned. As a result, unless we restart IIS, our C# Web Service
never comes back up.
(We're using Oracle as the database -- however, that shouldn't
matter.)
Anyone else seen this issue and can suggest a good solution?
Please reply...
Jim