Skip to main content
Solved

JMS message - valid json but containing an unescaped right brace, job fails to submit

  • January 21, 2025
  • 1 reply
  • 21 views

ebygomm
Influencer
Forum|alt.badge.img+44

An automation reads a message from a JMS queue and should trigger a workspace, the message content is passed as an automation parameter. This message is valid json, however we’ve had some cases where the message is something along the lines of

{
"ID": "1234",
"Notes": "Careless typing} includes a right hand curly brace"
}

This is valid json but the job fails with a status of FME_FAILURE and a statusMessage of  "extra characters after close-brace".

 

How should the message be passed to the workspace if json like the above example leads to failure to submit? 

Best answer by ebygomm

It looks like an upgrade to 2024 fixes this issue. 

1 reply

ebygomm
Influencer
Forum|alt.badge.img+44
  • Author
  • Influencer
  • 3434 replies
  • Best Answer
  • January 24, 2025

It looks like an upgrade to 2024 fixes this issue.