[jira] [Updated] (ARIES-1766) Configure log severity for Whiteboard JMX registration exceptions

[David Bosschaert (JIRA)]

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

David Bosschaert updated ARIES-1766:

Fix Version/s: jmx-whiteboard-1.2.0

> Configure log severity for Whiteboard JMX registration exceptions
> -
>
> Key: ARIES-1766
> URL: https://issues.apache.org/jira/browse/ARIES-1766
> Project: Aries
>  Issue Type: Bug
>  Components: JMX
>Affects Versions: jmx-1.1.5
>Reporter: David Bosschaert
>Assignee: David Bosschaert
> Fix For: jmx-whiteboard-1.2.0
>
>
> When Aries JMX Whiteboard registers MBeans (in 
> {{org.apache.aries.jmx.whiteboard.MBeanHolder}}) a number of exceptions, 
> including {{InstanceAlreadyExistsException}} are caught and logged at 
> {{error}} level. 
> Depending on the context these messages may not really be errors, but rather 
> warnings. It would be good to be able to configure Aries JMX wrt to how these 
> exceptions are logged, allowing certain ones to appear as warnings in the log 
> instead.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARIES-1630) jmx core fails if configadmin is not present

[David Bosschaert (JIRA)]

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

David Bosschaert updated ARIES-1630:

Fix Version/s: jmx-whiteboard-1.2.0

> jmx core fails if configadmin is not present
> 
>
> Key: ARIES-1630
> URL: https://issues.apache.org/jira/browse/ARIES-1630
> Project: Aries
>  Issue Type: Bug
>  Components: JMX
>Affects Versions: jmx-core-1.1.7
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: jmx-core-1.1.8, jmx-whiteboard-1.2.0
>
>
> JMX core claims it has an optional dependency to config admin. In the 
> Activator though it directly accesses StateConfig which depends on config 
> admin. 
> So the fix is to make config admin spec mandatory.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ARIES-1707) The BlueprintMetadata.getBlueprintContainer throws inconsistent exceptions

[David Bosschaert (JIRA)]

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

David Bosschaert updated ARIES-1707:

Fix Version/s: (was: jmx-1.2.0)
   jmx-blueprint-core-1.2.0
   jmx-blueprint-api-1.2.0

