[resolved] tRunTask throws Exceptions

[Anonymous]

Hello All,
we are using the customized component "tRunTask" from cimt ag. The problem is that this component throws exceptions at our customer but in contrast it runs smoothly at our local installation.
Has anybody ideas why this component "tRunTask" has problems with the task id?
Task null: got id for label: DI2012_EXPORT_ORCHESTRATION_PART_1
Exception in component tRunTask_1
java.lang.IllegalArgumentException: taskId cannot be null or empty
at de.cimt.talendcomp.tac.TaskAction.setTaskId(TaskAction.java:18)
at company.exportstarterjms_a_0_1.ExportStarterJMS_A.tRunTask_1Process(ExportStarterJMS_A.java:3159)
at company.exportstarterjms_a_0_1.ExportStarterJMS_A.tJDBCInput_1Process(ExportStarterJMS_A.java:3059)
at company.exportstarterjms_a_0_1.ExportStarterJMS_A.tJMSInput_1Process(ExportStarterJMS_A.java:2212)
at company.exportstarterjms_a_0_1.ExportStarterJMS_A.runJobInTOS(ExportStarterJMS_A.java:5034)
at company.exportstarterjms_a_0_1.ExportStarterJMS_A.main(ExportStarterJMS_A.java:4446)
Kind regards
Hilderich
 

[Anonymous]

It looks like there is a bug in the components error handling. Are you sure the Task (with case sensitive label!!) exists - please do not think about the job name! 
Could you please show me the configuration of the component?
I guess in the customer environment the component runs in a task build by the commandline?
I have often the problem with the command line because the commandline knows 2 different sources for user components:
1. the user component path
2. the components directory under the project. 
If you have deployed one of the first releases and use a Talend release older the 5.3 you will experience a strange behaviour of the commandline:
The commandline commits (!) the user components into the project components directory. If you update the component in the user component directory this update will be shadowed with now old release in the project components dir.
My way to solve that is to delete (and commit this deletion) the components in the project/components dir.
On the commandline:
1. stop the commandline (and check if the commandline is not running anymore!!)
2. delete the dir commandline-workspace
3. start the commandline (the deleted dir will be recreated automatically)

[Anonymous]

Hello jLolling,
Many thanks for your answer. The customer has as we do the TAC in use and we are not in touch
with its underlying commandline. We have desigend and tested the DI Jobs and the customer tries to install
theses jobs via its own TAC over a shared SVN. But that doesn't work because the component tRunTask
makes troubles. Enclosed you find a screenshot of the TAC that gives you the evidence that the job label
corresponds to the component configuration.
We use Talend 5.3.1 all the way through.
I have looked into the commandline view inside TAC and there is an entry about customer components
(see screenshot below). There is stated a path for customer components and when I look into it I can
see the tRunTask component. I can also find the component in
~/Talend-5.3.1/cmdline/studio/commandline-workspace/<project>/components/
That means it is not the problem you supposed.
Kind regards,
Hilderich

[Anonymous]

Hi Hilderich,
because of the screenshot I could say the task is correct but you would receive a meaningful message if this would be the case.
Indeed the terrible behaviour to commit component into the project dir and read them at last causes often problems. This bug is actually solved I guess in 5.4.
I suggest you delete the content of the dir ~/Talend-5.3.1/cmdline/studio/commandline-workspace/<project>/components/ 
in SVN (/<PROJECT>/trunc/components/) and repeat the commandline reset.
Another approach could be commit the new release of the component into the project component dir (with the project settings dialog). This way you avoid this problem. But this causes sometimes the problem the components will not loaded by the commandline. It is a nightmare !
If you mind, we can make a webex session to get it solved. Contact me per email: jan.lolling@gmail.com.
Best regards
Jan Lolling

[Anonymous]

Hello Jan,
That is very kind of you to provide us your help via webex session - many thanks for that.
Fortunately I logged on to the customer's TAC and there I have generated, deployed and run the DI Job again and now it works!?
Previously the customer did this. I don't know what happend differently.
Thank you for your hints regarding customized components and its location.
Kind regards
Hilderich

[Anonymous]

Great to hear! In the upcoming release of Talend 5.6 the TAC will provide much better information about the job error code and the check for the task status will be much more reliable because I do not have to deal with unrelated stats anymore.
I would wait until 5.6.2 before start using it - you know the Talend maturation time 😉

[Anonymous]

Hi Jlolling,
We are currently facing an issue when we use truntask.It would be very helpful if you can help us resolve this.
the truntask fails intermittently when we try to trigger multiple jobs.
For eg: we will be exposing our job as a web service,the job contains the truntask component.
When we trigger multiple instances of the job at the same time,we get the below exception and one our job does not run.
Task 277: got id for label: jB0610
Task jB0610: Own task is currently started or running. Wait for its end.
Task jB0610: All precondition tasks has been finished.
05:32:22.777# Task jB0610 starting ...
{"actionName":"runTask","authUser":"admin@company.com","authPass":"admin","taskId":"277","context":{"Filetype":"1","FileName":"/data01/Mule/EmbeddedFTP/NE45/Home/ne45bmrs_ftp_user1/XML/NGET-EMFIP-ATL8.xml","FileUniqueID":"1b1e3432-22d5-11e4-848e-31d6936bf221","properties":"/data01/Talend-5.4.1/XSDFiles/Phase1context.txt"},"mode":"asynchronous"}
Exception in component tRunTask_5
java.lang.Exception: Server error:The requested action cannot be carried out because the execution task
        at de.cimt.talendcomp.tac.TACAction.executeRequest(TACAction.java:133)
        at de.cimt.talendcomp.tac.RunTask.execute(RunTask.java:32)
        at bmrs.jinvoketalendjob_1_0.jInvokeTalendJob.tRunTask_5Process(jInvokeTalendJob.java:5032)
        at bmrs.jinvoketalendjob_1_0.jInvokeTalendJob.tMysqlInput_1Process(jInvokeTalendJob.java:4746)
        at bmrs.jinvoketalendjob_1_0.jInvokeTalendJob.tMysqlRow_1Process(jInvokeTalendJob.java:3699)
        at bmrs.jinvoketalendjob_1_0.jInvokeTalendJob.tMysqlRow_7Process(jInvokeTalendJob.java:3577)
        at bmrs.jinvoketalendjob_1_0.jInvokeTalendJob.tMysqlInput_3Process(jInvokeTalendJob.java:3312)
        at bmrs.jinvoketalendjob_1_0.jInvokeTalendJob.tMysqlConnection_1Process(jInvokeTalendJob.java:3006)
        at bmrs.jinvoketalendjob_1_0.jInvokeTalendJob.runJobInTOS(jInvokeTalendJob.java:13813)
        at bmrs.jinvoketalendjob_1_0.jInvokeTalendJob.runJob(jInvokeTalendJob.java:13338)
        at sun.reflect.GeneratedMethodAccessor408.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
        at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
        at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
        at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
        at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
        at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
        at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
        at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
        at org.apache.axis.transport.http.QSMethodHandler.invokeEndpointFromGet(QSMethodHandler.java:129)
        at org.apache.axis.transport.http.QSMethodHandler.invoke(QSMethodHandler.java:94)
        at sun.reflect.GeneratedMethodAccessor407.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.axis.transport.http.AxisServlet.processQuery(AxisServlet.java:1226)
        at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:249)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
        at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
        at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
        at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:744)
 Unable to invoke talend job jB0610 for /data01/Mule/EmbeddedFTP/NE45/Home/ne45bmrs_ftp_user1/XML/NGET-EMFIP-ATL8.xml. ( FileUniqueID= 1b1e3432-22d5-11e4-848e-31d6936bf221)
/data01/Mule/EmbeddedFTP/NE45/Home/ne45bmrs_ftp_user1/XML/NGET-EMFIP-ATL9.xml

[Anonymous]

This is an error message from the TAC server. The request to run the task was successfully received (thats the purpose of my component) but cannot carried out because ... ok here we are missing the actual problem. 
I have never seen such error and it looks like the TAC is self has a problem. Could you start the task with in the TAC webapp?
Could you please try to run this task with the MetaServletCaller (my component tRunTask uses the same communication methods like the Talend provided MetaServletCaller.

[_AnonymousUser]

t8UbJV <a href="">ngrgsseyzeca</a>, dddhervhcbgk, hxbuscelmylo,

[Anonymous]

Hi jlolling,
Thank you very much for responding..
We are currently facing this issue when we run try to invoke the job multiple times(say 15 times parallely at a single time).
So what happens is ,the jobs in TAC are invoked one by one, and intermittently as you said one the job gets triggeref but fails to run.Since we are invoking it 15 times,other instance of it starts running and we receive the above exception for the job that did not run.
Is there any way to handle this exception?
we will not be able to run the job multiple times at a single time using metaservlet.
Regards,
Scmal