You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Sahan Gamage (JIRA)" <ji...@apache.org> on 2006/02/14 09:18:09 UTC
[jira] Closed: (AXIS2C-57) log entries should have a timestamp
[ 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