Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 357803

Summary:	[update] [restart] changes to .ini file are not picked up in a restart, user needs to manually stop/start
Product:	[Eclipse Project] Equinox	Reporter:	Helmut J. Haigermoser <helmut.haigermoser>
Component:	Launcher	Assignee:	Project Inbox <equinox.launcher-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	major
Priority:	P3	CC:	erwan.legeleux, remy.suen, rolf.theunissen, tobias.brieden
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Helmut J. Haigermoser

2011-09-15 09:49:35 EDT

Build Identifier: 3.7.1

When restarting after updates were applied to a product the system does not pick options from the .ini file. Two issues I've seen recently:
1.) vmargs were not picked up
2.) obsolete option was not removed

In both cases the .ini file was updated correctly, but the platform did not recognize the changes, I assume that's because the ini file was not re-read by the launcher in the restart.

All changes are fine if Eclipse is ended and manually started again

Reproducible: Always

Steps to Reproduce:
1. Manufacture a product, application args: "-option -vmargs -Xmx96"
2. Install product
3. Manufacture an update for the product, new args: "-vmargs -Xmx256m"
4. Update the product
5. Attach to the restarted jvm using jconsole to see the memory limits, also check the logs to see if option -option was still present

Comment 1 erwan legeleux

2016-02-07 17:04:57 EST

I have same problem with environment variables set in Windows.
I have to stop and start my workspace to make my change, restart does not work.

Comment 2 Tobias Brieden

2017-07-24 10:18:31 EDT

The same problem exists during an update of an Eclipse installation. If the update ships a new launcher, the eclipse.ini will be updated to point to the new jar; for example:

-startup
plugins/org.eclipse.equinox.launcher_1.3.200.v20160318-1642.jar

However, after the recommended restart after the update, the new launcher code is not used. Instead, the initial version is loaded again. This becomes especially problematic, if a second update is performed without an intermediate manual stop and re-start. During the second update the launcher jar is again replaced with a new version, but the restart will still try to load the initial version. Since, the P2 system only stores the current and the previous version of a bundle but removes and older versions (and therefore the initially installed version of the launcher) the restart will crash. 

This can be reproduced by updating from Eclipse 4.2.2 to Eclipse 4.3 to Eclipse 4.4. But the problem also still exists in Eclipse 4.7.

Comment 3 Tobias Brieden

2017-07-24 10:20:14 EDT

The same problem is reported in the following bug report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=323565

Comment 4 Eclipse Genie

2019-10-12 03:38:18 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 5 Rolf Theunissen

2019-12-19 07:57:39 EST


*** This bug has been marked as a duplicate of bug 323565 ***