Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: 0.9.2.1
    • Fix Version/s: 2.1
    • Component/s: Development
    • Labels:
      None

      Description

      The UserLoginFilter uses the Mapped Diagnostic Context feature of Log4J to record the logged-in user that performs actions. This data is associated with a thread provided by the container. If the thread is re-used for another purpose, it is possible for the old data to be logged in subsequent, unrelated, activities.

      For example, here I (arh14) am interacting with the web UI, and then later making a service invocation from my desktop:

      2008-07-10 13:01:55,723 [http-localhost%2F127.0.0.1-8080-Processor10] D: U:arh14 INFO edu.iu.uis.eden.web.WorkflowAction :: methodToCall=menu
      2008-07-10 13:01:55,723 [http-localhost%2F127.0.0.1-8080-Processor10] D: U:arh14 INFO edu.iu.uis.eden.web.WorkflowAction :: dispatch to
      methodToCall menu called

      ...3 hours later in Processor10 thread "arh14" user is logged during web service invocation...

      2008-07-10 16:39:36,067 [http-localhost%2F127.0.0.1-8080-Processor10] D: U:arh14 ERROR org.codehaus.xfire.handler.DefaultFaultHandler :: Fault occurred!

        Attachments

          Issue Links

            Activity

            Hide
            ahamid Aaron Hamid (Inactive) added a comment -

            This should be fixed by related 2.1 work, so I'll accept my own fix

            Show
            ahamid Aaron Hamid (Inactive) added a comment - This should be fixed by related 2.1 work, so I'll accept my own fix

              People

              • Assignee:
                Unassigned
                Reporter:
                ahamid Aaron Hamid (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: