You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2015/12/02 21:24:11 UTC

[jira] [Commented] (KARAF-4167) Accidently shared config files diagnosed

    [ https://issues.apache.org/jira/browse/KARAF-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036537#comment-15036537 ] 

Jean-Baptiste Onofré commented on KARAF-4167:
---------------------------------------------

You are right: it's BAD to use the same PID for two @Components (or generally speaking for ManagedService). And you are right, at least a log message would be helpful. Let me take a look as I'm not sure it's only Karaf related.

> Accidently shared config files diagnosed
> ----------------------------------------
>
>                 Key: KARAF-4167
>                 URL: https://issues.apache.org/jira/browse/KARAF-4167
>             Project: Karaf
>          Issue Type: Improvement
>            Reporter: Benson Margulies
>
> If you stupidly tell two different @Components to use the same configurationPid, one of them will just get stuck, and neither bundle:services nor any of the scr commands will reveal what the problem is. It sure would be nice to have a log message, or some detail from one of the commands.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)