Uploaded image for project: 'Alfresco'
  1. Alfresco
  2. ALF-21114

JLAN DirectoryWatcher problems under load

    Details

    • Type: Bug
    • Status: New (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 5.0
    • Fix Version/s: None
    • Component/s: JLAN
    • Security Level: external (External user)
    • Labels:
      None
    • Environment:
      Win2008R2 server with native file sharing. Clients: JLAN on Mac OS X 10.9.5; Windows 7; Linux (CentOS 6.5).
    • Triage:
      ACE

      Description

      Under load, DirectoryWatcher sometimes delivers notifications with a missing notification type and filename. The directoryChanged callback gets typ of -1 and fname of null.
      Looking at what is coming across the wire, it appears that the remote server sometimes returns NT NOTIFY responses that lack the "NT NOTIFY Parameters" block. This could hypothetically be a Windows bug of some type - but a C++ Windows client using the Windows API running against the same remote Windows fileserver gets the notifications just fine. This may be because the Windows API program seems to negotiate the SMB2 protocol, rather than SMB as used by JLAN.
      Regardless of whose fault it is, JLAN DirectoryWatcher is unreliable because of this problem.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  riordanmr Mark Riordan (Inactive)
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Date of First Response:

                    Structure Helper Panel