topic Re: Logger can not be resolved to a type in Talend Studio

Logger can not be resolved to a type

Anonymous — Sat, 16 Nov 2024 09:53:47 GMT

Hi
I am trying to run a simple job on Talend Data Management studio 6.2.1
with tfileinputdelimited --> tlogrow
I am getting error as 'Logger can not be resolved to a type' highlighting every component

Could you please help resolve this error?

Thank in advance

Re: Logger can not be resolved to a type

Anonymous — Thu, 20 Apr 2017 07:15:56 GMT

Hi,

What's your OS and JDK version? Have you ever executed a job successfully in your Talend Data Management studio 6.2.1?

When you get some compile errors, please check your "Code" tab in your job. There will be your compile error highlighted in red line.

Best regards

Sabrina

Re: Logger can not be resolved to a type

Anonymous — Fri, 21 Apr 2017 06:46:17 GMT

Thanks for looking into this

I am using Windows 7 and JDK 1.8.0

I am getting error in code as follows

Please could you let me know if I need to make any changes

Thanks Again

Re: Logger can not be resolved to a type

Anonymous — Fri, 21 Apr 2017 08:16:11 GMT

Hi,

Have you ever executed a job successfully in your Talend Data Management studio 6.2.1? Have you already tried to click "sync columns " button on tLogRow component to see if it works?

Does this kind of issue (compile error) repro on all your jobs or a specific job?Is it Ok with you when re-create a new job in your studio?

Best regards

Sabrina

Re: Logger can not be resolved to a type

Anonymous — Mon, 24 Apr 2017 10:06:23 GMT

Hi Sabrina

I have not executed any job successfully as of now on TDM 6.2.1

Actually I executing some other job, it failed so I created this small job and tried but that also failed

Do I need to make any changes in configuration resolve this error?

Thanks and Regards

Neha

Re: Logger can not be resolved to a type

Anonymous — Mon, 24 Apr 2017 10:27:49 GMT

Hi,

We suppose that there is something wrong with your installation or configuration. Are you using oracle JDK 1.8 and have already installed your studio completely?

With your subscription solution, it is highly recommended that you should create a case on talend support portal so that we can give you a remote assistance on your issue through support cycle with priority.

Best regards

Sabrina

Re: Logger can not be resolved to a type

Anonymous — Mon, 05 Feb 2018 14:07:19 GMT

Hi Sabrina,

I have the similar issue.

My jobs were running fine and all of a sudden i got this issue.I use TAC for scheduling the jobs.

The scheduled TAC jobs are running fine.I am not able to generate and deploy and new jobs.So i checked running from studio, but i faced below issue.The issue is for all the jobs. I have not done any changes on JDK or Java settings.

Talend Version : 6.4.1.2017

OS: Windows 10 pro

org.talend.commons.exception.PersistenceException: org.talend.designer.runprocess.ProcessorException: Job compile errors
At least job "Jb_Sf_TaskObject" has a compile errors, please fix and export again.
Error Line: 3379
Detail Message: Logger cannot be resolved to a type
There may be some other errors caused by JVM compatibility. Make sure your JVM setup is similar to the studio.
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager.buildJob(BuildJobManager.java:234)
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager.buildJob(BuildJobManager.java:164)
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager.buildJobs(BuildJobManager.java:108)
at org.talend.repository.ui.wizards.exportjob.JobScriptsExportWizardPage.buildJobWithMaven(JobScriptsExportWizardPage.java:1487)
at org.talend.repository.ui.wizards.exportjob.JobScriptsExportWizardPage$8.run(JobScriptsExportWizardPage.java:1389)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1059)
at org.talend.repository.ui.wizards.exportjob.JobScriptsExportWizardPage.finish(JobScriptsExportWizardPage.java:1394)
at org.talend.repository.ui.wizards.exportjob.JavaJobScriptsExportWSWizardPage.finish(JavaJobScriptsExportWSWizardPage.java:1244)
at org.talend.repository.ui.wizards.exportjob.JobScriptsExportWizard.performFinish(JobScriptsExportWizard.java:126)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
at org.eclipse.jface.window.Window.open(Window.java:808)
at org.talend.repository.ui.actions.ExportJobScriptAction.doRun(ExportJobScriptAction.java:117)
at org.talend.repository.ui.actions.AContextualAction$2.run(AContextualAction.java:632)
at org.talend.repository.RepositoryWorkUnit.executeRun(RepositoryWorkUnit.java:99)
at org.talend.core.repository.model.AbstractRepositoryFactory.executeRepositoryWorkUnit(AbstractRepositoryFactory.java:258)
at org.talend.repository.localprovider.model.LocalRepositoryFactory.executeRepositoryWorkUnit(LocalRepositoryFactory.java:3369)
at org.talend.repository.gitprovider.core.GitRepositoryFactory.executeRepositoryWorkUnit(GitRepositoryFactory.java:369)
at org.talend.repository.remoteprovider.RemoteRepositoryFactory.executeRepositoryWorkUnit(RemoteRepositoryFactory.java:850)
at org.talend.core.repository.model.ProxyRepositoryFactory.executeRepositoryWorkUnit(ProxyRepositoryFactory.java:2119)
at org.talend.repository.ui.actions.AContextualAction.run(AContextualAction.java:641)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.talend.rcp.intro.Application.start(Application.java:255)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
Caused by: org.talend.designer.runprocess.ProcessorException: Job compile errors
At least job "Jb_Sf_TaskObject" has a compile errors, please fix and export again.
Error Line: 3379
Detail Message: Logger cannot be resolved to a type
There may be some other errors caused by JVM compatibility. Make sure your JVM setup is similar to the studio.
at org.talend.designer.runprocess.JobErrorsChecker.checkLastGenerationHasCompilationError(JobErrorsChecker.java:326)
at org.talend.designer.runprocess.DefaultRunProcessService.checkLastGenerationHasCompilationError(DefaultRunProcessService.java:380)
at org.talend.designer.runprocess.RunProcessService.checkLastGenerationHasCompilationError(RunProcessService.java:292)
at org.talend.designer.runprocess.ProcessorUtilities.generateBuildInfo(ProcessorUtilities.java:634)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:904)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:719)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:1270)
at org.talend.repository.ui.wizards.exportjob.handler.BuildJobHandler.generateJobFiles(BuildJobHandler.java:159)
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager$1.run(BuildJobManager.java:208)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
at org.talend.repository.ui.wizards.exportjob.scriptsmanager.BuildJobManager.buildJob(BuildJobManager.java:228)
... 60 more

Building_job_err.PNG

Re: Logger can not be resolved to a type

Anonymous — Wed, 07 Feb 2018 07:41:56 GMT

Hello

Could you please create a case on talend support portal so that we can give you a remote assistance on your issue through support cycle with priority?

Best regards

Sabrina

Re: Logger can not be resolved to a type

KarthikGs — Thu, 22 Mar 2018 05:27:00 GMT

so what is the solution?

Re: Logger can not be resolved to a type

Anonymous — Fri, 23 Mar 2018 06:21:03 GMT

Hello

This issue is probably caused by talend installer. What's talend build version you are using? Did you get this issue on your subscription solution?

Best regards

Sabrina

Re: Logger can not be resolved to a type

Anonymous — Thu, 10 May 2018 13:52:58 GMT

Hello, I met same problem. My Talend version is 6.4.1

Error in the component's properties:Logger cannot be resolved to a type
Logger cannot be resolved to a type
Logger cannot be resolved to a type
Logger cannot be resolved to a type
org.talend cannot be resolved to a type
org.talend cannot be resolved to a type
Logger cannot be resolved to a type
Logger cannot be resolved to a type
Logger cannot be resolved to a type
Logger cannot be resolved to a type

Re: Logger can not be resolved to a type

Anonymous — Fri, 18 May 2018 09:08:10 GMT

Hello,

Are you using talend installer to install your product? Could you please try to re-install it to see if it works?

Best regards

Sabrina

Re: Logger can not be resolved to a type

talend_consumer — Mon, 12 Aug 2019 08:43:21 GMT

Hi All,

I has exactly the same error but searching on it seemed re-install of talend client software was the only option...however luckily not in my case. I copied over the entire projects folder into a new location....created a new connection with the new location as my new workspace...then imported the project and that worked. So in summary create a new work space.