You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/06/20 18:30:48 UTC

DO NOT REPLY [Bug 20961] New: - Design-Error: concurrency in org.apache.axis.handles.LogHandler

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20961>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20961

Design-Error: concurrency in org.apache.axis.handles.LogHandler

           Summary: Design-Error: concurrency in
                    org.apache.axis.handles.LogHandler
           Product: Axis
           Version: 1.1RC1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Samples
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: gert.pache@gmx.de


The LogHandler sets when processing in the request-chain its member-field long
to the current time.
When processing the response-chain LogHandler uses this field to calcualate the
processing time. 
But in case that there are more than one client, a client can be "interrupted"
between this two points by another client and thus messing up the start-field of
the former one.
The start-value should be remembered in the message-context