You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Tibor Digana <ti...@apache.org> on 2018/09/12 07:57:50 UTC
Our builds crashed on Jenkins system due to "Failed to collect dependencies"
Hi all,
Last time the build failed quite often on connection problems with Maven
Central.
Sometimes the problem is connection timeout and sometimes it is HTTP 503.
Although in all cases I see "Maximum threads for service reached".
Does it mean that any thread pool in Wagon is limited or it is OS limit?
Do you have deeper insides in this area?
Created INFRA ticket at Jira. See my last three comments.
https://issues.apache.org/jira/browse/INFRA-16951
Cheers
Tibor
Re: Our builds crashed on Jenkins system due to "Failed to collect dependencies"
Posted by Olivier Lamy <ol...@apache.org>.
no need to send it twice :) (it works from your gmail account)
It's a very common error with Fastly see
https://docs.fastly.com/guides/debugging/common-503-errors.
And I think (not really sure of that) Sonatype is using fastly for central
repo (https://www.fastly.com/customers/sonatype)
so maybe it's the cause....
On Wed, 12 Sep 2018 at 20:52, Tibor Digana <ti...@apache.org> wrote:
> (sent from my gmail account)
> ok, and how is the error code related to the message "Maximum threads for
> service reached"?
> Thx.
>
> Cheers
> Tibor
>
> On Wed, Sep 12, 2018 at 12:16 PM Olivier Lamy <ol...@apache.org> wrote:
>
> > On Wed, 12 Sep 2018 at 17:58, Tibor Digana <ti...@apache.org>
> wrote:
> >
> > > Hi all,
> > >
> > > Last time the build failed quite often on connection problems with
> Maven
> > > Central.
> > > Sometimes the problem is connection timeout and sometimes it is HTTP
> 503.
> > > Although in all cases I see "Maximum threads for service reached".
> > >
> > > Does it mean that any thread pool in Wagon is limited or it is OS
> limit?
> > > Do you have deeper insides in this area?
> > >
> >
> > this is a server error status nothing related to wagon.
> > Wagon only reports server response here
> >
> >
> > >
> > > Created INFRA ticket at Jira. See my last three comments.
> > > https://issues.apache.org/jira/browse/INFRA-16951
> > >
> > > Cheers
> > > Tibor
> > >
> >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Our builds crashed on Jenkins system due to "Failed to collect dependencies"
Posted by Tibor Digana <ti...@apache.org>.
(sent from my gmail account)
ok, and how is the error code related to the message "Maximum threads for
service reached"?
Thx.
Cheers
Tibor
On Wed, Sep 12, 2018 at 12:16 PM Olivier Lamy <ol...@apache.org> wrote:
> On Wed, 12 Sep 2018 at 17:58, Tibor Digana <ti...@apache.org> wrote:
>
> > Hi all,
> >
> > Last time the build failed quite often on connection problems with Maven
> > Central.
> > Sometimes the problem is connection timeout and sometimes it is HTTP 503.
> > Although in all cases I see "Maximum threads for service reached".
> >
> > Does it mean that any thread pool in Wagon is limited or it is OS limit?
> > Do you have deeper insides in this area?
> >
>
> this is a server error status nothing related to wagon.
> Wagon only reports server response here
>
>
> >
> > Created INFRA ticket at Jira. See my last three comments.
> > https://issues.apache.org/jira/browse/INFRA-16951
> >
> > Cheers
> > Tibor
> >
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
Re: Our builds crashed on Jenkins system due to "Failed to collect dependencies"
Posted by Tibor Digana <ti...@googlemail.com.INVALID>.
ok, and how is the error code related to the message "Maximum threads for
service reached"?
On Wed, Sep 12, 2018 at 12:16 PM Olivier Lamy <ol...@apache.org> wrote:
> On Wed, 12 Sep 2018 at 17:58, Tibor Digana <ti...@apache.org> wrote:
>
> > Hi all,
> >
> > Last time the build failed quite often on connection problems with Maven
> > Central.
> > Sometimes the problem is connection timeout and sometimes it is HTTP 503.
> > Although in all cases I see "Maximum threads for service reached".
> >
> > Does it mean that any thread pool in Wagon is limited or it is OS limit?
> > Do you have deeper insides in this area?
> >
>
> this is a server error status nothing related to wagon.
> Wagon only reports server response here
>
>
> >
> > Created INFRA ticket at Jira. See my last three comments.
> > https://issues.apache.org/jira/browse/INFRA-16951
> >
> > Cheers
> > Tibor
> >
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
--
Cheers
Tibor
Re: Our builds crashed on Jenkins system due to "Failed to collect dependencies"
Posted by Olivier Lamy <ol...@apache.org>.
On Wed, 12 Sep 2018 at 17:58, Tibor Digana <ti...@apache.org> wrote:
> Hi all,
>
> Last time the build failed quite often on connection problems with Maven
> Central.
> Sometimes the problem is connection timeout and sometimes it is HTTP 503.
> Although in all cases I see "Maximum threads for service reached".
>
> Does it mean that any thread pool in Wagon is limited or it is OS limit?
> Do you have deeper insides in this area?
>
this is a server error status nothing related to wagon.
Wagon only reports server response here
>
> Created INFRA ticket at Jira. See my last three comments.
> https://issues.apache.org/jira/browse/INFRA-16951
>
> Cheers
> Tibor
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy