[JIRA] Commented: (JOST-160) not all times in logging normalized to Zulu

[Chad La Joie (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/JOST-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617#comment-13617 ] 

Chad La Joie commented on JOST-160:
-----------------------------------

@Peter: Well, technically, the log message timestamp is in whatever time you tell them to be in.  But yeah, the default is ISO8601 timestamps in local time.

Well, I didn't feel like trying to figure out which format I really liked best for this so now it just prints out both times.

> 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