[
http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12379#comment-12379
]
Bram de Kruijff commented on AMDATUCASSANDRA-153:
-------------------------------------------------
As there is a version in the filename I imagine that changed adn fileinstall
uses the path as bundle-location. in this case AFAIK it is spec compliant
behavior of ConfigurationAdmin to refuse the config update to the new bundle.
OSGi Compendium R42 Ch 104.4.1 specifies this behavior motivated as a
"security" feature.
> Startup fails with a new version of an amdatu application bundle
> ----------------------------------------------------------------
>
> Key: AMDATUCASSANDRA-153
> URL: http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-153
> Project: Amdatu Cassandra
> Issue Type: Bug
> Components: Cassandra daemon
> Affects Versions: 0.2.2
> Reporter: Arthur Meijer
>
> Starting amdatu with a new version of cassandra application fails:
> *ERROR* Cannot use configuration org.amdatu.core.cassandra.application
> for [org.osgi.service.cm.ManagedService, id=21, bundle=67]:
> Configuration bound to bundle
> file:/data/blueconic/deploy/org.amdatu.cassandra.application-0.2.2-SNAPSHOT.jar
> The server needs to be stopped and started again for a successful startup
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
