07. Troubleshooting

Here is a list of some common problems with possible solutions.

Problem	Possible Solution
"Could not resolve module" message during start up.	Check that all required plug-ins are included in your product configuration. Make sure that your product defines dependencies to all required plug-ins or features. Bundles may also require a certain version of the Java virtual machine, e.g., a bundle may require Java 1.6 and will therefore not load in a Java 1.5 VM. Check the MANIFEST.MF file on the Overview tab in the Execution Environments section which Java version is required.
"java.lang.RuntimeException: No application id has been found." message during start up.	See "Could not resolve module" message during start up error. In most cases also triggered by a missing plug-in dependency.
Strange behavior but no error message.	Check if your run configuration includes the -consoleLog parameter. This option allows you to see errors from Eclipse based applications in the Console view of the Eclipse IDE.
Runtime configuration is frequently missing required plug-ins.	Make sure that your product or your feature(s) includes all required dependencies.
A change in the product Dependencies tab is not reflected in the run configuration (e.g., a new plug-in is added but is not included in the run configuration)	A product updates an existing run configuration if you start the product directly from the product definition file. If you select the run configuration directly, it will not be updated.
Application model changes are not reflected in the Eclipse 4 application.	Eclipse 4 persists user changes in the application in a delta file which is restored at startup. During development this might lead to situations where model changes are not correctly applied to the runtime model, e.g., you define a new menu entry and this entry is not displayed in your application. Either set the Clear flag on the Main tab in your run configuration or add the clearPersistedState parameter for your product configuration file or run configuration.
Services, e.g., key bindings or the selection service, are not working in an Eclipse 4 application.	In Eclipse releases before 4.3 every part needed to implement a @Focus method which places the focus on an SWT control. This error does not occur anymore with Eclipse 4.3 or a higher release.
Menu entries are disabled in the Eclipse application.	Ensure that the HandlerProcessingAddon class in the package org.eclipse.e4.ui.internal.workbench.addons is registered as model add-on. The bundle symbolic name is org.eclipse.e4.ui.workbench.
Application "org.eclipse.ant.core.antRunner" could not be found in the registry or Application could not be found in the registry.	Ensure that you have pressed the New... button in the product configuration file and selected the E4Application as application to start. You can check the current setting in your plugin.xml file on the Extensions tab and in the details of the org.eclipse.core.runtime.products extension.
TaskManagerImpl - Client is not, or no longer, connected.	You should restart 'Lider Ahenk XMPP Client' bundle on karaf.
Where is the log file?	Log file can usually be found under workspace/.metadata/.log. See here for more info.