mod_log-any/9199: Logging wrong client IP under stress

[Rainer Jung <ra...@kippdata.de>]

>Number:         9199
>Category:       mod_log-any
>Synopsis:       Logging wrong client IP under stress
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Dec 19 11:00:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     rainer.jung@kippdata.de
>Release:        1.3.14
>Organization:
apache
>Environment:
Solaris 2.6
>Description:
We use apache under heavy load with mod_ssl on a Solaris 4 CPU machine.
Very rarely we see wrong logfile access lines: 
the client IP address is one, which belongs to another user which is active 
at the same time. We can identify users, 
because we also log a User ID (POST parameter).
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]