
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
tSendMail Compile Error with javax.activation.DataHandler
Hello,
first of all:
I tried and build several Mappings, SubJobs and Send Log Mails on my Windows Computer (Win10) in TOS () with Adopt OpenJDK 11.
It worked totally fine.
Now I switched to a Linux Machine (Debian Xfce 4.12) with Talend Version 7.3.1.20200219_1130.
I exported via Copy and Paste (Copy my Project Folder from Windows and Pasted to Linux Directory).
Everything is working fine except Mappings with the tSendMail Component.
I always get the same Error Code and also tried to switch to another JDK but its the same.
I also created a whole empty new Project only with one Job which includes 1 tSendMail Component but at compiling even without editing one Property in the Component ill get the Error.
All Additional Packages and Modules are installed.
Installed JRE Configuration under Preferences
I also upload the Configuration in the "About Talend Studio" Section.
Thanks in Advance
Error Log:
org.talend.designer.runprocess.ProcessorException: Job compile errors
At least job "BI_TEST" has a compile errors, please fix and export again.
Error Line: 1
Detail Message: The type javax.activation.DataHandler cannot be resolved. It is indirectly referenced from required .class files
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:358)
at org.talend.designer.runprocess.DefaultRunProcessService.checkLastGenerationHasCompilationError(DefaultRunProcessService.java:539)
at org.talend.designer.runprocess.RunProcessService.checkLastGenerationHasCompilationError(RunProcessService.java:317)
at org.talend.designer.runprocess.ProcessorUtilities.generateBuildInfo(ProcessorUtilities.java:955)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:615)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:2068)
at org.talend.designer.runprocess.RunProcessContext$1.run(RunProcessContext.java:601)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:440)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:356)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:474)
at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:240)
at org.eclipse.ui.internal.progress.ProgressManager.run(ProgressManager.java:966)
at org.talend.designer.runprocess.RunProcessContext.exec(RunProcessContext.java:548)
at org.talend.designer.runprocess.ui.ProcessComposite.exec(ProcessComposite.java:1448)
at org.talend.designer.runprocess.ui.views.ProcessView$RunAction.run(ProcessView.java:700)
at org.talend.designer.runprocess.ui.actions.RunProcessAction.run(RunProcessAction.java:63)
at org.talend.designer.core.debug.JobLaunchConfigurationDelegate$1$1.run(JobLaunchConfigurationDelegate.java:98)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4906)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4475)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
at org.talend.rcp.intro.Application.start(Application.java:280)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
at org.eclipse.equinox.launcher.Main.main(Main.java:1474)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What about if you create a new job and use tSendMail component in a new project? Do you still have the same compile errors.
Regards
Shong

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
yeah as i wrote above.
I created a whole new Project with one Job which includes one tSendMail Component but got again the compiler errors.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please try this workaround provided by our R&D team:
the workaround is to add missed javax.activation jar
- download the jar file from this site:https://mvnrepository.com/artifact/javax.activation/activation/1.1
- load the component using tLibraryLoad component in the beginning of job.
Let me know if it works.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It worked, thank you!
Is there another Workaround without using the tLibraryLoad component?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Open the Module views and check the installation status of required jar files for features or component such as activation-1.1.jar in this case, install the jar from modules view if it isn't installed yet.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is a Screenshot from my Modules View.
As you can See i installed it already or can you see something strange in my Installed Modules?
