On 04 Feb 2013, at 09:38, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-02-03, at 22:46, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 03 Feb 2013, at 21:51, Camillo Bruni <camillobruni@gmail.com> wrote:
When I export the whole pharo sources I get infrequent error 500 responses on http://seaside.gemstone.com/ss/metacello
----------------------------------------------------------------------------- MCRepositoryError: Could not access http://seaside.gemstone.com/ss/metacello:ZnHttpUnsuccessful: 500 Internal Server Error [0mMCHttpRepository>>loadAllFileNames in Block: [:exception | (exception className beginsWith: 'Zn...etc... BlockClosure>>cull: MethodContext(ContextPart)>>handleSignal: in Block: [self exceptionHandlerBlock cull: exception] BlockClosure>>ensure: MethodContext(ContextPart)>>handleSignal: MethodContext(ContextPart)>>handleSignal: ZnHttpUnsuccessful(Exception)>>signal ZnClient>>handleResponse ZnClient>>executeWithRedirectsRemaining: ... -----------------------------------------------------------------------------
is that a know problem, or do I just run into a strange image?
'occasional' is never good ;-)
Can you see anything useful in the response from the server ?
So it happens "regularly" after 300-350 hits ;)
normal content legth: 265975bytes, whereas the error 500 ones are returning a length of 620 (consistently) ------------------------------------------------------------------------------------------ '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Please contact the server administrator, is@gemstone.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p> <p>More information about this error may be available in the server error log.</p> <hr> <address>Apache/2.2.3 (CentOS) Server at seaside.gemstone.com Port 80</address> </body></html> ------------------------------------------------------------------------------------------
meh :/
This is clearly a server side problem. Maybe you (and your program doing the requests) should take a little nap after 100 requests so that the server can recover ;-) Sven