Core: error handling while plugin start

[jri]

When an error occurs very early in the plugin's starting phase that error is not logged and the plugin is retried to start endlessly (once per second). In particular this happens when an error occurs while reading the plugin.properties config file.

[Jörg Richter]

Core: error handling while plugin start (#693).

When an error occurs very early in the plugin's starting phase (e.g. while reading the plugin.properties file) that error is logged and the plugin is not retried to start endlessly.

See #693.

• Changeset: 3786682c6a459660eee7ada1541e890719c2aee4
• URL: ​https://github.com/jri/deepamehta/commit/3786682c6a459660eee7ada1541e890719c2aee4

[Jörg Richter]

Core: error handling while plugin start (#693).

When an error occurs very early in the plugin's starting phase (e.g. while reading the plugin.properties file) that error is logged and the plugin is not retried to start endlessly.

See #693.

• Changeset: 3786682c6a459660eee7ada1541e890719c2aee4
• URL: ​https://github.com/jri/deepamehta/commit/3786682c6a459660eee7ada1541e890719c2aee4

[jri]

There is yet another error handling problem: when actually an Error like NoClassDefFoundError (that is not an Exception) occurs while plugin startup that error might still be thrown through the OSGi container causing the known problem: that error is not logged and the plugin is retried to start endlessly.

So we must catch Throwable (instead of Exception) in all methods invoked by the OSGi container.

[Jörg Richter]

Core: fix plugin start error handling (#693).

Errors like NoClassDefFoundError are not thrown through the OSGi container.
The phenomenon of "swallowed" exceptions and endlessly retried plugin starts is eliminated once and for all!!

Close #693.

• Changeset: 8ef02dda24afe01eb6d6bae191289e8443b8716c
• URL: ​https://github.com/jri/deepamehta/commit/8ef02dda24afe01eb6d6bae191289e8443b8716c

[jri]

Though not related to plugin start but related to error handling: when an error occurs while event handling, in particular an error caused by an outdated plugin (not yet adapted to Core API changes) like NoSuchMethodError or AbstractMethodError the log is not very telling. The log should be more informative in that case.

[Jörg Richter]

More telling log in case of updated plugin (#693).

When an error occurs while event handling, in particular an error caused by an outdated plugin (not yet adapted to Core API changes) like NoSuchMethodError or AbstractMethodError the log is more informative in that case.

Close #693.

• Changeset: 489c7a5dd9d63a13f1ff4d1343ef35485512c65f
• URL: ​https://github.com/jri/deepamehta/commit/489c7a5dd9d63a13f1ff4d1343ef35485512c65f

[Jörg Richter]

Core: fix plugin start error handling (#693).

Errors like NoClassDefFoundError are not thrown through the OSGi container.
The phenomenon of "swallowed" exceptions and endlessly retried plugin starts is eliminated once and for all!!

Close #693.

• Changeset: 8ef02dda24afe01eb6d6bae191289e8443b8716c
• URL: ​https://github.com/jri/deepamehta/commit/8ef02dda24afe01eb6d6bae191289e8443b8716c

[Jörg Richter]

More telling log in case of updated plugin (#693).

When an error occurs while event handling, in particular an error caused by an outdated plugin (not yet adapted to Core API changes) like NoSuchMethodError or AbstractMethodError the log is more informative in that case.

Close #693.

• Changeset: 489c7a5dd9d63a13f1ff4d1343ef35485512c65f
• URL: ​https://github.com/jri/deepamehta/commit/489c7a5dd9d63a13f1ff4d1343ef35485512c65f