Hi guys, I was interacting with Maven just when the problem occurred. Since I was able to bypass the 404 adding some dummy parameter to the url of the resource, my guess is that a reverse proxy in front of the real web layer cached a page when the resources where not yet available.
HTTP headers show that the reverse proxy is Varnish $ curl -v http://central.maven.org/maven2/org/apache/camel/camel-jms/2.13.1/ * Adding handle: conn: 0x23fa950 * Adding handle: send: 0 * Adding handle: recv: 0 * Curl_addHandleToPipeline: length: 1 * - Conn 0 (0x23fa950) send_pipe: 1, recv_pipe: 0 * About to connect() to central.maven.org port 80 (#0) * Trying 185.31.17.129... * Connected to central.maven.org (185.31.17.129) port 80 (#0) > GET /maven2/org/apache/camel/camel-jms/2.13.1/ HTTP/1.1 > User-Agent: curl/7.32.0 > Host: central.maven.org > Accept: */* > < HTTP/1.1 200 OK * Server nginx is not blacklisted < Server: nginx < Content-Type: text/html < Via: 1.1 varnish < Content-Length: 4364 < Accept-Ranges: bytes < Date: Fri, 16 May 2014 07:02:42 GMT < Via: 1.1 varnish < Age: 30 < Connection: keep-alive < X-Served-By: cache-v43-ASH, cache-fra1229-FRA < X-Cache: HIT, HIT < X-Cache-Hits: 1, 1 < X-Timer: S1400223732.467250824,VS0,VS48,VE48,VE29830 < Vary: X-Repo-Manager, X-Repo-Manager Now it seems to be all working fine, in case the problem is reported again we could try to manually purge the cache or to revise the synchronization of the cache building job. A workaround on client side, for someone in a real rush to download artifacts that Maven cannot see, could be configuring it in this way: http://brettporter.wordpress.com/2009/06/16/configuring-maven-http-connections/ bye paolo On Wed, May 14, 2014 at 5:13 PM, Claus Ibsen <[email protected]> wrote: > Hi > > Yeah there is something weird going on. The JARs are in the listinging > but some of them returns 404, for example camel-jms which is a key > component :( > > Not sure if its something on maven central, or what else? > > > > On Wed, May 14, 2014 at 6:17 AM, Camel Guy <[email protected]> wrote: > > Components: > > > > mail > > stream > > > > e.g., > > > > wget > > > http://repo.maven.apache.org/maven2/org/apache/camel/camel-stream/2.13.1/camel-stream-2.13.1.jar > > > > --2014-05-13 14:56:55-- > > > http://repo.maven.apache.org/maven2/org/apache/camel/camel-stream/2.13.1/camel-stream-2.13.1.jar > > > > Resolving repo.maven.apache.org... 199.27.77.129, 199.27.79.192 > > > > Connecting to repo.maven.apache.org|199.27.77.129|:80... connected. > > > > HTTP request sent, awaiting response... 404 Not Found > > > > > > Thank you > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: [email protected] > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > hawtio: http://hawt.io/ > fabric8: http://fabric8.io/ >
