[
https://issues.apache.org/jira/browse/GERONIMO-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582057#action_12582057
]
Joseph Leong commented on GERONIMO-3887:
----------------------------------------
Update:
Ok good news, so rather than doing a filter on the higher level to prevent
users from installing misconfigurations. I am attacking the core of the
problem as it will solve more issues later.
So after further inspect, i can confirm what is happening. The
PluginInstallerGbean has no clean up procedure for if it it fails to install a
plugin. It will just set the downloadresult failure to true and make a log of
it. So the issue is hanging.
Approach to resolution:
In the PluginInstallerGBean , i've created an artifact list to keep track of
the history of dependencies and pieces that are being downloaded/installed .
Upon catching an exception for failure to start the artifact it will perform
the cleanup routine and uninstall the artifacts that is included in that plugin.
Thus far results looks promising.. further testing to confirm and a new patch
to be posted soon.
-Joseph Leong
> 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.
