The new version 3.6 of Knime Analytics Platform is blocked after running several KWs in batch mode.
When trying to run it the following error is received:
CompilerOracle: exclude javax/swing/text/GlyphView.getBreakSpot
Aug 15, 2018 3:02:12 AM org.apache.cxf.bus.osgi.CXFExtensionBundleListener addExtensions
INFO: Adding the extensions from bundle org.apache.cxf.cxf-rt-transports-http (129) [org.apache.cxf.transport.http.HTTPTransportFactory, org.apache.cxf.transport.http.HTTPWSDLExtensionLoader, org.apache.cxf.transport.http.policy.HTTPClientAssertionBuilder, org.apache.cxf.transport.http.policy.HTTPServerAssertionBuilder, org.apache.cxf.transport.http.policy.NoOpPolicyInterceptorProvider]
Aug 15, 2018 3:02:13 AM org.apache.cxf.bus.blueprint.NamespaceHandlerRegisterer register
WARNING: Aries Blueprint packages not available. So namespaces will not be registered
java.lang.NoClassDefFoundError: org/apache/aries/blueprint/NamespaceHandler
at java.lang.ClassLoader.defineClass1(Native Method)
10:51 AM
Caused by: java.lang.ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler cannot be found by org.apache.cxf.cxf-core_3.0.7
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:484)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 178 more
10:52 AM
Caused by: java.lang.ClassNotFoundException: org.apache.aries.blueprint.NamespaceHandler cannot be found by org.apache.cxf.cxf-rt-frontend-jaxrs_3.0.7
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:484)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 157 more
Hi, my workflow also crashes due to that warning. Do you have a solution yet please?
I launch it from command prompt:
knime.exe -consoleLog -nosplash -consoleLog -nosave -reset -preferences=“D:\Users\XXX\knime-workspace\XXX.epf” -application org.knime.product.KNIME_BATCH_APPLICATION -workflowDir=“C:\Users\Public\Documents\XXX_2019-01-02v2” -destFile=“C:\Users\Public\Documents\tested.zip”
The workflows goes ok until:
ADVERTENCIA: Aries Blueprint packages not available. So namespaces will not be registered
java.lang.NoClassDefFoundError: org/apache/aries/blueprint/NamespaceHandler
As other people have mentioned, this is a common, and non-application-crashing log message - i see it as well, launching from the development environment and not. Unless your specific workflow actually uses nodes which use Blueprint classes directly, i don’t believe it is very likely that this is the source of your workflow crash. Could you supply the whole log from your failed run?
From what I have seen, this error doesn’t happen if you launch the KNIME GUI at some point after you installed it on the machine. In a headless environment obviously that isn’t an option. You should be able to reproduce it by installing knime on the environment and trying to run it in batch mode without ever launching the actual GUI.
Hi! Thanks for such a quick answer. I removed a node that was not active nor connected but still, printing “ERROR” what was surely the cause of a bad log message.
Seems it works in spite of this error!
This is not a KNIME issue per se; Apache libraries which are a dependency of something, on which KNIME depends, have a bug that was fixed in a newer version ( see https://issues.apache.org/jira/browse/CXF-7142 ). At some point KNIME will be able to migrate to a newer version of the dependency which will hopefully move the CXF dependency (currently on 3.0.7) to a fixed version.
I got the information that this behavior is related to a problem with a third party dependency, as quaeler pointed out. Since this dependency is fixed already, I would assume KNIME is using the fixed version soon and then its solved. Maybe KNIME can comment on that.