Maven 3.0.3 hanging / having timeouts often?

Discussion:

Andrew Robinson

2011-05-12 00:22:34 UTC

I have been using maven 2.2.1 for a while at my company and we just switched
to maven 3. I have rebuilt my computer (ubuntu maverick 10.04 32-bit ==>
ubuntu natty 11.04 64-bit) and installed maven 3.

In maven 3.0.3, (I have not seen it with maven 2.2.1), it stops downloading
after a few to several downloads. If I ^C the build, and keep re-running it,
it will eventually built. It only dies when maven is trying to download
file. It may happen before any progress is display, partial progress or full
progress.

Example:
Downloading:
http://internalserver.ouritranet.com:8086/archiva/repository/internal/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Downloading: http://
internalserver.ouritranet.com:8086/archiva/repository/snapshots-corporate/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Downloading:
http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Downloading:
http://www.ibiblio.org/maven/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
341 B 341 B

If I let it go for a while it then prints:
Downloading:
http://internalserver.ouritranet.com:8086/archiva/repository/internal/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Downloading:
http://internalserver.ouritranet.com:8086/archiva/repository/snapshots-corporate/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Downloading:
http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Downloading:
http://www.ibiblio.org/maven/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
[WARNING] Checksum validation failed, could not read expected checksum:
Error transferring file: Connection timed out for
http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
[WARNING] Checksum validation failed, could not read expected checksum:
Error transferring file: Connection timed out for
http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml

My other co-workers have not reported seeing this issue yet. Any ideas on
why maven 3.0.3 is having this problem when maven 2.2.1 does not?

FYI, we have a corporate proxy, not sure if that could be part of the
problem.

-Andrew

Wayne Fay

2011-05-12 03:01:53 UTC

Permalink

Obviously you have a proxy. Why in the world are you connecting
directly to repo2, repo1, ibiblio etc instead of just letting your
proxy hit them on your behalf?

Wayne

Andrew Robinson

2011-05-12 16:01:19 UTC

Permalink

They are going through my proxy, why would you think I am hitting them
directly?

I have my <proxy> setup in my settings.xml.

It is working most of the time, if it were the fact that my proxy was not
used, it would fail 100% of the time (all internet traffic must go through
our proxy at work).

-Andrew

Post by Andrew Robinson
http://internalserver.ouritranet.com:8086/archiva/repository/internal/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://www.ibiblio.org/maven/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Obviously you have a proxy. Why in the world are you connecting
directly to repo2, repo1, ibiblio etc instead of just letting your
proxy hit them on your behalf?
Wayne
---------------------------------------------------------------------

Wayne Fay

2011-05-12 16:12:28 UTC

Permalink

Post by Andrew Robinson
They are going through my proxy, why would you think I am hitting them
directly?

I'm OK with the proxy. I'm confused about the Archiva repo you have
installed. I should not have said "proxy" when I really meant
MRM/Archiva. Your log shows that your build is hitting Archiva and
then also hitting repo2, repo1, and ibiblio for a metadata.xml file.

For us (and I think a lot of users of MRMs like Nexus, Artifactory,
Archiva), a large part of the reason why we are using a Maven Repo
Manager is so that we can tell all our Maven instances on all our
machines to look for ALL artifacts directly in that repo manager
(Archiva in your case). Then our governance functions can determine
which artifacts are OK to use (based on licensing and other concerns)
and which must be avoided etc.

I think the way you have things configured is less than ideal and you
may want to reconsider it. IMO all artifact access should be managed
by your Archiva instance.

Wayne

Andrew Robinson

2011-05-12 18:31:09 UTC

Permalink

Okay, good to know, I'll forward that question onto the fellas that
configured our settings.xml and pom.xml files for mvn3.

Post by Wayne Fay

Post by Andrew Robinson
They are going through my proxy, why would you think I am hitting them
directly?

