ESB API - THMap cached on server?

[Anonymous]

Hi All,

I have an API deployed to our ESB server. This takes in JSON via tRestRequest, uses a THMap component (which is contained inside a joblet) then send sends it into SAP.

This was working, however, there was a requirement to move some of the fields from the one object in the JSON to another.

eg;

{
  "order": {
    "productInfo": {
      "productInfoOne": "value",
      "productInfoTne": "value"
    },
    "customerInfo" : {
      "customerInfoOne": "value",
      "customerInfoTwo": "value"
    }
  }
}

becomes...

{
  "order": {
    "productInfo": {
      "productInfoTne": "value"
    },
    "customerInfo" : {
      "customerInfoOne": "value",
      "customerInfoTwo": "value",
      "productInfoOne": "value"
    }
  }
}

I made these changes and then tested it locally. It worked fine, however, upon deploying it to the ESB server. It does not work with the new changes, when I use the OLD postman with the NEW job, it works.. 

I'm guessing the THMap config is cached somewhere but I'm unable to find anything.

I've tried undeploying the job, deleting it from the TAC, removing it from the Nexus and then publishing it again and redeploying it, without any success.

Does anyone have any suggestions?

Thanks

[Anonymous]

This should not be happening. Have you looked at the Runtime command line interface? Take a look here and try it out

https://community.talend.com/t5/Design-and-Development/Talend-ESB-Route/m-p/45731/highlight/true#M14...

Sometimes the TAC can "orphan" routes and services if they are not stopped and undeployed before adding a new version.

[Anonymous]

Hi Richard,

We became aware of the Runtime CLI last week when our server restarted and failed to start services because there was more than one version but, unfortunately that isn't the problem in this case.

I read a thread that said that jobs with subjobs were not shipping the latest version of the subjob, so I extracted the functionality from the subjob and put it in the main job..

Somehow whilst trying to fix this, the problem has changed to another one, which is probably related? Hitting the endpoint now returns a 500 Server error with;

Map '/DATAANALYSIS/Maps/Jobs/SAP_Salesorder_API/SAPSalesOrder_From_JSON_Map' not found - project:P/DATAANALYSIS

DATAANALYSIS is the project name.

SAP_Salesorder_API is the job name.

SAPSalesOrder_From_JSON_MAP is the map name.

Again, this job still runs locally.

I look forward to anything you can come up with! I'm pretty much at a loss at this point.

Thanks

[Anonymous]

I've also just tried to hit the endpoint again and it returned the below...

Thread[qtp5263378-100,
    5,main
] Impossible

[Anonymous]

OK, I'm sure I could probably resolve this if I had access to your system, but that is not possible. Can I ask you to raise this as an urgent issue with support? They can remotely access your system (with your permission) and will be able to quickly identify what has happened. Thanks for raising this.

[Anonymous]

A ticket is already open but I've found that Talend Support is rather slow to reply.

Thanks for your help, I'll keep waiting for a reply from them!

[Anonymous]

Check your contract. You should have the ability to phone for assistance which may speed things up. Unfortunately support cannot always respond immediately, but you can chase them up if it is urgent. If you can PM me the support ticket number and your details, I may be able to speed things up. I don't often offer this, but I can see from your question that this is a serious issue

[Anonymous]

Is there any way we could see what maps have been deployed?

What steps would you take to troubleshoot this? Hopefully we can replicate them

Thanks

[Anonymous]

Was this built as a route (using a cRest component) or and calling a cTalendJob or as a service (some refer to this as a job)?

[Anonymous]

Sorry, I neglected to look back at the original post. So it is a service (built like a job). As such, you could get hold of the Jar that is the service and open it up using 7Zip. Then check inside to see what has been included. Other than that, it will mean looking through the logs and checking the features installed in your runtime.