Talend Job not stopping on TAC

[_AnonymousUser]

Hi,
I ran a talend job using TAC Job Conductor.It Populated all the required tables and log says Completed Successfully but Job Conductor job showing a weird status like "Running...." Status.Can some body help me out whats the issue..?
Other thing i missed out is when we try to stop the job it wont get stopped.
Thanks,
Kiran Kumar

[Anonymous]

Hi,
Perhaps there some wrong with DB connection. Although job is successful yet it is still waiting for the results of the database query. Would you give us the error log in tomcat, and we will check where is the wrong.
Best regards
Sabrina

[_AnonymousUser]

Hi,
Required Data is populated in the Tables and talend Log file shows the strat and end time of job which ran successfully.
We are uisng Web logic instead of Tomcat and in Weblogic log file there is a continous exception looks like:
2012-12-18 09:58:22 ERROR ServerMsgServiceImpl - org/talend/commons/exception/BusinessException.<init>(Lorg/talend/gwttoolkit/PropertiesLoader;Ljava/lang/String;[Ljava/lang/Object V
java.lang.NoSuchMethodError: org/talend/commons/exception/BusinessException.<init>(Lorg/talend/gwttoolkit/PropertiesLoader;Ljava/lang/String;[Ljava/lang/Object V
at org.talend.administrator.softwareupdate.SoftwareUpdateBusiness.checkArchivaRepos(SoftwareUpdateBusiness.java:109)
at org.talend.administrator.softwareupdate.SoftwareUpdateBusiness.getAvailablePatches(SoftwareUpdateBusiness.java:149)
at org.talend.gwtadministrator.server.message.ServerMsgServiceImpl.alertForVersionOrPatches(ServerMsgServiceImpl.java:131)
at org.talend.gwtadministrator.server.message.ServerMsgServiceImpl.getIdMessages(ServerMsgServiceImpl.java:65)
at sun.reflect.GeneratedMethodAccessor587.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:562)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:207)
at org.talend.gwttoolkit.server.TalendRemoteServiceServlet.processCall(TalendRemoteServiceServlet.java:81)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:243)
at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Please help me with the solution.Is it a Version Conflict or a Bug?
thanks,
Kiran

[Anonymous]

Hi,

We are uisng Web logic instead of Tomcat and in Weblogic log file there is a continous exception looks like

As I known, there is no mentioned that the Web logic can be supported by talend in user manual doc. Usually, our user use tomcat as the server. There is no supported environment for Web logic.
Best regards
Sabrina

[Anonymous]

Hi @xdshi ,

We faced same problem a day before and we had to restart the server.

While searching solution for this issue, i found 2 most recommended solutions

1. Update some details about the task in the database

2. Restart the server

In my view, both solutions are not feasible when it happens in production. Can you let me know if there is any other way to stop the task from TAC ?

FYI : We are using talend 7.1.1 subscription.

[Anonymous]

Hello,

There is a variety of reasons for this issue. Could you please create a support case on talend support portal so that our colleagues from support team will see if there is a feasible solution for you in production environment.

Best regards

Sabrina