I'm OK with the proxy. I'm confused about the Archiva repo you have
installed. I should not have said "proxy" when I really meant
MRM/Archiva. Your log shows that your build is hitting Archiva and
then also hitting repo2, repo1, and ibiblio for a metadata.xml file.
For us (and I think a lot of users of MRMs like Nexus, Artifactory,
Archiva), a large part of the reason why we are using a Maven Repo
Manager is so that we can tell all our Maven instances on all our
machines to look for ALL artifacts directly in that repo manager
(Archiva in your case). Then our governance functions can determine
which artifacts are OK to use (based on licensing and other concerns)
and which must be avoided etc.
I think the way you have things configured is less than ideal and you
may want to reconsider it. IMO all artifact access should be managed
by your Archiva instance.
Wayne
---------------------------------------------------------------------

Alex Lopez

2011-05-12 10:50:05 UTC

Permalink

Post by Andrew Robinson
I have been using maven 2.2.1 for a while at my company and we just switched
to maven 3. I have rebuilt my computer (ubuntu maverick 10.04 32-bit ==>
ubuntu natty 11.04 64-bit) and installed maven 3.
In maven 3.0.3, (I have not seen it with maven 2.2.1), it stops downloading
after a few to several downloads. If I ^C the build, and keep re-running it,

+1, I've been having this kind of 'hangs', using maven 3.0.2 and
artifactory 2.3.1 (sometimes when running maven site, sometimes
performing a build), then ^C seems to get maven to continue doing what
it was doing and eventually end with success...

Post by Andrew Robinson
it will eventually built. It only dies when maven is trying to download
file. It may happen before any progress is display, partial progress or full
progress.
http://internalserver.ouritranet.com:8086/archiva/repository/internal/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Downloading: http://
internalserver.ouritranet.com:8086/archiva/repository/snapshots-corporate/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://www.ibiblio.org/maven/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
341 B 341 B
http://internalserver.ouritranet.com:8086/archiva/repository/internal/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://internalserver.ouritranet.com:8086/archiva/repository/snapshots-corporate/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://www.ibiblio.org/maven/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Error transferring file: Connection timed out for
http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Error transferring file: Connection timed out for
http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
My other co-workers have not reported seeing this issue yet. Any ideas on
why maven 3.0.3 is having this problem when maven 2.2.1 does not?
FYI, we have a corporate proxy, not sure if that could be part of the
problem.
-Andrew

Alex Lopez

2011-05-12 11:01:40 UTC

Permalink

Now this got me thinking, my intuition is that this might be a network
related problem... maybe maven 2 had shorter timeouts, hence not
appearing to hang, does Maven 3 download more than one dependency at the
same time? Does this behavior differ from version 2? Why hitting ^C
under such circumstances wouldn't end mvn process, instead forcing it to
continue?

Post by Alex Lopez

---------------------------------------------------------------------

Anders Hammar

2011-05-12 11:16:35 UTC

Permalink

Yes, Maven 3 should download artifacts in parallell. But Maven 2.2.1 also
does that (this feature was introduced in 2.1.0 IIRC). But it is likely two
different implementations.

/Anders

Post by Alex Lopez
Now this got me thinking, my intuition is that this might be a network
related problem... maybe maven 2 had shorter timeouts, hence not appearing
to hang, does Maven 3 download more than one dependency at the same time?
Does this behavior differ from version 2? Why hitting ^C under such
circumstances wouldn't end mvn process, instead forcing it to continue?

Post by Alex Lopez

Post by Andrew Robinson
file. It may happen before any progress is display, partial progress or full
progress.
http://internalserver.ouritranet.com:8086/archiva/repository/internal/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Downloading: http://
internalserver.ouritranet.com:8086/archiva/repository/snapshots-corporate/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://www.ibiblio.org/maven/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
341 B 341 B
http://internalserver.ouritranet.com:8086/archiva/repository/internal/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://internalserver.ouritranet.com:8086/archiva/repository/snapshots-corporate/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
http://www.ibiblio.org/maven/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Error transferring file: Connection timed out for
http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
Error transferring file: Connection timed out for
http://repo2.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml
My other co-workers have not reported seeing this issue yet. Any ideas on
why maven 3.0.3 is having this problem when maven 2.2.1 does not?
FYI, we have a corporate proxy, not sure if that could be part of the
problem.
-Andrew

