Dasbhoard workspace JobHistoryStatisticsGathering.fmw Errors after upgrade to FME Server 2022.2.7

Question

I recently upgraded from FME Server 2022.1.3 to 2022.2.7. Since the upgrade, the JobHistoryStatisticsGathering.fmw workspace (which runs on a daily schedule as part of the built-in FME Server Dashboards) is failing. The error message is:

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Feature Type: `JobHistoryReader_LoopHere'
Attribute(32 bit integer)      : `Loop to JobHistoryReader_LoopHere1691186519 Input Splitter.BranchingFactory.Count' has value `1'
Attribute(string: UTF-8)       : `_min_job_age' has value `20230803000000'
Attribute(64 bit integer)      : `_offset' has value `0'
Attribute(string: windows-1252): `fme_feature_type' has value `Creator'
Attribute(string: windows-1252): `fme_geometry' has value `fme_undefined'
Attribute(string: windows-1252): `fme_type' has value `fme_no_geom'
Coordinate System: `'
Geometry Type: IFMENull
Coordinate Dimension: 2
===========================================================================
Loop to JobHistoryReader_LoopHere1691186519 Input Splitter (BranchingFactory): Transformer/Factory JobHistoryReader_HTTPCaller is blocking and cannot be used in a loop, but was found between 'Loop to JobHistoryReader_LoopHere1691186519 Input Splitter' and 'JobHistoryReader_LoopHere1691186519 Input Splitter'
An error has occurred. Check the logfile above for details

This workspace came from a previous version of FME Server and was restored following the recent upgrade. I retrieved a "clean" version of this workspace from a brand-new FME Server 2022.2.7 installation, but it manifests the same issue.

The workspace had been running fine in previous versions of FME Server. Why is this now a problem?

Page 1 / 1

Reviewing the logs on the server, it looks like this workspace runs fine most of the time. It has failed a couple times though since the upgrade, and fails every time with the same message when run from FME Desktop on another machine.

If it runs fine most of the time I wonder if the issue is only when it tried to loop? It looks like the Looping is done to request more jobs from the job table?

The HTTPCaller has gotten an upgrade so that it will now request in parallel (I think by default 25 requests). This shouldn't be happening though unless the transformer was upgraded in the workspace itself, which I guess is possible.

You will need to make sure to change the max number of requests from 25 back to 1.

Reply

virtualcitymatt · Accepted Answer

Reviewing the logs on the server, it looks like this workspace runs fine most of the time. It has failed a couple times though since the upgrade, and fails every time with the same message when run from FME Desktop on another machine.

If it runs fine most of the time I wonder if the issue is only when it tried to loop? It looks like the Looping is done to request more jobs from the job table?

The HTTPCaller has gotten an upgrade so that it will now request in parallel (I think by default 25 requests). This shouldn't be happening though unless the transformer was upgraded in the workspace itself, which I guess is possible.

You will need to make sure to change the max number of requests from 25 back to 1.

cfvonner · Answer

Reviewing the logs on the server, it looks like this workspace runs fine most of the time.  It has failed a couple times though since the upgrade, and fails every time with the same message when run from FME Desktop on another machine.

Reply

Community Stats

Sign up

An FME Account is required to contribute

Login to the community

An FME Account is required to contribute

Scanning file for viruses.

This file cannot be downloaded