Note: I believe this bug is different from bug #3736 log4j timestamps are not
ISO 8601 compatible.

Here is an example from the head of a log file in which it is obvious that the
date stamps miss the year. As we use these log files for checkointing and
jobmanagement for an application, it would be important to add the year to the
timestamp. If this is not doen our metadata management to manage large amounts
of jobs across 27 GRAM services will be limited to one year use. Worse, when it
come to the year end we will not be able to distingush between this years and
next years data. 

The error occurs when using 
globusrun version 4.4 

------------------------------

Ignoring Unknown attribute in
/soft/prews-gram-4.0.1-r3/share/globus_gram_job_manager/
globus-gram-job-manager.rvf: 'proxy expires the job-manager should exit."
Default: 60'
10/13 13:22:10 JM: Security context imported
10/13 13:22:10 JM: Adding new callback contact
(url=https://tg-login2.uc.teragrid.org:
50001/, mask=1048575)
10/13 13:22:10 JM: Added successfully
10/13 13:22:10 Pre-parsed RSL string: &("executable" = "/bin/sleep"
)("arguments" = "1
0" )("stdout" = "x-gass-cache://" # $("GLOBUS_GRAM_JOB_CONTACT") # "stdout"
"anExtraTa
g" )("stderr" = "x-gass-cache://" # $("GLOBUS_GRAM_JOB_CONTACT") # "stderr"
"anExtraTa
g" )
10/13 13:22:10 
<<<<<Job Request RSL
&("executable" = "/bin/sleep" )("arguments" = "10" )("stdout" =
"x-gass-cache://" # $(
"GLOBUS_GRAM_JOB_CONTACT") # "stdout" "anExtraTag" )("stderr" =
"x-gass-cache://" # $(
"GLOBUS_GRAM_JOB_CONTACT") # "stderr" "anExtraTag" )
>>>>>Job Request RSL
10/13 13:22:10