You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2021/09/21 09:23:00 UTC

[jira] [Resolved] (FELIX-6429) IllegalArgumentException that should not happen

     [ https://issues.apache.org/jira/browse/FELIX-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls resolved FELIX-6429.
-------------------------------
    Fix Version/s:     (was: framework-7.0.2)
       Resolution: Won't Fix

Hi [~jalbert], I talked about this a bit with [~tjwatson] and [~cziegeler] - we think this is working as designed as technically, when the service is unregistered, it is not provided by the ServiceObjects anymore. It should have the same effect in equinox/RI. 

I'll close this one as Won't Fix - if you think this should be clarified it probably should be done in OSGi first. 

> IllegalArgumentException that should not happen
> -----------------------------------------------
>
>                 Key: FELIX-6429
>                 URL: https://issues.apache.org/jira/browse/FELIX-6429
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: framework-7.0.0
>            Reporter: Jürgen Albert
>            Assignee: Karl Pauls
>            Priority: Major
>
> We recently stumbled a couple of times over an IllegalArgumentException when calling ServiceObjects.ungetService. In our case we are always in an async process and the service we are calling unget for ist already unregistered. According to the org.osgi.framework.ServiceObjects Spec the Exception will be thrown under the following circumstances:
> {code:java}
>  @throws IllegalArgumentException If the specified service object is
> 	 {@code null} or was not provided by a {@code ServiceObjects}
> 	 object for the associated service.
> {code}
> I can guarantee that both conditions are not meet in our case. It is simply that the service is already unregistered.
> If I read the javadoc correctly it should simply do nothing in such a case. I haven't checked with the Spec though.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)