> The BlueprintMetadata.getBlueprintContainer throws inconsistent exceptions
> --
>
> Key: ARIES-1707
> URL: https://issues.apache.org/jira/browse/ARIES-1707
> Project: Aries
>  Issue Type: Bug
>  Components: JMX
>Reporter: Hao Zhong
>Assignee: Guillaume Nodet
> Fix For: jmx-blueprint-api-1.2.0, jmx-blueprint-core-1.2.0
>
> Attachments: aries.patch
>
>
> The BlueprintMetadata_getBlueprintContainer method throws 
> IllegalArgumentException as follow:
> {code:title=BlueprintMetadata.java|borderStyle=solid}
>  if (serviceReferences == null || serviceReferences.length <1) {
> throw new IllegalArgumentException("Invalid BlueprintContainer 
> service id: " + containerServiceId);
> }
> {code}
> However, the FrameworkUtils_resolveService method throws IOException for the 
> same condition:
> {code:title=FrameworkUtils.java|borderStyle=solid}
> if (references == null || references.length < 1) {
> throw new IOException("Service with id [" + serviceId + "] 
> not found");
> } else {
> result = references[0];
> }
> {code}
> This is confusing. Indeed, I notice that the buggy code of ARIES-333 throws 
> IllegalArgumentException, but the fixed code throws IOException.
> The current BlueprintMetadata.java shall be modified to eliminate the 
> confusing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[RESULT][VOTE] Release Aries JMX components (take 2)

[David Bosschaert]

This vote is now concluded, with
3 binding +1s
1 non-binding +1
one -1 which is not meant to be a veto and was resolved on this thread.

I'll promote the artifacts.

David


On 2 January 2018 at 13:10, David Bosschaert 
wrote:

> Hi all,
>
> I'm calling a vote on various Aries JMX components, now with versions
> updated from 1.2 to 1.2.0.
> The org.apache.aries.jmx.api component has not changed since the last
> release and is thus not included in this set.
>
> org.apache.aries.jmx.core version 1.1.8
> org.apache.aries.jmx.core.whiteboard version 1.1.6
> [ARIES-1630] jmx core fails if configadmin is not present
>
> org.apache.aries.jmx.blueprint.api version 1.2.0
> org.apache.aries.jmx.blueprint.core version 1.2.0
> [ARIES-1707] BlueprintMetadata.getBlueprintContainer throws inconsistent
> exceptions
>
> org.apache.aries.jmx.whiteboard version 1.2.0
> [ARIES-1766] Configure log severity for Whiteboard JMX registration
> exceptions
> [ARIES-1630] jmx core fails if configadmin is not present
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachearies-1123
>
> Please vote:
>
>  +1 Approve the release
>  -1 Do not approve the release (please explain why)
>
> This vote will be open for at least 72 hours.
>
> Best regards,
>
> David Bosschaert
>

Re: [VOTE] Release Aries JMX components (take 2)

[Christian Schneider]

+1

Christian

2018-01-09 11:59 GMT+01:00 David Bosschaert :

> Hi all,
>
> I'd like to finish this release, but we need one more binding vote. As
> discussed we Dominik, the uber-bundles will not be released any more, and I
> can remove them from SVN going forward.
>
> @PMC members, please cast a vote so we can close this off?
>
> Many thanks,
>
> David
>
> On 7 January 2018 at 12:28, David Bosschaert 
> wrote:
>
> > Anyone else voting? We need one more binding vote...
> >
> > Cheers,
> >
> > David
> >
> > On 4 January 2018 at 06:29, Jean-Baptiste Onofré 
> wrote:
> >
> >> +1 (binding)
> >>
> >> Agree to not release uber bundles anymore (it's some changes to do in
> >> Karaf, but not a big deal).
> >>
> >> Regards
> >> JB
> >>
> >>
> >> On 01/02/2018 02:10 PM, David Bosschaert wrote:
> >>
> >>> Hi all,
> >>>
> >>> I'm calling a vote on various Aries JMX components, now with versions
> >>> updated from 1.2 to 1.2.0.
> >>> The org.apache.aries.jmx.api component has not changed since the last
> >>> release and is thus not included in this set.
> >>>
> >>> org.apache.aries.jmx.core version 1.1.8
> >>> org.apache.aries.jmx.core.whiteboard version 1.1.6
> >>> [ARIES-1630] jmx core fails if configadmin is not present
> >>>
> >>> org.apache.aries.jmx.blueprint.api version 1.2.0
> >>> org.apache.aries.jmx.blueprint.core version 1.2.0
> >>> [ARIES-1707] BlueprintMetadata.getBlueprintContainer throws
> inconsistent
> >>> exceptions
> >>>
> >>> org.apache.aries.jmx.whiteboard version 1.2.0
> >>> [ARIES-1766] Configure log severity for Whiteboard JMX registration
> >>> exceptions
> >>> [ARIES-1630] jmx core fails if configadmin is not present
> >>>
> >>> Staging repository:
> >>> https://repository.apache.org/content/repositories/orgapachearies-1123
> >>>
> >>> Please vote:
> >>>
> >>>   +1 Approve the release
> >>>   -1 Do not approve the release (please explain why)
> >>>
> >>> This vote will be open for at least 72 hours.
> >>>
> >>> Best regards,
> >>>
> >>> David Bosschaert
> >>>
> >>>
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
> >
> >
>



-- 
-- 
Christian Schneider
http://www.liquid-reality.de

Computer Scientist
http://www.adobe.com