• State Verified Answer
  • +2 person also asked this people also asked this
  • Replies 12 replies
  • Answers 2 answers
  • Subscribers 26 subscribers
  • Views 5350 views
  • Users 0 members are here

Bulk Import aborts due to inactivity

Catherine Marklove
Offline

Hello,

When using the bulk import utility imports are failing midway through due to 180 seconds of inactivity. This only seems to happen when users are trying to upload more than 30 documents, and the first 30 are still uploaded even though the process never completes. Is there any reason you know of that may cause the import to become inactive mid way through the process?

Kind regards,

Catherine

Parents
  • 0 Offline

    Hello Catherine,
    It's Document Bulk import tool, right?
    Does the job gets stuck in Work queue with error pointing to inactivity? Is it only data that are being uploaded or also files? Maybe you could provide me personally that import sheet and configuration .ini file for further investigation ?

    Regards
    Gintautas



  • 0 Offline in reply to Gintautas
    Hi Gintautas,

    Yes the bulk import tool, and the error is:

    -The job was aborted due to 180 seconds of successive inactivity. Exception Stack Trace: { --- Begin of exception stack trace --- System.Exception: The job was aborted due to 180 seconds of successive inactivity. at eB.Management.QueueJobHelper.InvokeCustomEngine(QueueEngineProcess qep, String engineDll, String engineNamespace, String proxyConnectInfo, IDictionary`2 jobAttributes) at eB.Management.QueueJobHelper.ProcessQueueEntry(Object sender, PollEventArgs e) --- End of exception stack trace --- }

    It seems to happen regardless of which .ini file is used and what is being uploaded (documents or documents and files). It did work in the past and nothing changed that we know of, and it does work if you only try a small number of documents. It's only when you try and increase the number past around 30. In past we could upload over 100 with no issue.

    Thanks,

    Catherine
  • 0 Offline in reply to TBadock
    Hello everyone,
    Please send me a copy of spreadsheet and config file you are using and let me know version of eB . We have few users who is running bulk import jobs which takes couple hours to process and these jobs completes with no issue. Maybe this issue specific to content or data that you are loading. This requires more detailed investigation involving your data.

    Best regards
    Gintautas



  • 0 Offline in reply to TBadock

    Any luck with the data I sent?
    Bulk loads are still regularly falling over with the same error Catherine reported:

    The job was aborted due to 540 seconds of successive inactivity.


    Exception Stack Trace:
    {
    --- Begin of exception stack trace ---
    System.Exception: The job was aborted due to 540 seconds of successive inactivity.
    at eB.Management.QueueJobHelper.InvokeCustomEngine(QueueEngineProcess qep, String engineDll, String engineNamespace, String proxyConnectInfo, IDictionary`2 jobAttributes)
    at eB.Management.QueueJobHelper.ProcessQueueEntry(Object sender, PollEventArgs e)
    --- End of exception stack trace ---
    }

  • 0 Offline in reply to TBadock

    I've noticed similar issues with eB sending out email notifications, any potential link?

    Failure sending mail.

    Unable to connect to the remote server

    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xx.xx.xxx.xx:xx

    AND ALSO


    Service not available, closing transmission channel. The server response was: 4.3.2 Service not available

  • +1 Offline in reply to TBadock

    Hello,

    Can you trying decreasing the threshold on the work queue to 5 or below and then restarting the work queue service.

    It should allow you to load the file.

    Regards,

    Pushpraj

Reply Children
Communities
Support and Services
Training and Learning
Social Media