Troubleshooting

• What do I do if I can't connect to the selected framework?

  A possible reason is that the IP address or domain name supplied in the settings is wrong.

  The connection to the remote framework may be also impossible because the remote OSGi framework running on that host is down.

  The OSGi framework is not running the IAgent bundle.

  The firewall of your PC might be switched on and the ports used for communication with the OSGi environment might be blocked. Make sure that ports 1450, 7365 and 5670 are open on the development computer.

• What do I have to do if I change my bundle after I have installed it on the framework?

  To reflect the changes to your bundle on the target OSGi framework, you need to update that bundle.

• What do I do if the OSGi framework refuses to accept and install my bundle?

  A possible reason might be incorrect bundle - missing native libraries, incorrect manifest etc.

• What do I do if my bundle does not perform any action on the OSGi framework?

  Perhaps you have forgotten to start it. Installing a bundle is not enough to make it handle its tasks within the OSGi framework. The installation only enables the framework to resolve the bundle's packages and make them available to the rest of the bundles. You must start it after installing it to observe any other results.

• What do I do if the framework refuses to start my bundle?

  This problem may be due to errors in the bundle activator or the bundle's services. Another possible reason is missing import packages or services. In any case, the error dialog that appears gives a hint on the exact reason.

  If the problem is determined by the behavior of the activator or services, you may view the ERROR and EXCEPTION levels of the Log Service. To do this, enter the Console view and locate the console of the target framework. Use the relevant console command for getting generated logs.