Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343165 - Eclipse hang when importing project: Retrieving listing
Summary: Eclipse hang when importing project: Retrieving listing
Status: CLOSED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-18 11:00 EDT by Julien HENRY CLA
Modified: 2021-04-19 13:22 EDT (History)
7 users (show)

See Also:


Attachments
Full session log output in DEBUG mode (45.88 KB, text/plain)
2011-04-19 03:42 EDT, Julien HENRY CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Julien HENRY CLA 2011-04-18 11:00:07 EDT
Build Identifier: I20110310-1119

I'm testing latest snapshot of m2eclipse and I have a blocking issue. When I try to import existing project into workspace, import wizard hangs after selecting source folder. The message is "Retrieving listing" and it last forever. Of course unable to close the modal window as it say there is an active operation. Unable to cancel the task (red button is clickable but ineffective as usual ;) ) I tried to kill Eclipse and restart but still same issue. I suspect an infinite timeout issue. I tried to unplug my network cable. I tried to disable my corporate proxy, resulting in the following message in logs:
!ENTRY org.eclipse.m2e.logback.appender 4 0 2011-04-18 16:08:13.615
!MESSAGE Status ERROR: org.eclipse.equinox.p2.discovery code=0 Failed to discover all connectors. null children=[Status ERROR: org.eclipse.equinox.p2.discovery code=0 M2ERemoteBundleDiscoveryStrategy failed with an error org.eclipse.equinox.p2.core.ProvisionException: Unknown Host: http://download.eclipse.org/technology/m2e/discovery/directory.xml]

But still the wizard will hang...

eclipse.buildId=I20110310-1119
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=fr_FR

  m2e - Maven Integration for Eclipse (Incubation)    0.13.0.201104180713    org.eclipse.m2e.feature.feature.group

After killing Eclipse and trying again several times, it finally worked. Maybe a race condition...

Reproducible: Sometimes
Comment 1 Igor Fedorenko CLA 2011-04-18 19:56:27 EDT
We will need AHC debug log when this hang happens to be able to troubleshoot this. You can enable AHC debug log, set <logger name="com.ning.http.client" level="DEBUG"/> in /workspaces/m2e-dev/.metadata/.plugins/org.eclipse.m2e.logging/logback.*.xml file.
Comment 2 Julien HENRY CLA 2011-04-19 03:32:48 EDT
(In reply to comment #1)
For me the log configuration was in .metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.0.13.0.201104180713.xml

I have enabled DEBUG logs, started Eclipse then tried an import of a project and I had the bug again. The import process was started at 09:23.

2011-04-19 09:18:40,255 [New I/O client worker #6-2] DEBUG c.n.h.c.p.n.NettyAsyncHttpProvider -

Request DefaultHttpRequest(chunked: false)
GET http://mirrors.ibiblio.org/pub/mirrors/maven2/dot-index/nexus-maven-repository-index.properties HTTP/1.1
Host: mirrors.ibiblio.org
Accept-Encoding: gzip
Connection: keep-alive
Proxy-Connection: keep-alive
Proxy-Authorization: Basic UzI3Njk3OlMyNzY5Nw==
Accept: */*
User-Agent: m2e/3.7.0.v20110304/0.13.0.201104180713

Response DefaultHttpResponse(chunked: false)
HTTP/1.0 200 OK
Content-Type: application/octet-stream
Accept-Ranges: bytes
ETag: "1789840817"
Last-Modified: Mon, 18 Apr 2011 08:32:05 GMT
Content-Length: 1130
Date: Tue, 19 Apr 2011 06:43:39 GMT
Server: lighttpd/1.4.26
X-Cache: MISS from proxy-net-2.mycompany.fr
X-Cache-Lookup: HIT from proxy-net-2.mycompany.fr:8080
Via: 1.0 proxy-net-2.mycompany.fr:8080 (squid/2.6.STABLE6)
Age: 2150
X-Cache: HIT from proxy.dtni.mycompany.fr
Proxy-Connection: keep-alive

2011-04-19 09:18:40,255 [New I/O client worker #6-2] DEBUG c.n.h.c.p.n.NettyAsyncHttpProvider - Adding uri: http://mirrors.ibiblio.org:80 for channel [id: 0x52ace533, /10.244.122.176:50288 => proxy/10.241.9.9:3128]
2011-04-19 09:18:41,630 [Worker-0] INFO  o.e.m.c.i.index.NexusIndexManager - Updated index for repository: uk|http://uk.maven.org/maven2/ in 2243 ms
2011-04-19 09:23:45,700 [ModalContext] WARN  org.eclipse.core.runtime - CatalogItem org.eclipse.m2e.discovery.lifecyclemapping.m2e-egit does not contain lifecycle mapping metadata

I don't think it is very interesting. Anything else I can do.
Comment 3 Julien HENRY CLA 2011-04-19 03:42:57 EDT
Created attachment 193549 [details]
Full session log output in DEBUG mode

This time I have enabled DEBUG also for root logger. See attached log output.
Comment 4 Igor Fedorenko CLA 2011-04-19 15:21:49 EDT
If you have time, can you also provide p2 transport debug log messages as explained in http://wiki.eclipse.org/Equinox/p2/TransportDebugging ?
Comment 5 Julien HENRY CLA 2011-04-20 03:28:18 EDT
(In reply to comment #4)
> If you have time, can you also provide p2 transport debug log messages as
> explained in http://wiki.eclipse.org/Equinox/p2/TransportDebugging ?

I tried to add the properties to eclipse.ini, but it doesn't seem to produce any result. Where am I supposed to see the p2 transport logs? The workspace/.metadata/.log file do not contains anything more...
Comment 6 Igor Fedorenko CLA 2011-04-20 07:00:42 EDT
Did you check if p2 writes to STDOUT? Unfortunately, I am not familiar with p2 transport layer, so don't know for sure where to look for logs.

This particular dialog uses both m2e/maven and p2 transports, so I am trying to determine which part hangs and debug logs I can forward to relevant developers.
Comment 7 Julien HENRY CLA 2011-04-20 09:33:52 EDT
Nope, nothing in STDOUT. I'm not sure the parameters I put in eclipse.ini are taken into account. But I don't know any other way to give parameters to Eclipse jvm.
Comment 8 Igor Fedorenko CLA 2012-05-21 11:22:22 EDT
Closing old/stale bugreports.
Comment 9 Damon Horrell CLA 2012-07-12 23:13:04 EDT
This is still an issue in the latest Eclipse Juno (and also in Indigo).

Hangs on importing existing project.  Just displays Retrieving listing http://download.eclipse.org/technology/m2e/discovery/directory-1.1.xml

I get this issue regularly.  Sometimes I leave it for a hour or so, other times I think it goes away if I kill Eclipse and try again several times.
Comment 10 Joseph Lust CLA 2012-08-01 11:51:29 EDT
(In reply to comment #9)
> I get this issue regularly.  Sometimes I leave it for a hour or so, other
> times I think it goes away if I kill Eclipse and try again several times.

We've been experiencing the same issue. It hangs on importing Maven projects when you select the directory and takes about 20min of just trying to get this xml file before finally showing the valid POM files in the directory. This is running on a new Macbook Pro with SSD, with everything local (no network shares or anything like that). Very unusual. Please reopen.

Eclipse 3.7.2
OSX 10.7.4
Java 1.6
xmx 2G
xms 512M
m2e - Maven Integration for Eclipse	1.1.0.20120530-0009
m2e - slf4j over logback logging (Optional)	1.1.0.20120530-0009
m2e connector for mavenarchiver pom properties	0.14.0.201109270543

Thanks.
Comment 11 Igor Fedorenko CLA 2012-08-01 11:59:55 EDT
take jvm thread dump when eclipse is in the hung state and attach it here
Comment 12 Petr Panuska CLA 2012-08-10 08:38:38 EDT
Actually, I experience similar behavior and I believe this problem has something to do with proxy settings.

I'm using
Version: Indigo Service Release 2
Build id: 20120216-1857

(with built-in m2e plug-in).

When trying to import an existing maven project, I get the list of poms (nearly immediatelly) but I cannot select any.

When selecting the pom, Eclipse just says:
Can't import project SDDG from an existing workspace folder

The interesting messages in workspace\.metadata\.log file are (they appear when retrieving data just before poms get listed):

!SESSION 2012-08-10 06:14:18.346 -----------------------------------------------
eclipse.buildId=M20120208-0800
java.version=1.7.0_03
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.java.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product

!ENTRY org.eclipse.m2e.logback.appender 2 0 2012-08-10 06:14:54.986
!MESSAGE CatalogItem org.eclipse.m2e.discovery.lifecyclemapping.m2e-egit does not contain lifecycle mapping metadata

!ENTRY org.eclipse.m2e.logback.appender 2 0 2012-08-10 06:14:54.992
!MESSAGE CatalogItem org.eclipse.m2e.discovery.lifecyclemapping.m2e-cvs does not contain lifecycle mapping metadata

!ENTRY org.eclipse.m2e.logback.appender 2 0 2012-08-10 06:14:54.994
!MESSAGE CatalogItem org.eclipse.m2e.discovery.lifecyclemapping.m2e-subversive does not contain lifecycle mapping metadata

!ENTRY org.eclipse.m2e.logback.appender 2 0 2012-08-10 06:14:54.996
!MESSAGE CatalogItem org.eclipse.m2e.discovery.lifecyclemapping.m2e-subclipse does not contain lifecycle mapping metadata

!ENTRY org.eclipse.m2e.logback.appender 2 0 2012-08-10 06:14:54.997
!MESSAGE CatalogItem org.eclipse.m2e.discovery.maven-runtime-3.0.3 does not contain lifecycle mapping metadata

!ENTRY org.eclipse.m2e.logback.appender 2 0 2012-08-10 06:14:55.020
!MESSAGE CatalogItem org.codehaus.groovy.m2eclipse does not contain lifecycle mapping metadata

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

Please note that I'm behing a proxy!
It was a bit tricky to setup maven + Eclipse proxy but I believe I managed to set it up correctly.
maven: provided the proxy settings in C:\Users\Administrator\.m2\settings.xml file
Eclipse: Window \ Preferences \ General \ Network Connections - Active Provider set to Native (so SOCKs is not used)
  - restart Eclipse (otherwise experienced following messages in .log file and was not able to retrieve the http://download.eclipse.org/technology/m2e/discovery/directory.xml file)

!ENTRY org.eclipse.core.net 1 0 2012-08-10 06:13:18.903
!MESSAGE System property http.proxyHost is not set but should be 156.152.46.12.

!ENTRY org.eclipse.core.net 1 0 2012-08-10 06:13:18.905
!MESSAGE System property http.proxyPort is not set but should be 8088.
Comment 13 Petr Panuska CLA 2012-08-10 09:51:30 EDT
So it DOES NOT relate to a proxy.
Just tried to open the same pom on another machine with no proxy settings and got to the very same problem:
CatalogItem ... does not contain lifecycle mapping metadata
Comment 14 Matthew Piggott CLA 2012-08-10 10:11:59 EDT
(In reply to comment #13)
> So it DOES NOT relate to a proxy.
> Just tried to open the same pom on another machine with no proxy settings
> and got to the very same problem:
> CatalogItem ... does not contain lifecycle mapping metadata

That message is entirely unrelated.

Also note that your proxy settings in Eclipse are not used by m2e for maven builds.
Comment 15 Petr Panuska CLA 2012-08-10 10:17:39 EDT
I just found the issue.

It was because my pom.xml file was stored right under workspace folder.

When I moved that into a sub-folder, it started working.

Eclipse just sucks.
Comment 16 Denis Roy CLA 2021-04-19 13:22:19 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/