How to diagnose a sporadic failure during export during publish?

Hi,

We are using Knowledge Center. Sometimes, a publish fails while topics are being exported in blocks of 50. It times out. I've been trying to diagnose the problem, but haven't been able to reproduce a failure. It's considered a critical issue though, because of the havoc it causes.

Do you have any suggestions for how to diagnose the problem? It might be a WCF and network bandwidth problem, I'm guessing.

Kendall

Parents
  • Hi Kendall,

    I assume a version before 13SP1/13.0.1, as that is the version where "PublishService" (which exports in blocks of 50) was rewritten to "Publish" (which exports one-by-one using streaming technology). And quite a lot faster if I may say so.

    You should consider the 50 as persons in an elevator, which most of the time is fine. But sometimes 50 persons of above average weight are breaking the elevator. That part of the elevator sign is not in place for "PublishService" and yes 50 big images or PDFs or... can break the export.

    So when logging an issue, besides the exact software version, please add information about

    1. Your information architecture, in this case, are you really exporting videos, images, big maps,...
    2. Windows Event Viewer might contain good information
    3. Log files
    4. "Event Monitor" as shown in the web client

    If you really have a reproducible case, "PublishService" is exported hosted by a "dllhost.exe" (so COM+ server application). You could monitor that with Windows Performance monitor (really guessing here that entry 'private bytes' if hitting its max so around 1.4GB of the available 2GB)

    Best wishes,
    Dave

    PS: The root cause is still unknown based on the above, but if it is about 50 per block, then https://docs.sdl.com/LiveContent/content/en-US/SDL%20Knowledge%20Center%20full%20documentation-v2.1.5/GUID-307FED94-DA75-4C04-B9CD-051EAC83A8AB could help. These are engineering debug values to workaround issues like this. Unfortunately they are not available in all versions of the software, and that is where the exact software version comes in.

Reply
  • Hi Kendall,

    I assume a version before 13SP1/13.0.1, as that is the version where "PublishService" (which exports in blocks of 50) was rewritten to "Publish" (which exports one-by-one using streaming technology). And quite a lot faster if I may say so.

    You should consider the 50 as persons in an elevator, which most of the time is fine. But sometimes 50 persons of above average weight are breaking the elevator. That part of the elevator sign is not in place for "PublishService" and yes 50 big images or PDFs or... can break the export.

    So when logging an issue, besides the exact software version, please add information about

    1. Your information architecture, in this case, are you really exporting videos, images, big maps,...
    2. Windows Event Viewer might contain good information
    3. Log files
    4. "Event Monitor" as shown in the web client

    If you really have a reproducible case, "PublishService" is exported hosted by a "dllhost.exe" (so COM+ server application). You could monitor that with Windows Performance monitor (really guessing here that entry 'private bytes' if hitting its max so around 1.4GB of the available 2GB)

    Best wishes,
    Dave

    PS: The root cause is still unknown based on the above, but if it is about 50 per block, then https://docs.sdl.com/LiveContent/content/en-US/SDL%20Knowledge%20Center%20full%20documentation-v2.1.5/GUID-307FED94-DA75-4C04-B9CD-051EAC83A8AB could help. These are engineering debug values to workaround issues like this. Unfortunately they are not available in all versions of the software, and that is where the exact software version comes in.

Children