---------------------------------------------------------------------

Tim Pizey

2011-05-12 11:02:54 UTC

Permalink

+1, I've been having this kind of 'hangs', using maven 3.0.2 and artifactory
2.3.1 (sometimes when running maven site, sometimes performing a build),
then ^C seems to get maven to continue doing what it was doing and
eventually end with success...

Me too, on win7/cygwin. I thought it was a cygwin problem.

cheers

--
Tim Pizey - http://pizey.net/~timp
Centre for Genomics and Global Health - http://cggh.org

Alex Lopez

2011-05-12 11:39:20 UTC

Permalink

Post by Tim Pizey

+1, I've been having this kind of 'hangs', using maven 3.0.2 and artifactory
2.3.1 (sometimes when running maven site, sometimes performing a build),
then ^C seems to get maven to continue doing what it was doing and
eventually end with success...

Me too, on win7/cygwin. I thought it was a cygwin problem.

+1 now that I think about that it seems definitely like a cygwin
problem, since I'm never getting this through m2eclipse...

could it be related with the warning cygwin gives me complaining about
bad ms-dos style paths?

$ mvn site site:stage
cygwin warning:
MS-DOS style path detected: C:\Program Files\Apache Software
Foundation\apache-maven-3.0.2/boot/
Preferred POSIX equivalent is: /cygdrive/c/Program Files/Apache
Software Foundation/apache-maven-3.0.2/boot/
...

Post by Tim Pizey
cheers

Andrew Robinson

2011-05-16 16:16:12 UTC

Permalink

Any advice on this? Should I be opening a maven bug? It is really killing my
productivity as I have to babysit every build and keep aborting it and
restarting it several times until all updates (mostly snapshots per day) are
downloaded.

Thanks,
Andrew

Post by Tim Pizey

+1, I've been having this kind of 'hangs', using maven 3.0.2 and artifactory
2.3.1 (sometimes when running maven site, sometimes performing a build),
then ^C seems to get maven to continue doing what it was doing and
eventually end with success...

Me too, on win7/cygwin. I thought it was a cygwin problem.

+1 now that I think about that it seems definitely like a cygwin problem,
since I'm never getting this through m2eclipse...
could it be related with the warning cygwin gives me complaining about bad
ms-dos style paths?
$ mvn site site:stage
MS-DOS style path detected: C:\Program Files\Apache Software
Foundation\apache-maven-3.0.2/boot/
Preferred POSIX equivalent is: /cygdrive/c/Program Files/Apache Software
Foundation/apache-maven-3.0.2/boot/
...

Post by Tim Pizey
cheers

---------------------------------------------------------------------

Wayne Fay

2011-05-16 16:34:11 UTC

Permalink

Post by Andrew Robinson
Any advice on this? Should I be opening a maven bug? It is really killing my
productivity as I have to babysit every build and keep aborting it and
restarting it several times until all updates (mostly snapshots per day) are
downloaded.

If this was typical then we would see similar complaints from lots of
people. Clearly something is special about the way you have things
configured or something else in your environment. I'm not sure how you
expect anyone here to diagnose this class of problem.

Did you reconfigure your proxy and settings.xml so all requests are
going through Archiva? I see that as a pre-requisite before talking
about anything else.

Wayne

Andrew Robinson

2011-05-16 16:54:16 UTC

Permalink

Archiva is being used to serve our internal packages of our company, it is
not being used to serve dependencies from internet repositories. So no I
cannot send all requests through Archiva.

It may be as simple as a linux kernel issue with e1000e driver (dell
latitude E6410). It has caused me issues in Ubuntu in 10.10 and could be
still some issues in 11.04. It is hard to say as there is not much to debug
with at this point and I am not seeing any obvious system errors or anything
to troubleshoot with.

