Eclipse Community Forums: Java Development Tools (JDT) » Eclipse Photon ( for Java EE) stuck at starting up

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Eclipse Photon ( for Java EE) stuck at starting up

Show: Today's Messages :: Show Polls :: Message Navigator

Eclipse Photon ( for Java EE) stuck at starting up [message #1797991]

Fri, 09 November 2018 15:40

harry sheng

Messages: 62
Registered: July 2009

Member

Environment:
Windows 10,
Oracle JDK 10.0.2,
Photon Release (4.8.0) Build id: 20180619-1200

Eclipse stuck at starting up for 10+ minutes.
Found the following in the .log file (This is all I have in the .log file).

I've been using Photon on and off for a while now, shouldn't everything ever required have already been downloaded to local? Why does eclipse need to connect to the server every now and then, and causes trouble whenever there's network issue?

Does this mean if dev.eclipse.org is down, every Eclipse Photon user will have trouble using it?

Is it possible to configure Photon to work offline?

!SESSION 2018-11-09 10:25:15.594 -----------------------------------------------
eclipse.buildId=4.8.0.I20180611-0500
java.version=10.0.2
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_CA

!ENTRY org.eclipse.osgi 4 0 2018-11-09 10:25:16.453
!MESSAGE The -clean (osgi.clean) option was not successful. Unable to clean the storage area: C:\eclipse\photon\configuration\org.eclipse.osgi

!ENTRY org.eclipse.core.resources 2 10035 2018-11-09 10:25:38.968
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.core.net 4 0 2018-11-09 10:25:57.493
!MESSAGE WinHttp.GetProxyForUrl for pac failed with error 'The handle is invalid.
' #6.

!ENTRY org.eclipse.egit.ui 2 0 2018-11-09 10:25:58.551
!MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git
user global configuration and to define the default location to store repositories: 'C:\Users\harry'. If this is
not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and
EGit might behave differently since they see different configuration options.
This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.

!ENTRY org.eclipse.epp.logging.aeri.ide 2 17 2018-11-09 10:26:00.742
!MESSAGE Server 'org.eclipse.epp.logging.aeri.ide.server' failed with exception: Connect to dev.eclipse.org:443 [dev.eclipse.org/198.41.30.200] failed: connect timed out. ; version: 2.0.7.v20170906-1327
!STACK 0
org.apache.http.conn.ConnectTimeoutException: Connect to dev.eclipse.org:443 [dev.eclipse.org/198.41.30.200] failed: connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at org.apache.http.client.fluent.Request.internalExecute(Request.java:173)
at org.apache.http.client.fluent.Executor.execute(Executor.java:262)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.request(IO.java:170)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.refreshConfiguration(IO.java:64)
at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.startUp(ServerConnection.java:124)
at com.google.common.util.concurrent.AbstractIdleService$DelegateService$1.run(AbstractIdleService.java:62)
at com.google.common.util.concurrent.Callables$4.run(Callables.java:122)
at java.base/java.lang.Thread.run(Thread.java:844)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.base/java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.base/java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:400)
at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:243)
at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:225)
at java.base/java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148)
at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:402)
at java.base/java.net.Socket.connect(Socket.java:591)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:339)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
... 17 more

Report message to a moderator

Re: Eclipse Photon ( for Java EE) stuck at starting up [message #1798003 is a reply to message #1797991]

Sat, 10 November 2018 04:01

Ed Merks

Messages: 33210
Registered: July 2009

Senior Member

From the stack trace, that work is being done on a background thread so it shouldn't (at least in in principle) be blocking the UI thread.

To figure out what's actually holding up the UI thread, you could use these instructions the next time it happens:

https://wiki.eclipse.org/How_to_report_a_deadlock

Using jvisualvm is the approach I use when I'm trying to figure out why the UI itself is blocked:

https://wiki.eclipse.org/How_to_report_a_deadlock#Using_jvisualvm

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Eclipse Photon ( for Java EE) stuck at starting up [message #1798100 is a reply to message #1798003]

Mon, 12 November 2018 14:22

harry sheng

Messages: 62
Registered: July 2009

Member

The most frustrating thing with Oxygen, Photon and SimRel2018-09 of Eclipse is, a couple minute before, it worked perfectly fine, and suddenly everything slowed down, like taking a few seconds to toggle a breakpoint, a few seconds to switch from one file to another in the editor, etc.

This time, when Photon eventually started up, the IDE was in a unusable state. Nothing really works, expanding the source code tree takes one year, opening a java file takes another year, switching between opened java files takes forever. And nothing can be found in the .log file, except the network timeout.

A few minutes later, I killed the Eclipse process from windows task manager, and restarted Photon again. And it just healed it self! I did make any change whatsoever! Only that no network timeout in the .log file.

I've using Oxygen for quite some time now, I did not remember any problem with it before the official release of Photon, or SimRel2018-09 maybe. I fall back from Photon or SimRel2018-09 to Oxygen a couple times, and now I'm having the same headache with Oxygen! I guess next time I'll have to go back to Neon and see if it can give me a break.

Report message to a moderator

Re: Eclipse Photon ( for Java EE) stuck at starting up [message #1798105 is a reply to message #1798100]

Mon, 12 November 2018 14:59

harry sheng

Messages: 62
Registered: July 2009

Member

Ok, I guess the problem with Photon is largely related to the network issue.

I had a slow startup of Photon just now, and everything was slow after it eventually started up. When I checked the .log file, I saw this again:

!MESSAGE Server 'org.eclipse.epp.logging.aeri.ide.server' failed with exception: Connect to dev.eclipse.org:443 [dev.eclipse.org/198.41.30.200] failed: connect timed out. ; version: 2.0.7.v20170906-1327
!STACK 0
org.apache.http.conn.ConnectTimeoutException: Connect to dev.eclipse.org:443 [dev.eclipse.org/198.41.30.200] failed: connect timed out

So I added the following two lines in the eclipse.ini file (https://wiki.eclipse.org/EPP/Logging#Disabling_AERI_in_builds_and_runtime_Eclipse), and restarted Photon,
-Dorg.eclipse.epp.logging.aeri.skipReports=true
-Dorg.eclipse.epp.logging.aeri.ui.skipReports=true

Now, I see no more "connection timeout" in .log, and Photon seems startup quickly and work smoothly.

[Updated on: Mon, 12 November 2018 14:59]

Report message to a moderator

Previous Topic:	Using Eclipse compiler standalone with Java 11?
Next Topic:	Weird Java editor behaviour

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Sep 13 11:28:35 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter