Saturday 20 January 2018

TALEND ERROR : DEBUGGING/TROUBLESHOOTING in TALEND


Sometimes, Talend (JAVA) works wierdly(To us, Actually it works correctly only by its nature).

It gives a ERROR specifying a COMPONENT name.
you/I will go to that specified COMPONENT and check the code.
All of the code is 100% correct.
Even it gives the ERROR in that COMPONENT only.

In this case How are we going to HANDLE?


SOL:

For Example :

A talend job consists of 3 flows.
Say,Each flow consists of 4 to 5 components.

In order to debug any kind of ERROR, just follow the BASIC thumb rule i am going to tell you.
and Most of the time 99.99% you will definitely find , where the job is EXACTLY failing.

you just got to DISABLE/DE-ACTIVATE the COMPONENTS one by one from the STARTING COMPONENT TO THE COMPONENT where it is giving ERROR.

MOSTLY, the ERROR occurs with the PRIOR component adjacent to the ERRORED component.



TALEND/TAC ERROR : CONNECTION TO THE SERVER FAILED in TAC (Talend Adminstrator Center)

0)Check the SERVERS section in the  left hand pane whether the corresponding JOB SERVER is in RUNNING state or not.
If the JOBSERVER  is not RUNNING, then RESTART the VM in which TAC is installed.

1)The job you deployed in TAC, might have been corrupted.
    Hence BUILD the talend job again and re-deploy the job in TAC.

2)Check for the  HARDDISK capacity in the VM in which TAC is installed.
   If the HARDDISK  size/capacity is very LOW then try to delete some of the UNNECESSARY data and try to RE-DEPLOY the job.





COURTS : CASES : LAWYERS : JUDGES : ::::::::: VICTIMS : ACCUSED

  *We have got so many SMART people in our COUNTRY. *we have got so many IIT completed SMART students in our COUNTRY. * we have got so many ...