NextGen (Mirth) Connect 3.11.0 Released!

NextGen (Mirth) Connect 3.11.0 is now available as an appliance update and on our GitHub page. This release contains improvements to licensing and the NCPDP data type. It also includes various security fixes, general bug fixes, and improvements to commercial extensions. See the release notes for the complete list of fixes and improvements.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Regenerated Template doesn't appear to be working

  • Filter
  • Time
  • Show
Clear All
new posts

  • Regenerated Template doesn't appear to be working

    Connect v 3.9.1
    We have a HTTP sender destination connector that has a message transform that sets a variable. Lets call it UTC time. This is used in a wsse SOAP security timestamp for created moment. The remote receiving server only allows the prior 5 minute window of created messages to be accepted. Otherwise we get a SOAP fault.

    We set Queue on Failure, Regenerate Template, Including Transformers with multiple retry attempts with a 60 second socket timeout and 30 second wait before retrying.

    We have
    Variable defined and set to connectorMap in a Transformer JavaScript step
    Variable is used in the Velocity template SOAP message
    Regenerate Template is turned on so variables can be updated on resubmission
    Include Filter/Transformers is also set as the var is calculated in Transformer

    Lots of setup to explain what is wrong

    It does not work. The timestamp variable is always the very first calculated value even tough we may have retried so many times more than 5 minutes have passed since we first started. And the remote server sends us back a soap fault for timestamp outside the bounds of the server and it references the value of the SOAP security timestamp from more than 5 minutess ago.

    I have found this forum post --> And it describes the behavior of the options as I already understood them.

    Does it have to go to Queue first before regeneration occurs?
    These errors happen daily during a maintenance scan on the remote server at like 2 or 3 in the morning. If the variable would just update we would save a dozen or more errors a day.