Hi everyone. We had a seemingly random CruiseControl build failure today. When I investigated, it appeared to have been caused by a fleeting error on our local maven proxy server. Here's the snippet from maven-proxy.log:
2007-01-16 14:16:56,113 [INFO ] proxy.servlets.RepositoryServlet - Received request: /groovy/groovy-all-1.0-jsr/06/groovy-all-1.0-jsr-06.jar 2007-01-16 14:16:56,113 [DEBUG] proxy.engine.DownloadEngine - Request: source=192.168.137.199, path=/groovy/groovy-all-1.0-jsr/06/groovy-all-1.0-jsr-06.jar, lastModified=-1, headOnly=false, ifModifiedSince=-1 2007-01-16 14:16:56,113 [DEBUG] proxy.config.FileRepoConfiguration - Repo[global]: Checking last modified time for ./target/repo/groovy/groovy-all-1.0-jsr/06/groovy-all-1.0-jsr-06.jar 2007-01-16 14:16:56,113 [INFO ] proxy.engine.DownloadEngine - Transferring /groovy/groovy-all-1.0-jsr/06/groovy-all-1.0-jsr-06.jar directly to user from Repo[global] 2007-01-16 14:16:56,122 [ERROR] proxy.engine.DownloadEngine - java.lang.IllegalStateException: Committed Does anyone know what might have caused that IllegalStateException? I checked and the jar is still on our proxy server at the right location, and hasn't been moved or changed for a while. Of course a subsequent CruiseControl build (manually kicked off) succeeded with no new changes to the codeline. Thanks for any insights anyone might have. I do appreciate the maven-proxy server. It has been a reliable and essential tool for us for a while now. - Don
