tHMap is not working on the ESB Runtime

[APopova1632837688]

Hello.

The service is working successfully in Talend Studio V7.3.1.

But after deployment on the ESB Runtime, it displays this message:

org.apache.avro.AvroTypeException:Expected start-union. Got END_OBJECT

I do not use any functions in tHMap.

This issue is with all services that use tHMap.

Can you please help in resolving the issue.

[michad]

Hello,

Using the tHMap and cHMap components requires the installation of a feature in Karaf.

Connect to the Karaf shell and run the command "feature:list | grep talend" to see if a feature named "talend-data-mapper" is present. If this feature is present but not installed then launch its installation by running the command "feature:install talend-data-mapper".

Hope this helps.

[APopova1632837688]

Thanks for the answer.

I will try to do it the way you wrote it.

But TDM features were installed in Karaf.

Old services with tHMap work on this ESB Runtime.

The only issue is with new publications.

[APopova1632837688]

Hello.

I did it the way you wrote it, the issue did not solved.

[NGuittet]

Hello,

I face the same issue.

My tHMap is in a job called from a route (ESB Package), and I get the exact same 'org.apache.avro.AvroTypeException: Expected start-union. Got END_OBJECT' exception while it executes properly within the Studio...

And the talend-data-mapper features are installed on my Karaf too.

Anyone ?

[youssef2]

Hello,

Any news about the error org.apache.avro.AvroTypeException: Expected start-union. Got END_OBJECT?

I'm using talend 7.31 evreything is ok on studio but the runtime fail to run the service!

It seems to be a bug on this version. any workarounds?

[NGuittet]

Hi,

We had reply from the support to install the latest Runtime patch.

Also, make sure your route subjobs are correctly having the build type 'Bundle OSGi' (in the "Job" tab, "Deployment" subtab).

From our side, we abandonned the tHMap.

We came back to more usual components, like tFlowToIterate/tFixedFlowInput to handle data over loops, tWriteJSONField to build parts of the JSON, and tJava/tJavaRow to aggregate built strings...

This is way bigger than a single tHMap in the job design, but more maintenable as I can spot easily which loop needs attention.

And obviously, this needs no additional dependancy to deploy...

Good luck.