]
Denis Golovin commented on JBDS-4343:
-------------------------------------
There is nothing we could really do here. What installer does is just call Eclipse
p2-director and gives it repository URL inside jar and target destination.
There were no changes in installer related to this, there might be something related to
changes in repository itself.
Also we might need to look at latest p2-director eclipse application and update our
modified version here
Installation hangs on 'Configuring
toolingorg.eclipse.equinox.launcher.*'
-------------------------------------------------------------------------
Key: JBDS-4343
URL:
https://issues.jboss.org/browse/JBDS-4343
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: installer
Affects Versions: 10.4.0.AM2
Environment: devstudio-10.4.0.AM2-v20170330-1543-B348-installer-standalone.jar
Reporter: Jan Richter
Assignee: Denis Golovin
Attachments: install.png
The installer spends several minutes in this state:
!install.png|thumbnail!
Just for comparison
- AM1 installation takes total of about 2 minutes 15 seconds
- AM2 takes 5 minutes 40 seconds
There is no shortage of memory or disk I/O availability, the CPU is not topped off (even
though AM2 eats up more CPU itself during this time).
DTRACE=true reveals nothing interesting really, this is what it says in the particular
moment (notice how much time the operation takes):
{noformat}
Configuring toolingorg.eclipse.equinox.launcher.gtk.linux.x86_64
Preparing to commit the provisioning operation.
Committing the provisioning operation.
Operation completed in 289855 ms.
{noformat}