Thank you, Yoav. I will try setting fixed versions on the various plugins.
Do you know whom to contact to get this problem/answer listed on the Maven and/or Artifactory FAQs? There are many, many mailing threads and blog entries etc on these timeout problems and no clear solutions. Good FAQ visibility would really help. I do not appear to have update permissions on the Artifactory confluence wiki (http://wiki.jfrog.org/confluence/display/RTF/Troubleshooting) thanks, djb > There are reoccurring reports from the last couple of days about connection > problems with repo1, here and on other lists. > In your case Maven probably reaches out to look for metadata about the > available versions of the pmd plugin, so the simplest solution would be to > lock down the version of the plugins used in your project (which is also a > good practice for maintaining reproducible builds). > > You may also try to increase the network timeouts in the advance > configuration of the repo1 repository. However, in some cases I saw that the > connection phase may randomly take an unacceptable amount of time (>60 > secs). > > On Fri, May 7, 2010 at 8:56 PM, David Biesack <[email protected]> wrote: > > > > > We have CruiseControl performing builds via Maven (mvn -U ...), > > Most of the time, builds work fine. However, from time to time (several > > times a day), a build will fail > > > > [INFO] > > ------------------------------------------------------------------------ > > [ERROR] BUILD ERROR > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] The plugin 'org.apache.maven.plugins:maven-pmd-plugin' does not > > exist > > or no valid version could be found > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Trace > > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > > 'org.apache.maven.plugins:maven-pmd-plugin' does not exist or no valid > > version could be found > > at > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin(DefaultLifecycleExecutor.java:1651) > > .... > > > > when this happens, the entire build fails, and CruiseControl sends > > developers email, > > so they must take time to investigate this. Often, this clears up the next > > time > > CruiseControl tries to build the project automatically a couple minutes > > later. > > > > (This plugin does exist in our artifactory in the repo1-cache; for example > > > > http://aclmvn.unx.sas.com/artifactory/repo/org/apache/maven/plugins/maven-pmd-plugin/2.5/ > > shows > > both the jar and pom.) > > > > I assume this failure is because of an update check from Central, which may > > be timing out. > > Can anyone confirm this? More importantly, is there a way to resolve or > > prevent > > or workaround this, either through Artifactory (i.e. adding a timeout/retry > > strategy; > > or letting it fall back on the cache if an update check times out) or > > elsewhere (i.e. Maven). > > > > I thought about putting a wrapper around Maven so that if it gets such a > > failure, it will > > sleep for a short time, then try again (not no more than a few times) > > instead of always > > failing the first time, but that would be much more expensive (time, > > compute > > resources) than > > a repository fix. > > > > Has anyone implemented such a workaround? > > > > ----- > > > > configuration details: > > > > > > where Maven is configured with Artifactory 2.2.2 on our local server. Maven > > is configured using the settings.xml traight out of Artifactory > > (http://aclmvn.unx.sas.com/artifactory/webapp/mavensettings.html), > > including > > mirror: > > > > <mirrors> > > <mirror> > > <mirrorOf>*</mirrorOf> > > <name>repo</name> > > <url>http://aclmvn.unx.sas.com/artifactory/repo</url> > > <id>repo</id> > > </mirror> > > </mirrors> > > > > as well as (abbreviated): > > > > <url>http://aclmvn.unx.sas.com/artifactory/libs-releases</url> > > <url>http://aclmvn.unx.sas.com/artifactory/libs-snapshots</url> > > <url>http://aclmvn.unx.sas.com/artifactory/plugins-releases</url> > > <url>http://aclmvn.unx.sas.com/artifactory/plugins-snapshots</url> > > > > -- > > View this message in context: > > http://forums.jfrog.org/intermittent-plugin-failures-tp5020586p5020586.html > > Sent from the Artifactory - Users mailing list archive at Nabble.com. > > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > Artifactory-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/artifactory-users > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Artifactory-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/artifactory-users > > > ______________________________________ > View message @ > http://forums.jfrog.org/intermittent-plugin-failures-tp5020586p5021301.html > > To unsubscribe from intermittent plugin failures, click (link removed) > > > > <div dir="ltr">There are reoccurring reports from the last couple of days > about connection problems with repo1, here and on other lists.<div>In your > case Maven probably reaches out to look for metadata about the available > versions of the pmd plugin, so the simplest solution would be to lock down > the version of the plugins used in your project (which is also a good > practice for maintaining reproducible builds).</div> > > <div><br></div><div>You may also try to increase the network timeouts in the > advance configuration of the repo1 repository. However, in some cases I saw > that the connection phase may randomly take an unacceptable amount of time > (>60 secs).<br> > > <div><br><div class="gmail_quote">On Fri, May 7, 2010 at 8:56 PM, David > Biesack <span dir="ltr"><<a > href="/user/SendEmail.jtp?type=node&node=5021301&i=0" target="_top" > rel="nofollow">[hidden email]</a>></span> wrote:<br><blockquote > style="border-left:2px solid #CCCCCC;padding:0 1em" class="gmail_quote" > style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> > > <br> > We have CruiseControl performing builds via Maven (mvn -U ...),<br> > Most of the time, builds work fine. However, from time to time (several<br> > times a day), a build will fail<br> > <br> > [INFO]<br> > ------------------------------------------------------------------------<br> > [ERROR] BUILD ERROR<br> > [INFO]<br> > ------------------------------------------------------------------------<br> > [INFO] The plugin 'org.apache.maven.plugins:maven-pmd-plugin' does > not exist<br> > or no valid version could be found<br> > [INFO]<br> > ------------------------------------------------------------------------<br> > [INFO] Trace<br> > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin<br> > 'org.apache.maven.plugins:maven-pmd-plugin' does not exist or no > valid<br> > version could be found<br> > at<br> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyReportPlugin(DefaultLifecycleExecutor.java:1651)<br> > ....<br> > <br> > when this happens, the entire build fails, and CruiseControl sends<br> > developers email,<br> > so they must take time to investigate this. Often, this clears up the next<br> > time<br> > CruiseControl tries to build the project automatically a couple minutes<br> > later.<br> > <br> > (This plugin does exist in our artifactory in the repo1-cache; for example<br> > <a > href="http://aclmvn.unx.sas.com/artifactory/repo/org/apache/maven/plugins/maven-pmd-plugin/2.5/"; > target="_blank" rel="nofollow" > link="external">http://aclmvn.unx.sas.com/artifactory/repo/org/apache/maven/plugins/maven-pmd-plugin/2.5/</a><br> > shows<br> > both the jar and pom.)<br> > <br> > I assume this failure is because of an update check from Central, which > may<br> > be timing out.<br> > Can anyone confirm this? More importantly, is there a way to resolve or<br> > prevent<br> > or workaround this, either through Artifactory (i.e. adding a > timeout/retry<br> > strategy;<br> > or letting it fall back on the cache if an update check times out) or<br> > elsewhere (i.e. Maven).<br> > <br> > I thought about putting a wrapper around Maven so that if it gets such a<br> > failure, it will<br> > sleep for a short time, then try again (not no more than a few times)<br> > instead of always<br> > failing the first time, but that would be much more expensive (time, > compute<br> > resources) than<br> > a repository fix.<br> > <br> > Has anyone implemented such a workaround?<br> > <br> > -----<br> > <br> > configuration details:<br> > <br> > <br> > where Maven is configured with Artifactory 2.2.2 on our local server. > Maven<br> > is configured using the settings.xml traight out of Artifactory<br> > (<a href="http://aclmvn.unx.sas.com/artifactory/webapp/mavensettings.html"; > target="_blank" rel="nofollow" > link="external">http://aclmvn.unx.sas.com/artifactory/webapp/mavensettings.html</a>), > including<br> > mirror:<br> > <br> >  <mirrors><br> >   <mirror><br> >    <mirrorOf>*</mirrorOf><br> >    <name>repo</name><br> >    <url><a href="http://aclmvn.unx.sas.com/artifactory/repo"; > target="_blank" rel="nofollow" > link="external">http://aclmvn.unx.sas.com/artifactory/repo</a></url><br> >    <id>repo</id><br> >   </mirror><br> >  </mirrors><br> > <br> > as well as (abbreviated):<br> > <br> >  <url><a href="http://aclmvn.unx.sas.com/artifactory/libs-releases"; > target="_blank" rel="nofollow" > link="external">http://aclmvn.unx.sas.com/artifactory/libs-releases</a></url><br> >  <url><a href="http://aclmvn.unx.sas.com/artifactory/libs-snapshots"; > target="_blank" rel="nofollow" > link="external">http://aclmvn.unx.sas.com/artifactory/libs-snapshots</a></url><br> >  <url><a href="http://aclmvn.unx.sas.com/artifactory/plugins-releases"; > target="_blank" rel="nofollow" > link="external">http://aclmvn.unx.sas.com/artifactory/plugins-releases</a></url><br> >  <url><a > href="http://aclmvn.unx.sas.com/artifactory/plugins-snapshots"; > target="_blank" rel="nofollow" > link="external">http://aclmvn.unx.sas.com/artifactory/plugins-snapshots</a></url><br> > <br> > --<br> > View this message in context: <a > href="http://forums.jfrog.org/intermittent-plugin-failures-tp5020586p5020586.html"; > target="_blank" rel="nofollow" > link="external">http://forums.jfrog.org/intermittent-plugin-failures-tp5020586p5020586.html</a><br> > Sent from the Artifactory - Users mailing list archive at Nabble.com.<br> > <br> > ------------------------------------------------------------------------------<br> > <br> > _______________________________________________<br> > Artifactory-users mailing list<br> > <a href="/user/SendEmail.jtp?type=node&node=5021301&i=1" target="_top" > rel="nofollow">[hidden email]</a><br> > <a href="https://lists.sourceforge.net/lists/listinfo/artifactory-users"; > target="_blank" rel="nofollow" > link="external">https://lists.sourceforge.net/lists/listinfo/artifactory-users</a><br> > </blockquote></div><br><br clear="all"><br> > </div></div></div> > <br > />------------------------------------------------------------------------------ > <br><br><br />_______________________________________________ > <br>Artifactory-users mailing list > <br><a href="/user/SendEmail.jtp?type=node&node=5021301&i=2" target="_top" > rel="nofollow">[hidden email]</a> > <br><a href="https://lists.sourceforge.net/lists/listinfo/artifactory-users"; > target="_top" rel="nofollow" > link="external">https://lists.sourceforge.net/lists/listinfo/artifactory-users</a><br> > <br/><br/> > <hr noshade="noshade" size="1" color="#cccccc" /> > <div style="color:#666666; font: 11px > tahoma,geneva,helvetica,arial,sans-serif;"> > View message @ <a > href="http://forums.jfrog.org/intermittent-plugin-failures-tp5020586p5021301.html";>http://forums.jfrog.org/intermittent-plugin-failures-tp5020586p5021301.html</a> > > <br>To unsubscribe from intermittent plugin failures, <a href=" (link > removed) ">click here</a>. > </div> > <br/> > -- David J. Biesack, SAS SAS Campus Dr. Cary, NC 27513 www.sas.com (919) 531-7771 -- View this message in context: http://forums.jfrog.org/intermittent-plugin-failures-tp5020586p5030237.html Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
_______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
