You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Tang Kin Chuen (JIRA)" <ji...@apache.org> on 2011/03/16 01:19:29 UTC

[jira] Created: (ARIES-613) use error() instead of info() log in BeanRecipe's destroy() on exception

use error() instead of info() log in BeanRecipe's destroy() on exception
------------------------------------------------------------------------

                 Key: ARIES-613
                 URL: https://issues.apache.org/jira/browse/ARIES-613
             Project: Aries
          Issue Type: Bug
          Components: Blueprint
    Affects Versions: 0.3
            Reporter: Tang Kin Chuen
            Priority: Trivial


Suggesting to change the following line in org.apache.aries.blueprint.container.BeanRecipe's destroy() to LOGGER.error.

LOGGER.info("Error invoking destroy method", getRealCause(e));

2011-03-15 22:21:04,760 INFO  [Thread:Gogo shell] [8/org.apache.aries.blueprint/0.3.0]
org.apache.aries.blueprint.container.BeanRecipe - Error invoking destroy method
org.osgi.service.blueprint.container.ServiceUnavailableException: The Blueprint container is being or has been destroyed
	at org.apache.aries.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:176)
	at org.apache.aries.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:49)
	at org.apache.aries.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:201)
	at org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:50)

It is a trivial thing, but helps in troubleshooting.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (ARIES-613) use error() instead of info() log in BeanRecipe's destroy() on exception

Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ARIES-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alasdair Nottingham resolved ARIES-613.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: blueprint-0.4.0
         Assignee: Alasdair Nottingham

> use error() instead of info() log in BeanRecipe's destroy() on exception
> ------------------------------------------------------------------------
>
>                 Key: ARIES-613
>                 URL: https://issues.apache.org/jira/browse/ARIES-613
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: 0.3
>            Reporter: Tang Kin Chuen
>            Assignee: Alasdair Nottingham
>            Priority: Trivial
>             Fix For: blueprint-0.4.0
>
>
> Suggesting to change the following line in org.apache.aries.blueprint.container.BeanRecipe's destroy() to LOGGER.error.
> LOGGER.info("Error invoking destroy method", getRealCause(e));
> 2011-03-15 22:21:04,760 INFO  [Thread:Gogo shell] [8/org.apache.aries.blueprint/0.3.0]
> org.apache.aries.blueprint.container.BeanRecipe - Error invoking destroy method
> org.osgi.service.blueprint.container.ServiceUnavailableException: The Blueprint container is being or has been destroyed
> 	at org.apache.aries.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:176)
> 	at org.apache.aries.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:49)
> 	at org.apache.aries.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:201)
> 	at org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:50)
> It is a trivial thing, but helps in troubleshooting.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (ARIES-613) use error() instead of info() log in BeanRecipe's destroy() on exception

Posted by "Alasdair Nottingham (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ARIES-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007427#comment-13007427 ] 

Alasdair Nottingham commented on ARIES-613:
-------------------------------------------

I'm of two minds about this. The problem is not an error in blueprint, as indicated by [8/org.apache.aries.blueprint/0.3.0], but an error in the blueprint bean. As a result I'm concerned that while it is an error if we report it as an error it will cause people to raise bugs against blueprint, rather than looking to fix their code.

I'm of course talking general case here because this instance was caused by ARIES-612

> use error() instead of info() log in BeanRecipe's destroy() on exception
> ------------------------------------------------------------------------
>
>                 Key: ARIES-613
>                 URL: https://issues.apache.org/jira/browse/ARIES-613
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: 0.3
>            Reporter: Tang Kin Chuen
>            Priority: Trivial
>
> Suggesting to change the following line in org.apache.aries.blueprint.container.BeanRecipe's destroy() to LOGGER.error.
> LOGGER.info("Error invoking destroy method", getRealCause(e));
> 2011-03-15 22:21:04,760 INFO  [Thread:Gogo shell] [8/org.apache.aries.blueprint/0.3.0]
> org.apache.aries.blueprint.container.BeanRecipe - Error invoking destroy method
> org.osgi.service.blueprint.container.ServiceUnavailableException: The Blueprint container is being or has been destroyed
> 	at org.apache.aries.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:176)
> 	at org.apache.aries.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:49)
> 	at org.apache.aries.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:201)
> 	at org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:50)
> It is a trivial thing, but helps in troubleshooting.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (ARIES-613) use error() instead of info() log in BeanRecipe's destroy() on exception

