Success! Looks like we've fixed this one. According to our records the fix was applied for
HTTP 503 on RPCs at Remote Filter Grid
If I do any actions like sorting at http://www.sencha.com/examples/#Exam...motefiltergrid
most of the time the first RPC fails with HTTP 503.
Even clicking the refresh button several times leads to nearly every 2nd call to fail.
Attention: to realize a failed call u have to look at "Net" Tab of ur FireBug or Wireshark the connection, etc. since the example doesn't tell u that a call failed.
I do not know if this is due to our network, your server or a bug in client- or serverside code. I should try from home. Can some confirm my observation?
Tried from home, same result: About every 2nd RPC returns HTTP 503.
Setup at home: Win7 64bit, Chrome
Setup at work: Win7 Enterprise SP1 64bit, FireFox 24.3.0 ESR
Sencha - Support Team
Thanks for the reporting!
We've noticed the issue, looks like we have some load balancing issue going on.
I have opened a bug in our bug tracker.