Installing The Android Plugin For Eclipse

Artem Russakovskii — Thu, 15 Oct 2009 21:36:56 +0000

Today is my first day looking at Android development. My first encounter with the Android plugin for Eclipse has not been very smooth, to say the least. I am not sure if it's Android's or Eclipse's fault but I just wasted 2 hours on errors during the plugin installation and would like to pass on the time savings to you.

The plugin install page provides initial instructions and the location of the plugin to give Eclipse (https://dl-ssl.google.com/android/eclipse/). This is very standard stuff and I've installed many plugins exactly the same way. However, here's when problems started.

Problem #1: Error while loading manipulator

Eclipse just shows a cryptic Install failed box. Here are the highlights:

!MESSAGE Error while loading manipulator
java.lang.IllegalStateException: !fwConfigLocation.equals(fwPersistentDataLocation)

It looks like for whatever reason, Eclipse's fwConfigLocation variable does not match fwPersistentDataLocation. I have no idea where those come from and searching for a solution (such as this crazy Japanese sourceforge and this Eclipse bug), restarting Eclipse, and beating my head against the wall took the majority of my the 2 hours I spent on this.

Here's the full log, which will help people with the same problem find it in search engines:

!ENTRY org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2009-10-15 13:21:11.224
!MESSAGE Error while loading manipulator.
!STACK 0
java.lang.IllegalStateException: !fwConfigLocation.equals(fwPersistentDataLocation)
	!fwConfigLocation=C:\eclipse\configuration
	,fwPersistentDataLocation=C:\eclipse\plugins\configuration
	at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.checkConsistencyOfFwConfigLocAndFwPersistentDataLoc(EquinoxManipulatorImpl.java:65)
	at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.loadWithoutFwPersistentData(EquinoxManipulatorImpl.java:360)
	at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.load(EquinoxManipulatorImpl.java:331)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:50)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.uninstallBundle(UninstallBundleAction.java:74)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.execute(UninstallBundleAction.java:29)
	at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:35)
	at org.eclipse.equinox.internal.provisional.p2.engine.Phase.mainPerform(Phase.java:129)
	at org.eclipse.equinox.internal.provisional.p2.engine.Phase.perform(Phase.java:72)
	at org.eclipse.equinox.internal.provisional.p2.engine.PhaseSet.perform(PhaseSet.java:44)
	at org.eclipse.equinox.internal.provisional.p2.engine.Engine.perform(Engine.java:54)
	at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningUtil.performProvisioningPlan(ProvisioningUtil.java:389)
	at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProfileModificationOperation.doExecute(ProfileModificationOperation.java:61)
	at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningOperation.execute(ProvisioningOperation.java:37)
	at org.eclipse.equinox.internal.provisional.p2.ui.ProvisioningOperationRunner$1.run(ProvisioningOperationRunner.java:94)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
 
!ENTRY org.eclipse.equinox.p2.engine 4 4 2009-10-15 13:21:11.240
!MESSAGE An error occurred while uninstalling
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-10-15 13:21:11.240
!MESSAGE session context was:(profile=epp.package.php, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Uninstall, operand=[R]javax.activation 1.1.0.v200905021805 --> [R]javax.activation 1.1.0.v200906290531, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction).
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2009-10-15 13:21:11.240
!MESSAGE Error while loading manipulator.
!STACK 0
java.lang.IllegalStateException: Error while loading manipulator.
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.loadDelegate(LazyManipulator.java:54)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.LazyManipulator.getConfigData(LazyManipulator.java:108)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.uninstallBundle(UninstallBundleAction.java:74)
	at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.UninstallBundleAction.execute(UninstallBundleAction.java:29)
	at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:35)
	at org.eclipse.equinox.internal.provisional.p2.engine.Phase.mainPerform(Phase.java:129)
	at org.eclipse.equinox.internal.provisional.p2.engine.Phase.perform(Phase.java:72)
	at org.eclipse.equinox.internal.provisional.p2.engine.PhaseSet.perform(PhaseSet.java:44)
	at org.eclipse.equinox.internal.provisional.p2.engine.Engine.perform(Engine.java:54)
	at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningUtil.performProvisioningPlan(ProvisioningUtil.java:389)
	at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProfileModificationOperation.doExecute(ProfileModificationOperation.java:61)
	at org.eclipse.equinox.internal.provisional.p2.ui.operations.ProvisioningOperation.execute(ProvisioningOperation.java:37)
	at org.eclipse.equinox.internal.provisional.p2.ui.ProvisioningOperationRunner$1.run(ProvisioningOperationRunner.java:94)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SESSION 2009-10-15 13:31:40.853 -----------------------------------------------