Posted by "Jeremy Hughes (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ARIES-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremy Hughes updated ARIES-613:
--------------------------------

    Fix Version/s:     (was: blueprint-0.4.0)
                   blueprint.core-0.4
    
> use error() instead of info() log in BeanRecipe's destroy() on exception
> ------------------------------------------------------------------------
>
>                 Key: ARIES-613
>                 URL: https://issues.apache.org/jira/browse/ARIES-613
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: 0.3
>            Reporter: Tang Kin Chuen
>            Assignee: Alasdair Nottingham
>            Priority: Trivial
>             Fix For: blueprint.core-0.4
>
>
> Suggesting to change the following line in org.apache.aries.blueprint.container.BeanRecipe's destroy() to LOGGER.error.
> LOGGER.info("Error invoking destroy method", getRealCause(e));
> 2011-03-15 22:21:04,760 INFO  [Thread:Gogo shell] [8/org.apache.aries.blueprint/0.3.0]
> org.apache.aries.blueprint.container.BeanRecipe - Error invoking destroy method
> org.osgi.service.blueprint.container.ServiceUnavailableException: The Blueprint container is being or has been destroyed
> 	at org.apache.aries.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:176)
> 	at org.apache.aries.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:49)
> 	at org.apache.aries.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:201)
> 	at org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:50)
> It is a trivial thing, but helps in troubleshooting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (ARIES-613) use error() instead of info() log in BeanRecipe's destroy() on exception

Posted by "Jeremy Hughes (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ARIES-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremy Hughes updated ARIES-613:
--------------------------------

    Fix Version/s: blueprint uber bundle 0.4
    
> use error() instead of info() log in BeanRecipe's destroy() on exception
> ------------------------------------------------------------------------
>
>                 Key: ARIES-613
>                 URL: https://issues.apache.org/jira/browse/ARIES-613
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: 0.3
>            Reporter: Tang Kin Chuen
>            Assignee: Alasdair Nottingham
>            Priority: Trivial
>             Fix For: blueprint uber bundle 0.4, blueprint.core-0.4
>
>
> Suggesting to change the following line in org.apache.aries.blueprint.container.BeanRecipe's destroy() to LOGGER.error.
> LOGGER.info("Error invoking destroy method", getRealCause(e));
> 2011-03-15 22:21:04,760 INFO  [Thread:Gogo shell] [8/org.apache.aries.blueprint/0.3.0]
> org.apache.aries.blueprint.container.BeanRecipe - Error invoking destroy method
> org.osgi.service.blueprint.container.ServiceUnavailableException: The Blueprint container is being or has been destroyed
> 	at org.apache.aries.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:176)
> 	at org.apache.aries.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:49)
> 	at org.apache.aries.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:201)
> 	at org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:50)
> It is a trivial thing, but helps in troubleshooting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (ARIES-613) use error() instead of info() log in BeanRecipe's destroy() on exception

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ARIES-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated ARIES-613:
----------------------------------

    Fix Version/s: blueprint-core-0.3.2
    
> use error() instead of info() log in BeanRecipe's destroy() on exception
> ------------------------------------------------------------------------
>
>                 Key: ARIES-613
>                 URL: https://issues.apache.org/jira/browse/ARIES-613
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: 0.3
>            Reporter: Tang Kin Chuen
>            Assignee: Alasdair Nottingham
>            Priority: Trivial
>             Fix For: blueprint uber bundle 0.4, blueprint.core-0.4, blueprint-core-0.3.2
>
>
> Suggesting to change the following line in org.apache.aries.blueprint.container.BeanRecipe's destroy() to LOGGER.error.
> LOGGER.info("Error invoking destroy method", getRealCause(e));
> 2011-03-15 22:21:04,760 INFO  [Thread:Gogo shell] [8/org.apache.aries.blueprint/0.3.0]
> org.apache.aries.blueprint.container.BeanRecipe - Error invoking destroy method
> org.osgi.service.blueprint.container.ServiceUnavailableException: The Blueprint container is being or has been destroyed
> 	at org.apache.aries.blueprint.container.ReferenceRecipe.getService(ReferenceRecipe.java:176)
> 	at org.apache.aries.blueprint.container.ReferenceRecipe.access$000(ReferenceRecipe.java:49)
> 	at org.apache.aries.blueprint.container.ReferenceRecipe$ServiceDispatcher.call(ReferenceRecipe.java:201)
> 	at org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:50)
> It is a trivial thing, but helps in troubleshooting.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira