Test Data Manager

 View Only
  • 1.  Error while executing Javelin workflow as a Post-Action in TDM generator

    Posted Apr 22, 2021 08:05 AM
    Hi Team, 

    I've a Javelin workflow, in which I'm calling APIs, so when I'm executing(start) it as a standalone workflow it is working fine and giving expected output.
    But, as I attached it as Post-Action workflow to a generator, and published it, then it is throwing an error: 
    2021-04-22 01:02:15 - Error executing RESTPutActivity: Error reading JToken from JsonReader. Path '', line 0, position 0.


    This is what API configuration looks like:

    Post- Action:


    Can you please advise on this? What could be the possible reason for this error?

    Thanks


  • 2.  RE: Error while executing Javelin workflow as a Post-Action in TDM generator

    Broadcom Employee
    Posted Apr 23, 2021 02:48 PM
    Karan,

    Are you able to try executing the Javelin post-publish action as a HOST command calling a .bat (see Javelin batch mode) to see if it exhibits the same behavior?
    Can you also double-check that the applications.properties file workflow.path.executor line points to the same Javelin you are using?

    Scott



  • 3.  RE: Error while executing Javelin workflow as a Post-Action in TDM generator

    Posted Apr 28, 2021 08:04 AM
    Edited by Karan Aggarwal Apr 28, 2021 08:05 AM


  • 4.  RE: Error while executing Javelin workflow as a Post-Action in TDM generator

    Posted Apr 29, 2021 03:30 AM
    Hi Scott,
    We tried executing Javelin post-publish as a HOST command calling a .bat file and got the below error:
    ERROR: Publish failed for job 112613, Publish action failed, action name: Host Action, action type Post-Publish, action code type HOST, resolve_meta_data_item: TDMServiceException: unknown variable: 1


    Also, when we are running this .bat file from cmd, it is working fine and giving expected output.


  • 5.  RE: Error while executing Javelin workflow as a Post-Action in TDM generator

    Posted May 03, 2021 02:31 AM
    Hi Scott,

    We are troubleshooting firewall issues for this, as we believe there is a possibility for firewall restrictions.
    So, will update you once that issue get resolved and still this issue persists.


    Thanks for support.