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

• Type: Bug
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 0.3
• Fix Version/s: blueprint uber bundle 0.4, blueprint.core-0.4, blueprint-core-0.3.2
• Component/s: Blueprint
• Assignee: Alasdair Nottingham
• Reporter: Tang Kin Chuen
• Created: 16/Mar/11 00:18
• Updated: 22/May/12 14:17
• Resolved: 13/May/11 19:09

Description

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.