tracker issue : CF-3562712

select a category, or use search below
(searches all categories and all time range)
Title:

503 Errors - Server Stops Responding to Requests for SOAP Web Services

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/

Reporter/Name(from Bugbase): Ben Rosamond / Ben Rosamond (brosamond)

Created: 05/17/2013

Components: Web Services

Versions: 9.0.1

Failure Type: Crash

Found In Build/Fixed In Build: 9.0.1 /

Priority/Frequency: Critical / All users will encounter

Locale/System: English / Win 2008 Server R2 64 bit

Vote Count: 0

Problem Description:

From time to time, we've seen instances become entirely unresponsive to any and all SOAP service requests.  When trying to browse to the WSDL, it simply returns a 503 error.  When this triggers it happens to all services across all applications on that instance and the only way we've been able to resolve it is by restarting that instance.  We haven't been able to identify what might possibly be causing it, but it happens fairly rarely and we've seen it occurring for years now.  It happened to the same instance twice this week.  Other instances on that server are unaffacted.

Steps to Reproduce:

Not certain what causes it stop responding, but once it does, attempt to invoke a method of the web service or browse to the WSDL file in a browser

Actual Result:

503 - Service Unavailable Message is returned

Expected Result:

Normal web service processing

Any Workarounds:

Restart that instance

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3562712

Deployment Phase:	Release Candidate

External Customer Info:
External Company:  
External Customer Name: brosamond
External Customer Email:  
External Test Config: My Hardware and Environment details:



Has occurred at 2 separate hosting facilities on varied hardware.  Win Server 2k8 R2 Standard 64-bit, IIS 7.5



Multi-Instance, Non-Clustered

Attachments:

Comments:

I'd settle for a method to resolve this situation when it occurs without having to restart the instance. We primarily run login-protected applications with a long application load time, so having to trigger a restart mid-day is extremely aggravating for our users.
Comment by External U.
15355 | May 17, 2013 01:12:15 PM GMT
The information provided is less for us to repro the case and to look into the issue further. Please provide us code snippet to repro the case and also (very important) the log file content generated just before the instance went unresponsive. This would help us to find the issue. Thanks.
Comment by Akhila K.
15356 | December 22, 2013 03:27:05 AM GMT
This bug is inactive for a while now, hence closing the same. Incase if user is still facing the issue and wants it to be fixed, please let us know and provide required information. We will look into it.Thanks.
Comment by Akhila K.
15357 | December 03, 2014 02:23:06 AM GMT