Hi Tamás Is it possible to run proximity in offline mode?
For example, when ibiblio goes down, I would stop proximity and restart it in offline mode so that it serves jars from its cache without even trying to access ibiblio (and so saving developers from suffering the http timeouts). Thanks Adam -----Original Message----- From: Tamás Cservenák [mailto:[EMAIL PROTECTED] Sent: 15 June 2006 19:08 To: Maven Users List Subject: Re: Maven repository manager (and maven-proxy) Hi all, Thank you Ben for emailing me, in latest days i have little overflow at job :) First, the answers to the Q's: - to serve up jars from its own cache when the internet connection is down Proximity WILL serve artifacts if it can/have it, even if remote peer is down or unreachable (at the cost of http timeout, see below), it will not "hardfail" in maven-proxy terms. It will actually serve what it have (if it have). If the requested artifact in not reachable from remote AND does not exists in local cache, proximity will give 404 as a result, thus maven build will fail. So, Proximity WILL protect you from 500 (quite often lately on ibilio) or any other HTTP error from ibiblio et al. Moreover, the Px uses the defaultRetryHandler of Commons HttpClient, so it wil retry 3 times (i think - not sure - will see) before failing.... And this is what makes you go over frequent ibiblio HTTP 500 errors. I set up recently Continuum, and first 5 builds of one project was failing. The log said that Continuum's embedded maven cannot get the needed plugins for it (remember, it was a clean start) because every 3rd request to ibilio returned 500! (and maven dies on 500 with transport error or so) So, i placed a proximity "in front" of continuum and it worked like a charm! - to time-out quicker than 60 seconds when it is down The http connection timeout is configurable, look at remotePeer properties.The default value is 10000 in msec. But remember, that actual timeout might be "worse", because of retry handling. Will see to externalize the retry count too. Newest build: https://is-micro.myip.hu/projects/ismicro-commons/deploy/proximity/nightly/ with a much improvements over alpha2. Here, i separated the "maven deps" and made general enhancement (searching by groupId, artifactId and much more). Will make a RC1 soon. My biggest problem is stats page. It is maybe 10% complete... but does not affect the functionality of Px itself. Is it needed? I just thought it will look cool with lists for top 10's ... :) Should I leave it out of Proximity? :) Have fun! ~t~ On 6/15/06, ben short <[EMAIL PROTECTED]> wrote: > > Adam, > > I have email the Proximity developer to see if he can answer your time > out question. > > Ben > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
