Skip to main content
Question

FMEFlowJobSubmitter 'Failure when receiving data from the peer'

  • September 19, 2024
  • 2 replies
  • 67 views

taylordowns
Contributor
Forum|alt.badge.img+4

Hello everyone,

 

I am reaching out because I have run into a problem recently and searched through previous thread and couldn’t quite find my issue with a solution.

I am running into a hang up when I run a workspace that triggers an additional workspace through FMEFlow using FMEFlowJobSubmitter. I will paste an example of what the log looks like.

 

FMEFlowJobSubmitter: https://your.specific. - Submitting a request to run workspace 'Your-Workspace' in repository 'YourRepository'…

FMEFlowJobSubmitter: https://your.specific - Failed to submit request to run workspace ''Your-Workspace'' in repository 'YourRepository'
FMEFlowJobSubmitter - 'Failure when receiving data from the peer'

 

My workflow is submitting around 70 jobs so after this error occurs around 15 times the error switches to:

Error: Failed to update access token.

FME Flow error: `FME Flow error: `929026:Error: Connection reset''

FMEFlowJobSubmitter: https://your.specific - Failed to submit request to run workspace ''Your-Workspace'' in repository 'YourRepository'

FMEFlowJobSubmitter: Reason - 'Failed to login'

After this cycles through and I receive this error numerous times the job submitter starts working right and the remaining jobs are sent through and executed.

 

 

 

The team I am apart of just upgraded this specific server from 2023.1 to 2024.1. NOTE: There are two engines that are configured to load balance on this specific server.

 

I am also going to submit a trouble ticket for this case, so I will keep this thread updated with what the root cause and fix was.

2 replies

lazarlubomir
Contributor
Forum|alt.badge.img+7
  • Contributor
  • February 10, 2025

Hi ​@taylordowns and everyone,

 

do you have any solution for that issue? I have got the same trouble… :-(


taylordowns
Contributor
Forum|alt.badge.img+4
  • Author
  • Contributor
  • February 10, 2025

Sadly there was no fix that my team or support was able to find. What I did was moved the workspaces that run the jobsubmitter into the automations and have them connected that way, instead of with the jobsubmitter. I tried multiple different solutions but none worked, from adding a http caller to trying to embed the connection, I even ended up working with my company’s server team to ensure that there were no ports being blocked. I know this is probably not the answer you were looking to hear but don’t be like me and spend months looking for the answer just to come up blank. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings