[JIRA] Commented: (JOST-160) not all times in logging normalized to Zulu
Chad La Joie (JIRA)
noreply at shibboleth.net
Wed Sep 28 15:30:25 BST 2011
[ https://issues.shibboleth.net/jira/browse/JOST-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597#comment-13597 ]
Chad La Joie commented on JOST-160:
-----------------------------------
I don't think it's possible to make it configurable (at least in the logging library itself), but go ahead and file it for v3 and we'll see if there isn't something we can do above the logging lib.
> not all times in logging normalized to Zulu
> -------------------------------------------
>
> Key: JOST-160
> URL: https://issues.shibboleth.net/jira/browse/JOST-160
> Project: OpenSAML 2 - Java
> Issue Type: Improvement
> Components: SAML 2
> Affects Versions: 2.5.0
> Reporter: skoranda at uwm.edu
> Assignee: Chad La Joie
> Priority: Minor
> Fix For: 2.5.2
>
>
> Not all times in the logging have been normalized to Zulu. As an example one can get a log message like this:
> 15:31:48.097 - INFO
> [org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider:405]
> - New metadata loaded from
> '/opt/shibboleth-idp-2.3.0/metadata/ligo-metadata.xml', next
> refresh will occur at approximately
> 2011-07-15T15:43:03.040-05:00
> followed by one like this:
> 15:43:03.042 - INFO
> [org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider:237]
> - Metadata from
> '/opt/shibboleth-idp-2.3.0/metadata/ligo-metadata.xml'
> unchanged since last refresh, next refresh will occur at
> approximately 2011-07-15T20:54:18.040Z
> Note the mixing of local and UTC times.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list