Bug 1441086 - 50% of webcalls ends up in 503 Service Unavailable
Summary: 50% of webcalls ends up in 503 Service Unavailable
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Networking
Version: 3.x
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: Meng Bo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-11 08:15 UTC by micha.van.santvoort
Modified: 2017-04-17 17:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-17 17:54:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description micha.van.santvoort 2017-04-11 08:15:53 UTC
50% of webcalls end up in:

503 Service Unavailable
No server is available to handle this request. 


How reproducible:


Steps to Reproduce:
1. create app, add wildfly 10.1, add mysql
2. goto browser with http://servicename-appname.44fs.preview.openshiftapps.com
3. press CTRL-F5

Actual results:
50% gives 
503 Service Unavailable
No server is available to handle this request. 

50% gives correct website (wildfly default page)

Expected results:
100% wildfly default page 

Additional info:
Problem occurs since previews week

Comment 1 micha.van.santvoort 2017-04-12 10:16:08 UTC
I added the sample app, you can test with 
http://sample-mvsservices.44fs.preview.openshiftapps.com/
Press 10 times CTRL-F5 

50% OK (default wildfly page)
50% NOK -> 
Application is not available

The application is currently not serving requests at this endpoint. It may not have been started or is still starting.

Comment 2 micha.van.santvoort 2017-04-13 13:00:21 UTC
Problem seems to be fixed ! 
Tx !!!


Note You need to log in before you can comment on or make changes to this bug.