axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sahan Gamage (JIRA)" <j...@apache.org>
Subject [jira] Closed: (AXIS2C-57) log entries should have a timestamp
Date Tue, 14 Feb 2006 08:18:09 GMT
     [ http://issues.apache.org/jira/browse/AXIS2C-57?page=all ]
     
Sahan Gamage closed AXIS2C-57:
------------------------------

    Fix Version: Current (Nightly)
                     (was: M0.4)
     Resolution: Fixed

Implemented. We have the time stamp in the log as follows.
[Tue Feb 14 14:16:42 2006] [info]  Read Timeout : 60000 ms



> log entries should have a timestamp
> -----------------------------------
>
>          Key: AXIS2C-57
>          URL: http://issues.apache.org/jira/browse/AXIS2C-57
>      Project: Axis2-C
>         Type: Improvement
>   Components: util
>     Versions: Current (Nightly)
>     Reporter: Samisa Abeysinghe
>      Fix For: Current (Nightly)

>
> We should have some timing information against all the log enties to grasp what happened
when.
> e.g. the httpd log reads as follows:
> [Sat Feb 04 08:21:17 2006] [notice] LDAP: SSL support unavailable
> [Sat Feb 04 08:21:17 2006] [notice] mod_python: Creating 4 session mutexes based on 256
max processes and 0 max hreads.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message