Solved

What is STATRP in log file? Why does it suddenly appear part way through?


Badge +7

FME Desktop 2018.1.01. on Windows Server 2012.

I started a translation at 1523 yesterday which simply reads point data from SQL Server Spatial and writes it to an ArcSDE layer. At 1821 STATRP lines started appearing in the log. And at the end I got 2 lines saying "Translation was SUCCESSFUL with 1 warning(s)..." instead of the usual 1 line.

Statistics are ticked in the translation options but I've never noticed this situation before. What is STATRP, and how is it different from STATS?

2019-06-17 18:21:30|9989.8| 2.5|INFORM|Transaction #3779 was successfully committed

 

2019-06-17 18:21:34|9993.1| 3.3|INFORM|Reading source feature # 3780000

 

2019-06-17 18:21:34|9993.1| 0.0|INFORM|Transaction #3780 was successfully committed

 

2019-06-17 18:21:36|9995.6| 2.5|INFORM|Transaction #3781 was successfully committed

 

2019-06-17 18:21:39|9998.1| 2.5|INFORM|Transaction #3782 was successfully committed

 

2019-06-17 18:21:40|9999.4| 1.3|INFORM|Reading source feature # 3782500

 

2019-06-17 18:21:42|10000.6| 1.2|STATRP|Reading source feature # 3783000

 

2019-06-17 18:21:42|10000.6| 1.2|INFORM|Transaction #3783 was successfully committed

 

2019-06-17 18:21:43|10001.9| 1.3|STATRP|Reading source feature # 3783500

 

2019-06-17 18:21:44|10003.2| 2.5|STATRP|Reading source feature # 3784000

 

2019-06-17 18:21:44|10003.2| 2.5|INFORM|Transaction #3784 was successfully committed

 

2019-06-17 18:21:45|10004.4| 1.3|STATRP|Reading source feature # 3784500

 

2019-06-17 18:21:47|10005.7| 2.5|STATRP|Reading source feature # 3785000

 

2019-06-17 18:21:47|10005.7| 2.5|INFORM|Reading source feature # 3785000

 

2019-06-17 18:21:47|10005.7| 0.0|INFORM|Transaction #3785 was successfully committed

 

2019-06-17 18:21:48|10007.0| 1.3|STATRP|Reading source feature # 3785500

 

2019-06-17 18:21:49|10008.2| 2.5|STATRP|Reading source feature # 3786000

 

2019-06-17 18:21:49|10008.2| 2.5|INFORM|Transaction #3786 was successfully committed

...

2019-06-17 19:07:01|12583.8| 0.0|STATS |==============================================================================

 

2019-06-17 19:07:01|12583.8| 0.0|STATS |Total Features Written 4795418

 

2019-06-17 19:07:01|12583.8| 0.0|STATS |=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

 

2019-06-17 19:07:01|12583.8| 0.0|INFORM|Translation was SUCCESSFUL with 1 warning(s) (4795418 feature(s) output)

 

2019-06-17 19:07:01|12583.8| 0.0|STATRP|Translation was SUCCESSFUL with 1 warning(s) (4795418 feature(s) output)
icon

Best answer by jovitaatsafe 19 March 2020, 20:42

View original

2 replies

Badge +7

Just noticed this again after seeing duplicate lines in my logfile (FME 2018), and found my own unanswered question! Surely this is an easy one to answer...?!

2020-03-12 18:52:32|14192.7| 0.0|INFORM|Translation was SUCCESSFUL with 1 warning(s) (4827955 feature(s) output)

2020-03-12 18:52:32|14192.7| 0.0|STATRP|Translation was SUCCESSFUL with 1 warning(s) (4827955 feature(s) output)

Userlevel 1
Badge +11

Hi @tim_wood,

Sorry to see that we missed your question from last year!

Our friends from the development team explain that it may be a mistake in logging this to the logfile. 

STATRP
 is a unique message severity, similar to 
INFORM
WARN
, or 
ERROR
 that means 
status report.
 It's intended to be shown in the status bar in Workbench and not meant to be logged.

Does this message appear for you with newer versions of FME? Our team suspects that it may be bug that we've since fixed but we won't be adding that fix to FME 2018 unfortunately.

Reply