sora4222 / databasedirectoryrecord Goto Github PK

The release/v1.1.0 will attempt to read from a file it doesn't own or create a watcher on a folder it can't read or execute and the java will report the issue and crash.

Using a RDS database has revealed that the needed database table is not capable of being created.
The error given is:

[42000][1071] Specified key was too long; max key length is 3072 bytes

This needs to be fixed so the maximum size path length and computer hostname can be stored.

The current methodology of setup creates a great amount of fileInformation objects, fills memory, and takes a very long time for anything to have come through.

Accessing the database continually will affect data usage for the attached network, and be slow and encumbersome for data delivery and receiving.

An exception is occurring when running createExe. This had worked the night before. Unsure why it is happening.

Security framework of XStream not initialized, XStream is probably vulnerable.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':createExe'.
> net.sf.launch4j.BuilderException: net.sf.launch4j.ExecException: Exec failed (1): C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\tmp\launch4j\bin-launch4j-3.12\bin\ld.exe -mi386pe --oformat pei-i386 --dynamicbase --nxcompat --no-seh --subsystem windows -s C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\tmp\launch4j\bin-launch4j-3.12\w32api\crt2.o C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\tmp\launch4j\bin-launch4j-3.12\head\guihead.o C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\tmp\launch4j\bin-launch4j-3.12\head\head.o C:\Users\sora4\AppData\Local\Temp\launch4j5761446975487944505o C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\tmp\launch4j\bin-launch4j-3.12\w32api\libmingw32.a C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\tmp\launch4j\bin-launch4j-3.12\w32api\libgcc.a C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\tmp\launch4j\bin-launch4j-3.12\w32api\libmsvcrt.a C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\tmp\launch4j\bin-launch4j-3.12\w32api\libkernel32.a C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\tmp\launch4j\bin-launch4j-3.12\w32api\libuser32.a C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\tmp\launch4j\bin-launch4j-3.12\w32api\libadvapi32.a C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\tmp\launch4j\bin-launch4j-3.12\w32api\libshell32.a -o C:\Users\sora4\OneDrive\Desktop\DatabaseDirectoryRecord\build\launch4j\DatabaseDirectoryRecord.exe

A file that is deleted will still remain in the database, and the original location information file that is moved will also remain in the database. These need to be deleted, either through the hash or by using a scan.

As a system administrator I don't want the system responding to every log file change. I want to be able to ignore directories or files as specified.

The current software will go through the setup scan each time unless it has been passed the setting not to do so. This is a struggle in that an initial setup scan can take a long time.
This could be stored during scan which would help.

A potential solution:

1. Create a table in the database for storing this information
2. Use this in conjunction with the computer database saving all folders visited

• When doing this use a thread, and a queue, this will decouple from the setup

3. At startup read from this database skipping folders that have been read from last startup.

When the Files.walk reaches an AccessDenied exception the entire stream stops. This doesn't allow for the file to be filtered out.

A solution can be seen:
https://stackoverflow.com/questions/44007055/avoid-java-8-files-walk-termination-cause-of-java-nio-file-accessdeniedexc?noredirect=1&lq=1
This is the major solution at this stage.