Resolution:
Description:
===========
Error "[ERROR][] [FileProcessor.cpp, 103: FileProc essor::getLoadFile: ][file_header_invalid] Ignoring file for load <Exception>" reported.

Environment:
===========
TIBCO ActiveSpaces 2.x
All Operating Systems

Symptoms:
=========
Error in ActiveSpaces log file:

[ERROR][] [FileProcessor.cpp, 103: FileProcessor::getLoadFile: ][file_header_invalid] Ignoring file for load
<Exception> 1) FileReader201.cpp: 102: FileReader201::processFileHeader: file_header_invalid
- file_name=<filename>
SystemService_store_1366188444, load view number is zero
2) FileProcessor.cpp: 162: FileProcessor::processFileHeader
3) FileProcessor.cpp: 144: FileProcessor::isValidLoadFile
</Exception>

Cause:
======
If the seeder has fully joined the space either after recovery or during a normal start up without any files, there should be only one current file present per seeder. However, if you do start up, kill, and the agentagent/node has not fully joined the cluster, there can be multiple files which are created and initialized with a zero view number. When you start up again, seeders with such files will rename the file with .INVALID extension and leave it around. INVALID files could be either due to this repeated start up, kill, or they could also be created when encountering some failure trying to parse old files during recovery.

Resolution:
========
When you run a  Java application as a SEEDER and are trying to create space with the share nothing persistence option, you have to recover the space command.

Example:
======================================================================================================
      if(!titleSpace.getSpaceState().equals("READY"))
        {
           System.out.println("space recovering==============================="+titleSpace.getSpaceState());
            itelMetaspace.recoverSpace(titleSpace.getName(), RecoveryOptions.create().setLoadWithData(true));
        System.out.println("space recovering complated ==============================="+titleSpace.getSpaceState());
        }

=======================================================================================================

Now you cannot see the error. Even if the error is seen you can ignore the error. We currently do not delete the files with extension .INVALID files to be able to perform some offline checks using as-dump/as-convert to get as much data out of invalid files as possible.This was the original reason for not cleaning up those files. However, we could provide a mechanism in the future to delete INVALID files as well upon start up.

NOTE: You can ignore the error while recovery.

Error "[ERROR][] [FileProcessor.cpp, 103: FileProc essor::getLoadFile: ][file_header_invalid] Ignoring file for load ;Exception;" reported.