eclipse.buildId=I20090611-1540
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

Finally, I found a solution that worked – modify eclipse.ini (the one that sits in elipse's install directory) and add the following:

-startup
file:/C:/eclipse/plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar
--launcher.library
file:/C:/eclipse/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519

Note that the exact locations may differ for you, so figure out what is installed on your machine and replace accordingly.

Also, it seems that the location of the file HAS to be on a new line – otherwise it is not recognized. What kind of shit is that, Eclipse? Some values in eclipse.ini are specified on the same line separated by space, some separated by '=', and some have to be on a new line? This fun trivia fact wasted about 45 minutes of my time.

And yes, startup has 1 dash and launcher.library has 2. /sigh

Edit: it looks like by default Eclipse does come with these options. I somehow managed to lose them, so this is probably my fault. The error couldn't be more cryptic though.

Problem #2: java.io.IOException: The file "C:\eclipse\features\com.android.ide.eclipse.adt_0.9.3.v200909031112-12945" does not exist

Great. Now what…

After examining the features directory, I indeed found that directory com.android.ide.eclipse.adt_0.9.3.v200909031112-12945 does not exist. What I did find though is com.android.ide.eclipse.adt_0.9.3.v200909031112-12945.jar, which is simply an archive. Why didn't you unpack this archive, Eclipse? Or Android plugin devs? Whoever is responsible for this – argh!

After quickly creating the directories and unpacking the .jar contents into them, Eclipse was finally able to install the Android plugin.

If installing a plugin is this friendly, I can only imagine what awaits me in Android app development. Am I the only one with these problems? You let me know.

[Solr] How To Fix java.io.IOException: directory FOO exists and is a directory, but cannot be listed: list() returned null

Artem Russakovskii — Mon, 21 Sep 2009 19:47:53 +0000

The Problem

I am throwing up a quick post about a relatively cryptic error that Solr started throwing the other day here at Plaxo. After happily running for a few days, I suddenly started getting pages about failed Solr indexing.

Upon closer examination, I saw the following repeatedly in the log file:

catalina.2009-09-18.log:SEVERE: java.io.IOException: directory 'DATADIR/index'
exists and is a directory, but cannot be listed: list() returned null

I tried to see if sending an OPTIMIZE command would help but the server returned the same response.

Digging Deeper

The reason was these errors was quite simple – Solr was running into the system level limit on allowed number of open files (ulimit). This limit can be seen by running

ulimit -n
1024

or simply

ulimit -a | grep 'open files'
open files                      (-n) 1024

This means that if a process tries to open that many files at the same time, the kernel will prohibit opening any more, which in my case caused the Java IOException.

In my case, I haven't been using the Solr OPTIMIZE command for a while, so after a lot of COMMITs, the Solr data got pretty fragmented, thus hitting the open files limit.

The Solution

There are 2 things to be done here:

OPTIMIZE Solr more often. When an OPTIMIZE occurs, multiple index files are merged into 1, thus reducing the number of files that need to be opened. However, before you can OPTIMIZE, you have to raise the allowed number of open files (see the next bullet).
Set a higher open files limit for the user that runs Solr (in my case, the solr user) – for example to 4096 instead of 1024. One way to do it is by adding a file /etc/security/limits.d/solr.conf with the following contents:
```
solr hard nofile 4096
solr soft nofile 4096
```
and then logging out and back in. The file should be automatically loaded, which you can verify by running the ulimit commands from the section above.

Happy Solring!

By the way, here's a really good resource for Solr 1.4 that just came out: Solr 1.4 Enterprise Search. I have this book and it's quite helpful in explaining such topics as multicore setup, search methods, replication, etc.