You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2014/07/22 07:06:38 UTC
[jira] [Resolved] (SM-2287) Bundle refresh problem when eventadmin
is installed
[ https://issues.apache.org/jira/browse/SM-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved SM-2287.
---------------------------------
Resolution: Fixed
Assignee: Gert Vanthienen
> Bundle refresh problem when eventadmin is installed
> ---------------------------------------------------
>
> Key: SM-2287
> URL: https://issues.apache.org/jira/browse/SM-2287
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: 5.0.0, 5.0.1, 5.1.0, 6.0.0
> Reporter: Krzysztof Sobkowiak
> Assignee: Gert Vanthienen
> Fix For: 5.0.3, 5.1.1
>
> Attachments: activiti-install-output-after-restart.txt, activiti-install-output-initial.txt, bundle-list-while-freezing.txt, servicemix.log
>
>
> Pro problem was observed when the installation of {{activiti}} feature frozen the ServiceMix with installed {{eventadmin}} feature. At the end of the installation some Spring bundles are refreshed
> {code}
> karaf@root> features:install -v activiti
> Installing feature activiti 5.15.1
> Installing feature jpa 1.0.1
> ...
> Installing bundle mvn:org.activiti/activiti-osgi/5.15.1
> Installing bundle mvn:org.activiti/activiti-spring/5.15.1
> Installing bundle mvn:org.activiti/activiti-bpmn-converter/5.15.1
> Refreshing bundles org.springframework.context.support (73), org.springframework.context (72), org.springframework.transaction (104)
> {code}
> Full output attached. This process never stops and the container freezes. After killing the container and starting again, the {{activiti}} feature can be installed and only few bundles are installed (in opposite to the initial install) -- probably most of the bundles have been installed before the failed bundle refresh
--
This message was sent by Atlassian JIRA
(v6.2#6252)