You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Martin Lichtin (JIRA)" <ji...@apache.org> on 2015/01/30 22:32:36 UTC
[jira] [Commented] (ARIES-1193) INFO log when optional service is
not available
[ https://issues.apache.org/jira/browse/ARIES-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299246#comment-14299246 ]
Martin Lichtin commented on ARIES-1193:
---------------------------------------
Note that this INFO log is produced _every time_ the optional service is referenced.
It just fills up the logs with useless information.
> INFO log when optional service is not available
> -----------------------------------------------
>
> Key: ARIES-1193
> URL: https://issues.apache.org/jira/browse/ARIES-1193
> Project: Aries
> Issue Type: Bug
> Reporter: Martin Lichtin
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
>
> Can the log level be reconsidered?
> if (metadata.getAvailability() == ServiceReferenceMetadata.AVAILABILITY_MANDATORY) {
> LOGGER.info("Timeout expired when waiting for mandatory OSGi service reference {}", getOsgiFilter());
> throw new ServiceUnavailableException("Timeout expired when waiting for mandatory OSGi service reference: " + getOsgiFilter(), getOsgiFilter());
> } else {
> LOGGER.info("No matching service for optional OSGi service reference {}", getOsgiFilter());
> throw new ServiceUnavailableException("No matching service for optional OSGi service reference: " + getOsgiFilter(), getOsgiFilter());
> }
> I don't see the need to repeatedly emit INFO logs for an optional service not being around. Can it be changed to DEBUG level?
> On the other side, for a mandatory service, the INFO log could become a WARN, perhaps.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)