I'm getting this from multiple machines hosted at various data centers when trying to do a clean build of a project with a large set of dependencies:

Could not transfer artifact org.hibernate:hibernate-entitymanager:jar:3.6.4.Final from/to jboss-public-repository-group (https://repository.jboss.org/nexus/cont ... /releases/): Error transferring file: Connection refused

It isn't just the entitymanager, it seems like the jboss repository just randomly fails. If I wait and try again a half dozen times eventually maven can get all the hibernate artifacts from the Jboss repository but this problem makes our nightly build tool report failures quite often.

Is this a know issue with the jboss.org repository?

hi, thanks for the heads up; I'll send a note to the administrators of that Nexus instance.

I'm also wondering, is your CI server re-downloading all artifacts every night? that's not how it's supposed to work, and the poor maven servers couldn't handle the load if everybody was doing this way.
To guarantee stable builds of your project people usually setup local proxies, or even services such as Artifactory or Nexus; they both provide free versions which provide very good tools for developers, or pay for versions with more advanced features; I'd definitely use one so you're in control of your libraries: how can you guarantee repeatable builds in the long run otherwise? other companies might cease to exist or have to change urls.

Thanks for looking into it.

The CI server isn't doing it every night, I realize I wasn't really very clear about that in my original post. All of our on-commit and nightly builds are use a local repository. We have one weekly build that does a build with a clean local repository. We do that to make sure that changes in remote repos (yeah, not supposed to happen but it does A LOT) don't break a clean build of our project.

We're planning on stopping that build completely once we can remove all additional repositories from the project pom since we haven't seen things change/disappear from central. At this point the JBoss repo and one other repo are our last two non-central repositories and i think we may be down to just having the additional JBoss repository specified in the project. What I'd love to see is syncing of the jboss release repo to central. It would significantly help our clean build time (no need to hit the jboss repo first for every artifact) and reduce you're load :)

We do have it documented that for people actually doing deployment of the project to use a local proxy, generally Nexus. A lot of the actual project developers don't necessarily have a local proxy available to them.

Thanks again for the response and looking into the issue.

-Eric

sounds good, but if you where regularly building from your local repository it would be impossible for artifacts to change ;)

Anyway, both from central and from jboss.org you'll never see artifacts disappear or change, there are strict policies in place to prevent that.

again, thanks for warning about that.

Right, the concern is for people new to the project or that version of the project. They are checking out the code running maven commands and having to download all of the dependencies.

Glad to hear that JBoss has strict controls as well, we may look at just disabling that build and seeing if we have any problems with the the other non-central repo we have as well.