Bug #13174

Jobs can hang if output is greater than 64K

Added by Mike Cantelon about 1 month ago. Updated 27 days ago.

Status:VerifiedStart date:09/12/2019
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Job scheduling
Target version:Release 2.6.0
Google Code Legacy ID: Tested version:
Sponsored:Yes Requires documentation:No

Description

David J.'s recommendation for stable/2.5.x is to truncate all jobs output to 64KB (-1 byte), before inserting it into the DB, to mimic the MySQL <5.7 behaviour.


Related issues

Related to Access to Memory (AtoM) - Bug #13095: 500 error when link PDF digital object with much text con... Feedback 06/20/2019

History

#1 Updated by Mike Cantelon about 1 month ago

  • Status changed from In progress to Code Review
  • Assignee deleted (Mike Cantelon)

#2 Updated by Mike Cantelon about 1 month ago

  • Sponsored changed from No to Yes

#3 Updated by José Raddaoui Marín about 1 month ago

  • Related to Bug #13095: 500 error when link PDF digital object with much text content added

#4 Updated by José Raddaoui Marín about 1 month ago

  • Status changed from Code Review to Feedback
  • Assignee set to Mike Cantelon

#5 Updated by Mike Cantelon about 1 month ago

  • Status changed from Feedback to QA/Review
  • Assignee deleted (Mike Cantelon)

Merged into qa/2.6.x.

#6 Updated by Dan Gillean 27 days ago

  • Status changed from QA/Review to Verified
  • Target version set to Release 2.6.0
  • Requires documentation set to No

Seems to work. I ran several normal jobs successfully, and then imported a huge XML file. The console log on the job details cuts page off abruptly but the import succeeded. Marking verified.

Also available in: Atom PDF