Post by Wayne Fay

Post by Andrew Robinson
Any advice on this? Should I be opening a maven bug? It is really killing

Post by Andrew Robinson
productivity as I have to babysit every build and keep aborting it and
restarting it several times until all updates (mostly snapshots per day)

are

Post by Andrew Robinson
downloaded.

If this was typical then we would see similar complaints from lots of
people. Clearly something is special about the way you have things
configured or something else in your environment. I'm not sure how you
expect anyone here to diagnose this class of problem.
Did you reconfigure your proxy and settings.xml so all requests are
going through Archiva? I see that as a pre-requisite before talking
about anything else.
Wayne
---------------------------------------------------------------------

Benson Margulies

2011-05-16 17:34:41 UTC

Permalink

Unless you can post a project to github that demonstrates differential
behavior everywhere, or use mvn -X or wireshark to deliver an analysis
of *how* 3.0.3 is hitting the network differently than 2.2.1, you're
unlikely to get much succor here.

It would really help you if you could convince your corporate
Archiva-ists to configure it to work as a cache for the internet.

Or if you quietly put a copy of Archiva or Nexus for those purposes on
your own machine :-)

On Mon, May 16, 2011 at 12:54 PM, Andrew Robinson

Post by Andrew Robinson
Archiva is being used to serve our internal packages of our company, it is
not being used to serve dependencies from internet repositories. So no I
cannot send all requests through Archiva.
It may be as simple as a linux kernel issue with e1000e driver (dell
latitude E6410). It has caused me issues in Ubuntu in 10.10 and could be
still some issues in 11.04. It is hard to say as there is not much to debug
with at this point and I am not seeing any obvious system errors or anything
to troubleshoot with.

Post by Wayne Fay

Post by Andrew Robinson
Any advice on this? Should I be opening a maven bug? It is really killing

Post by Andrew Robinson
productivity as I have to babysit every build and keep aborting it and
restarting it several times until all updates (mostly snapshots per day)

are

Post by Andrew Robinson
downloaded.

If this was typical then we would see similar complaints from lots of
people. Clearly something is special about the way you have things
configured or something else in your environment. I'm not sure how you
expect anyone here to diagnose this class of problem.
Did you reconfigure your proxy and settings.xml so all requests are
going through Archiva? I see that as a pre-requisite before talking
about anything else.
Wayne
---------------------------------------------------------------------

Barrie Treloar

2011-05-16 23:43:32 UTC

Permalink

Post by Benson Margulies
Or if you quietly put a copy of Archiva or Nexus for those purposes on
your own machine :-)

Running a repository manager locally is a smart idea if you are on a laptop.
Saves you the pain of reconfiguring maven when you unplug from the network.

Benson Margulies

2011-05-16 23:52:50 UTC

Permalink

"Running a local nexus means never having to say --offline"

Post by Barrie Treloar

Post by Benson Margulies
Or if you quietly put a copy of Archiva or Nexus for those purposes on
your own machine :-)

Running a repository manager locally is a smart idea if you are on a laptop.
Saves you the pain of reconfiguring maven when you unplug from the network.
---------------------------------------------------------------------

Andrew Robinson

2011-05-17 23:03:22 UTC

Permalink

Okay, I removed a bunch of cruft from my settings.xml and odd settings that
our company has asked us to put in there. Once cleaning this up I have not
had the timeout yet. I think I am okay for a while, but will respond again
if the problem comes back and I can provide more useful information.

Thanks

Post by Benson Margulies
"Running a local nexus means never having to say --offline"

Post by Barrie Treloar

Post by Benson Margulies
Or if you quietly put a copy of Archiva or Nexus for those purposes on
your own machine :-)

Running a repository manager locally is a smart idea if you are on a

laptop.

Post by Barrie Treloar
Saves you the pain of reconfiguring maven when you unplug from the

network.

Post by Barrie Treloar
---------------------------------------------------------------------

