Mendix 7.4 and FileDocumentSizesPopulateJob

5
We're going to upgrade from 7.1 to 7.4 and during testing I encountered these messages (during startup) Log node: FileDocumentSizesPopulateJob File not found for 8e618585-720b-4c76-8cee-506c6e48d0e0: LocalFileSystemStore:: File does not exist for key: 8e618585-720b-4c76-8cee-506c6e48d0e0. Setting size to 0. This is repeating over and over again (for the about 300 files I should actually have). I see that I have probably mixed up the test database and deployment/files (losing the file corresponding to the database entries). But now I cannot start the Application on that database anymore. Has anyone encountered this and knows a way to bypass this "FileDocumentSizesPopulateJob   Date/time Log node Message 2017-07-10 08:54:01.792 Core Mendix Runtime 7.4.0 (build 22537). Copyright © 2003-2017 Mendix bv. All rights reserved. 2017-07-10 08:54:03.383 Core Storage service: Local file system storage, uploaded files path: C:\...\deployment\data\files 2017-07-10 08:54:03.408 ConnectionBus Database: PostgreSQL 9.6.2, name: 'DataCross' (...) 2017-07-10 08:54:03.552 Core The runtime has been started using a trial license, the framework will be terminated when the maximum time is exceeded! 2017-07-10 08:54:04.659 Core Running after-startup-action... 2017-07-10 08:54:04.786 APMAgent.Shared Error getting jar 2017-07-10 08:54:04.786 APMAgent.Shared JarIdentifier 1. : (...) 2017-07-10 08:54:04.787 APMAgent.Shared Instance ID 0 2017-07-10 08:54:04.787 APMAgent.Shared Project ID 05A725ED9D32384C99FD0A02D0C580FD 2017-07-10 08:54:04.792 APMAgent.TrapTool Starting with recording a maximum of 3 queues, creating a new queue after 1000 (ms) or after recording 10000 records. . Max messages to buffer is 100000. When max buffer is reached the trap tool pauses until the buffer is empty plus a pause of 300s. Max messages to store is 100000. When max messages are reached the oldest trap messages are deleted.. Max lag (processing delay) is 4000 (ms). 2017-07-10 08:54:04.795 APMAgent.TrapTool Registering log subscriber 2017-07-10 08:54:04.797 APMAgent.TrapTool Started Traptool 2017-07-10 08:54:04.797 APMAgent.TrapTool Start private store thread 2017-07-10 08:54:04.820 APMAgent.StatisticsTool Starting statistics trace. Max lag (processing delay) is 4500 (ms). 2017-07-10 08:54:04.820 APMAgent.StatisticsTool Registering statistics subscriber 2017-07-10 08:54:04.820 APMAgent.StatisticsTool Started statistics trace. 2017-07-10 08:54:04.825 APMAgent.Shared Started dynamic scheduled event Statistics Tool Daily 2017-07-10 08:54:04.829 APMAgent.Shared Started dynamic scheduled event Statistics Tool Console 2017-07-10 08:54:04.835 APMAgent.JavaConsole Re-routing java console 2017-07-10 08:54:04.835 APMAgent.JavaConsole Re-routing java console done 2017-07-10 08:54:04.841 APMAgent.JMX JMX starting 2017-07-10 08:54:04.849 APMAgent.JMX JMX started 2017-07-10 08:54:04.849 APMAgent.Shared APMAgent startup complete. 2017-07-10 08:54:04.867 Core Successfully ran after-startup-action. 2017-07-10 08:54:04.870 ActionManager Scheduling CommunityCommons.releaseOldLocks every 5 minutes, starting from 2011-01-27 09:58:53 (UTC) 2017-07-10 08:54:04.884 ActionManager Scheduling Exchange.CheckRequestEscalationTimes every 1 minute, starting from 2017-01-12 14:25:33 (UTC) 2017-07-10 08:54:04.887 ActionManager Scheduling Exchange.Scheduled_SystemRequest_ProductDeclaration_Complete every 15 minutes, starting from 2017-06-20 10:40:29 (UTC) 2017-07-10 08:54:04.887 ActionManager Scheduling Administration.Check_AccountsOrPassword_Expired every 1 second, starting from 2016-10-06 12:15:00 (UTC) 2017-07-10 08:54:04.998 ActionManager Scheduling EmailTemplate.SendQueuedEmails every 1 minute, starting from 2015-04-10 00:00:00 (UTC) 2017-07-10 08:54:05.005 ActionManager Scheduling APMAgent.APMCleanup_SE every 1 day, starting from 2016-05-24 00:00:00 (UTC) 2017-07-10 08:54:05.006 ActionManager Scheduling Exchange.SCE_SharedAnswerCatalogue_Process every 1 minute, starting from 2017-07-03 12:12:14 (UTC) 2017-07-10 08:54:05.007 ActionManager Scheduling Licensing.LicenseFile_LicenseExpration every 1 hour, starting from 2017-04-05 14:21:41 (UTC) 2017-07-10 08:54:05.007 ActionManager Scheduling EmailTemplate.Cleanup every 1 week, starting from 2015-04-10 01:00:00 (UTC) 2017-07-10 08:54:05.007 ActionManager Scheduling Regulations.RunComplianceCheck every 10 seconds, starting from 2017-05-04 13:23:46 (UTC) 2017-07-10 08:54:05.011 ActionManager Scheduling Exchange.Scheduled_SystemRequest_ProductDeclaration every 15 minutes, starting from 2017-06-20 10:40:29 (UTC) 2017-07-10 08:54:05.066 Core Mendix Runtime successfully started, the application is now available. 2017-07-10 08:54:09.873 FileDocumentSizesPopulateJob Start populating size of 87 file documents ... 2017-07-10 08:54:09.947 FileDocumentSizesPopulateJob File not found for d177e948-bae8-4f9b-99cb-4b058a4afaf2: LocalFileSystemStore:: File does not exist for key: d177e948-bae8-4f9b-99cb-4b058a4afaf2. Setting size to 0. ... repeating over and over again....  
asked
2 answers
1

I'm also getting this, any resolution? I have hundreds of thousands of files on a prod server and it's gonna kill me. The Prod server is currently Mendix 7.12 in a VM Bubble so it's not true prod, but is the actual duplicate prod evnironment

answered
0

I asked customer support but there is no way to stop this scheduled job. But I am analysing queries for performance improvement and this job is cluttering my SQLServer profiler logging (and driving me crazy).

II ‘solved’ it by executing following sql statement:

UPDATE system$filedocument

set Size = 0

where Size = -1

Just for my local database ;o)   I am using Mendix Modelere 7.23.8. by the way.

answered