Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Want to see what's currently in public preview? We've pulled it all together in one place. Check it out here
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] missing jar:org.apache.commons.logging_1.1.1.v201101211721.jar

G'Day,

When I attempt to run a job I get the following error:

Contents of E:\Program Files\Talend\6.2\Studio\workspace\.metadata\.log:

!MESSAGE 2016-05-24 01:09:52,576 INFO  org.talend.commons.exception.CommonExceptionHandler  - The download URL for org.apache.commons.logging_1.1.1.v201101211721.jar is not available

!ENTRY org.talend.platform.logging 1 0 2016-05-24 01:09:59.049
!MESSAGE 2016-05-24 01:09:59,049 INFO  org.talend.commons.exception.CommonExceptionHandler  - missing jar org.apache.commons.logging_1.1.1.v201101211721.jar

!ENTRY org.talend.platform.logging 1 0 2016-05-24 01:10:08.572
!MESSAGE 2016-05-24 01:10:08,569 INFO  org.talend.commons.exception.CommonExceptionHandler  - Missing jars: org.apache.commons.logging_1.1.1.v201101211721.jar
!STACK 0
org.talend.commons.exception.BusinessException: Missing jars: org.apache.commons.logging_1.1.1.v201101211721.jar
at org.talend.designer.runprocess.java.JavaProcessorUtilities.handleMissingJarsForProcess(JavaProcessorUtilities.java:453)
at org.talend.designer.runprocess.java.JavaProcessorUtilities.sortClasspath(JavaProcessorUtilities.java:370)
at org.talend.designer.runprocess.java.JavaProcessorUtilities.computeLibrariesPath(JavaProcessorUtilities.java:277)
at org.talend.designer.runprocess.DefaultRunProcessService.updateLibraries(DefaultRunProcessService.java:261)
at org.talend.designer.runprocess.RunProcessService.updateLibraries(RunProcessService.java:190)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:464)
at org.talend.designer.runprocess.ProcessorUtilities.generateCode(ProcessorUtilities.java:1298)
at org.talend.designer.runprocess.RunProcessContext$1.run(RunProcessContext.java:561)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:527)
at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:284)
at org.eclipse.ui.internal.progress.ProgressManager.run(ProgressManager.java:1190)
at org.talend.designer.runprocess.RunProcessContext.exec(RunProcessContext.java:524)
at org.talend.designer.runprocess.ui.ProcessComposite.exec(ProcessComposite.java:1450)
at org.talend.designer.runprocess.ui.views.ProcessView$RunAction.run(ProcessView.java:691)
at org.talend.designer.runprocess.ui.actions.RunProcessAction.run(RunProcessAction.java:58)
at org.talend.designer.core.debug.JobLaunchConfigurationDelegate$1.run(JobLaunchConfigurationDelegate.java:84)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764)
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:197)
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(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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)
Manually pointing to the missing jar makes no difference:


Finally, the following is logged to the console:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See  for further details.
Question: how to resolve the missing JAR file - org.apache.commons.logging-1.1.1.v201101211721.jar ??
0683p000009ME6y.png 0683p000009MDwN.png 0683p000009ME2h.png
Labels (3)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Solved.
The problem was an incorrect "-" (dash) instead of an underscore in the JAR filename.
The JAR downloaded from http://central.maven.org/maven2/org/eclipse/birt/runtime/org.apache.commons.logging/1.1.1.v201101211...
contained a "-" (dash) in the filename, instead of an "_" (underscore), resulting in an incorrect installation path.
Solution was to rename the JAR (with underscore) to org.apache.commons. logging_1.1.1.v201101211721.jar.
When installed, this generated a folder in the ...\libraries folder called 
org.apache.commons. logging_1.1.1.v201101211721
The attached screenshot shows the correctly named folder alongside the incorrect folder.
0683p000009MEBi.png
Regards
Alex Bramford

View solution in original post

2 Replies
Anonymous
Not applicable
Author

SLF4J is not part of the org.apache.commons.logging framework!
Checkout the download page here:  http://www.slf4j.org/download.html
Anonymous
Not applicable
Author

Solved.
The problem was an incorrect "-" (dash) instead of an underscore in the JAR filename.
The JAR downloaded from http://central.maven.org/maven2/org/eclipse/birt/runtime/org.apache.commons.logging/1.1.1.v201101211...
contained a "-" (dash) in the filename, instead of an "_" (underscore), resulting in an incorrect installation path.
Solution was to rename the JAR (with underscore) to org.apache.commons. logging_1.1.1.v201101211721.jar.
When installed, this generated a folder in the ...\libraries folder called 
org.apache.commons. logging_1.1.1.v201101211721
The attached screenshot shows the correctly named folder alongside the incorrect folder.
0683p000009MEBi.png
Regards
Alex Bramford