---------------------------------------------------------------------

arro

2012-04-23 07:03:34 UTC

Permalink

Sorry for resurrecting an old thread, but I'm having the exact same problem
with Maven 3.0.4 timing out while trying to download artifacts.

Right now I'm running Maven from home, with no proxy. The problem also
occured when I tried to use the same laptop at work, with a Nexus repository
manager. I then assumed it was some kind of temporary network problem, but
since I'm seeing the same thing again, I guess it must have something to do
with the computer setup.

I'm on Windows 7 and cygwin (CYGWIN_NT-6.1-WOW64). I have removed my
~/.m2/settings.xml to see if that made any difference -- it did not. There
does not appear to be any network problem, I can download the artifacts
manually (in Firefox) just fine.

Anyone else seen this problem?

/Henrik Arro

--
View this message in context: http://maven.40175.n5.nabble.com/Maven-3-0-3-hanging-having-timeouts-often-tp4388958p5658520.html
Sent from the Maven - Users mailing list archive at Nabble.com.

Wayne Fay

2012-04-23 14:26:26 UTC

Permalink

Post by arro
I'm on Windows 7 and cygwin (CYGWIN_NT-6.1-WOW64). I have removed my
~/.m2/settings.xml to see if that made any difference -- it did not. There
does not appear to be any network problem, I can download the artifacts
manually (in Firefox) just fine.

Can you try building your projects with Maven 3.0.4 in Windows (not in
the Cygwin environment) to see if there is any difference?

Wayne

martin.eisengardt

2012-04-23 15:40:58 UTC

Permalink

I got some similar problems.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=362418
Seems that java itself or maven or any other thing is not liking my aviara
firewall or my network device. There are some other java apps that sometime
have the same connection problems resulting in timeouts. Are there any
hints what maven is doing (activate debug option) or can you simply wait to
see if it is the same network timeout issue?

Post by Wayne Fay

Post by arro
I'm on Windows 7 and cygwin (CYGWIN_NT-6.1-WOW64). I have removed my
~/.m2/settings.xml to see if that made any difference -- it did not.

There

Post by arro
does not appear to be any network problem, I can download the artifacts
manually (in Firefox) just fine.

Can you try building your projects with Maven 3.0.4 in Windows (not in
the Cygwin environment) to see if there is any difference?
Wayne
---------------------------------------------------------------------

Henrik Arro

2012-04-25 10:49:48 UTC

Permalink

Interesting. Do you have an example of another Java application that has
network connectivity problems? Then I could try it to see if it is the
combination Java / network hardware that is the culprit.

Just for the record, my JAVA_HOME is C:\Program Files\Java\jdk1.7.0_03, but
when I run "java -version", I get "java version "1.6.0_31"". The computer in
question is a Sony Vaio laptop, with an Atheros AR9285 wireless network
adapter.

/Henrik Arro

Post by martin.eisengardt
I got some similar problems.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=362418
Seems that java itself or maven or any other thing is not liking my aviara
firewall or my network device. There are some other java apps that sometime
have the same connection problems resulting in timeouts. Are there any
hints what maven is doing (activate debug option) or can you simply wait to
see if it is the same network timeout issue?

--
View this message in context: http://maven.40175.n5.nabble.com/Maven-3-0-3-hanging-having-timeouts-often-tp4388958p5664491.html
Sent from the Maven - Users mailing list archive at Nabble.com.

Wayne Fay

2012-04-25 13:44:33 UTC

Permalink

Post by Henrik Arro
Just for the record, my JAVA_HOME is C:\Program Files\Java\jdk1.7.0_03, but
when I run "java -version", I get "java version "1.6.0_31"". The computer in

That simply means you have another java in your path before the
jdk1.7.0_03. Perhaps there is a "java.exe" file in c:\windows or
something like that.

Wayne

Bob Wang

2012-04-26 00:58:42 UTC

Permalink

Hi,

You can use "where java" in the command line to check where your java is.

