grisu / gricli

Grisu commandline client
7 stars 2 forks source link

Clean job fails #151

Closed sgenie68 closed 13 years ago

sgenie68 commented 13 years ago

Clean job fails after 1-2 jobs cleaned

com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status code 413: Request Entity Too Large at com.sun.xml.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:203) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:179) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:94) at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:89) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439) at com.sun.xml.ws.client.Stub.process(Stub.java:222) at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118) at $Proxy41.kill(Unknown Source) at grisu.gricli.command.KillJobCommand.execute(KillJobCommand.java:39) at grisu.gricli.Gricli.runCommand(Gricli.java:203) at grisu.gricli.Gricli.executionLoop(Gricli.java:86) at grisu.gricli.Gricli.main(Gricli.java:178)

makkus commented 13 years ago

Can we put all those 413 errors in the same ticket?

sgenie68 commented 13 years ago

After a bit of pondering markus suggested that the problem was related to the number of files in the job directories - gridftp takes too long to delete them and grisu fails with 413.

makkus commented 13 years ago

Test for this error:

https://github.com/grisu/grit/blob/develop/test-templates/clean_job.groovy https://github.com/grisu/grit/blob/develop/src/main/groovy/grisu/tests/tests/CleanJobTest.groovy

makkus commented 13 years ago

Hm, could not reproduce the exact 413 error, but could reproduce the client fail for cleans with jobdirs that have lots of files/folders in them. This at least is fixed, not quite sure how to tackle 413 since I can't reproduce...

makkus commented 13 years ago

Closing issue since I couldn't reproduce anymore with the change to making clean jobs asynchronous. Reopen if it still occurs for users.