Huge log file

[Arnoud van den Broek]

On our FileMaker 14 Server I have installed the FTPeek plug-in. I am using this plug-in in a server side script to upload pictures to our webserver. At first we got a huge log file in Program Files\FileMaker\FileMaker Server\Log\360Plugin Logs (up to 70GB in 24 hours !!). So I modified the logging.properties file as suggested in http://docs.360works.com/index.php/Plugin_log_files#Logging_Level and added 'com.prosc.level= OFF'. I also restarted the fmse and even the server itself.

But surprisingly the log file still contains lots of INFO messages like:

INFO : C++ Handling a child response CodeToParent::is_empty
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::get_fm_data_as_fm_text
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::get_text_length
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::get_fm_data_as_string
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::create_fm_text
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::write_fm_text_to_fm_data
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::clear_memory
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Child process is expecting result
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::is_empty
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::get_fm_data_as_fm_text
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::get_text_length
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::get_fm_data_as_string
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::create_fm_text
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::write_fm_text_to_fm_data
Jul 10, 2017 03:30:24 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::clear_memory
Jul 10, 2017 03:30:30 PM C++ <Unknown>
INFO : C++ Child process is expecting result
Jul 10, 2017 03:30:30 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::is_empty
Jul 10, 2017 03:30:30 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::get_fm_data_as_fm_text
Jul 10, 2017 03:30:30 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::get_text_length
Jul 10, 2017 03:30:30 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::get_fm_data_as_string
Jul 10, 2017 03:30:30 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::create_fm_text
Jul 10, 2017 03:30:30 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::write_fm_text_to_fm_data
Jul 10, 2017 03:30:30 PM C++ <Unknown>
INFO : C++ Handling a child response CodeToParent::clear_memory

 

So my question is: what is going wrong? Why are the changed properties not effecting the log-file?

 

[ryan360Works]

Hi Arnaud,

That logging property only controls java logging. What you are seeing is the C++ side of things. Please email [email protected] with this issue so we can open an official ticket for you.