[
https://issues.apache.org/jira/browse/GERONIMO-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582110#action_12582110
]
Jarek Gawor commented on GERONIMO-3887:
---------------------------------------
I think there are two separate issues at hand here.
The problem I've ran into is that when a first plugin fails to install,
installing another plugin after that fails with an error
"org.apache.geronimo.kernel.config.LifecycleException: start of <previous
plugin name> failed". It looks like the installation of the second plugin tries
to (re)start the first plugin. And since first plugin cannot start (for
whatever reason) the above error message is displayed (even though the second
plugin installed fine but did not get started). So I think in this case the
problem is that when a plugin fails to install (or start really) it should be
marked as not loadable (setLoad(false)) so that next installation does not try
to start it.
The installation of jetty plugin on tomcat container (or vice versa) is a
separate issue and the regex idea to prevent that is still necessary.
> After installing with wrong configuration unable to proceed with any new
> plugin installs
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMO-3887
> URL: https://issues.apache.org/jira/browse/GERONIMO-3887
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 2.1, 2.1.1, 2.2
> Reporter: Joseph Leong
> Assignee: Joseph Leong
> Fix For: 2.1.1, 2.2
>
>
> The plugin installer located in the administration console fails to install
> new plugins once it runs into an install that throws an exception for being
> the wrong configuration type. IE. trying to install a Jetty piece on Tomcat.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