-----Original Message-----
From: Wayne Fay [mailto:***@gmail.com]
Sent: Wednesday, April 25, 2012 9:45 PM
To: Maven Users List
Subject: Re: Maven 3.0.3 hanging / having timeouts often?

Post by Henrik Arro
Just for the record, my JAVA_HOME is C:\Program
Files\Java\jdk1.7.0_03, but when I run "java -version", I get "java
version "1.6.0_31"". The computer in

That simply means you have another java in your path before the jdk1.7.0_03. Perhaps there is a "java.exe" file in c:\windows or something like that.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@maven.apache.org
For additional commands, e-mail: users-***@maven.apache.org

Wayne Fay

2012-04-26 01:41:01 UTC

Permalink

Post by Henrik Arro
Interesting. Do you have an example of another Java application that has
network connectivity problems? Then I could try it to see if it is the
combination Java / network hardware that is the culprit.

Problems like this on Windows are frequently related to some antivirus
or firewall (Windows or another). Try disabling your antivirus and any
firewalls you may be running (including the built-in Windows
firewall).

If you are running this on a computer "at work" there can also be
transparent Internet proxies (Squid) or antivirus appliances etc
between your machine and the download site. This is less common "at
home" but I know some ISPs are caching hits etc.

Wayne

Henrik Arro

2012-04-25 08:54:59 UTC

Permalink

Thanks for the suggestion, but unfortunately the same behavior when running
Maven in a Windows command-line (cmd.exe).

Running "mvn -X" does not provide much useful information, as far as I can
tell, just a timeout after around 30 minutes:

[DEBUG] Using connector WagonRepositoryConnector with priority 0 for
http://repo.maven.apache.org/maven2
Downloading:
http://repo.maven.apache.org/maven2/org/codehaus/groovy/groovy/1.8.3/groovy-1.8.3.jar
[DEBUG] Writing resolution tracking file C:\Users\Henrik
Arro\.m2\repository\org\codehaus\groovy\groovy\1.8.3\groovy-1.8.3.jar.lastUpdated
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 30:02.959s
[INFO] Finished at: Wed Apr 25 09:35:49 CEST 2012
[INFO] Final Memory: 10M/105M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-archetype-plugin:2.2:generate (default-cli)
on project standalone-pom: Execution default-cli of goal
org.apache.maven.plugins:maven-archetype-plugin:2.2:generate failed: Plugin
o rg.apache.maven.plugins:maven-archetype-plugin:2.2 or one of its
dependencies could not be resolved: Could not transfer artifact
org.codehaus.groovy:groovy:jar:1.8.3 from/to central
(http://repo.maven.apache.org/maven2): GET request of:
org/codehaus/groovy/groovy/1.8.3/groovy-1.8.3.jar from central failed: Read
timed out -> [Help 1]

...

Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at
org.apache.maven.wagon.providers.http.httpclient.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)
at
org.apache.maven.wagon.providers.http.httpclient.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)
at
org.apache.maven.wagon.providers.http.httpclient.impl.io.AbstractSessionInputBuffer.read(AbstractSessionInputBuffer.java:195)
at
org.apache.maven.wagon.providers.http.httpclient.impl.io.ChunkedInputStream.read(ChunkedInputStream.java:173)
at
org.apache.maven.wagon.providers.http.httpclient.conn.EofSensorInputStream.read(EofSensorInputStream.java:138)
at
java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:238)
at
java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
at java.util.zip.GZIPInputStream.read(GZIPInputStream.java:116)
at
org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:493)
at
org.apache.maven.wagon.AbstractWagon.getTransfer(AbstractWagon.java:339)
... 9 more

Post by Wayne Fay
Can you try building your projects with Maven 3.0.4 in Windows (not in
the Cygwin environment) to see if there is any difference?

--
View this message in context: http://maven.40175.n5.nabble.com/Maven-3-0-3-hanging-having-timeouts-often-tp4388958p5664251.html
Sent from the Maven - Users mailing list archive at Nabble.com.