[
http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12524#comment-12524
]
Ivo Ladage - van Doorn edited comment on AMDATUCASSANDRA-153 at 2/7/12 12:46 PM:
---------------------------------------------------------------------------------
Seems that this is a 'feature' of the Felix implementation of the
ConfigurationManagement service.
Code from org.apache.felix.cm.impl.ConfigurationManager, line 1135:
// 104.3 Ignore duplicate PIDs from other bundles and report
// them to the log
// 104.4.1 No update call back for PID already bound to another
// bundle location
// 104.4.1 assign configuration to bundle if unassigned
if ( !config.tryBindLocation( serviceBundle.getLocation() ) )
{
log( LogService.LOG_ERROR, "Cannot use configuration " + pid + " for "
+ ConfigurationManager.toString( sr ) + ": Configuration bound to bundle "
+ config.getBundleLocation(), null );
return;
}
In this case the bundle location has changed, hence the error.
was (Author: ivol):
Seems that this is a 'feature' of the Felix implementation of the
ConfigurationManagement service.
Code from org.apache.felix.cm.impl.ConfigurationManager, line 1135:
// 104.3 Ignore duplicate PIDs from other bundles and report
// them to the log
// 104.4.1 No update call back for PID already bound to another
// bundle location
// 104.4.1 assign configuration to bundle if unassigned
if ( !config.tryBindLocation( serviceBundle.getLocation() ) )
{
log( LogService.LOG_ERROR, "Cannot use configuration " + pid + " for "
+ ConfigurationManager.toString( sr ) + ": Configuration bound to bundle "
+ config.getBundleLocation(), null );
return;
}
In this case the bundle location has changed, hence the error.
> 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
> Priority: Critical
> Labels: blueconic
> Fix For: 0.2.3
>
>
> 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
