Recurring warning "could not get type for name" in Transformer without any pipelines running.

  • 13 December 2023
  • 0 replies
  • 9 views

Userlevel 4
Badge

Environment: 

  • Transformer v5.4.

Issue: 

It has been observed that following errors are appearing in the transformer logs without any pipeline running on v5.4.

2023-08-14 04:04:35,552 [user:] [pipeline:] [stage:] WARN  Reflections - could not get type for name com.sun.xml.txw2.output.CharacterEscapeHandler from any class loader
st.shaded.org.reflections.ReflectionsException: could not get type for name com.sun.xml.txw2.output.CharacterEscapeHandler
at st.shaded.org.reflections.ReflectionUtils.forName(ReflectionUtils.java:312) ~[streamsets-transformer-dist_2.11-5.4.0.jar:?]
at st.shaded.org.reflections.Reflections.expandSuperTypes(Reflections.java:382) ~[streamsets-transformer-dist_2.11-5.4.0.jar:?]
at st.shaded.org.reflections.Reflections.<init>(Reflections.java:140) ~[streamsets-transformer-dist_2.11-5.4.0.jar:?]
at st.shaded.io.swagger.jaxrs.config.BeanConfig.classes(BeanConfig.java:276) ~[streamsets-transformer-dist_2.11-5.4.0.jar:?]
at st.shaded.io.swagger.jaxrs.config.BeanConfig.scanAndRead(BeanConfig.java:240) ~[streamsets-transformer-dist_2.11-5.4.0.jar:?]
at st.shaded.io.swagger.jaxrs.config.BeanConfig.setScan(BeanConfig.java:221) ~[streamsets-transformer-dist_2.11-5.4.0.jar:?]
at com.streamsets.datacollector.restapi.configuration.RestAPIResourceConfig.<init>(RestAPIResourceConfig.java:81) ~[streamsets-transformer-dist_2.11-5.4.0.jar:?]
  • Above warning is coming for the following classes as well:

    • org.osgi.framework.BundleListener

    • com.sun.xml.txw2.ContentVisitor 

    • com.sun.xml.txw2.NamespaceResolver 

    • com.sun.xml.txw2.output.XmlSerializer

    • org.apache.xml.resolver.CatalogManager

    • com.google.protobuf.AbstractMessageLite$InternalOneOfEnum

    • com.fasterxml.jackson.core.TSFBuilder

    • org.apache.commons.jxpath.ri.model.NodePointer

    • com.fasterxml.jackson.dataformat.xml.util.DefaultXmlPrettyPrinter

    • org.apache.tools.ant.Task

    • org.osgi.service.jdbc.DataSourceFactory

    • org.osgi.framework.BundleActivator

    • st.shaded.org.eclipse.jetty.jmx.ObjectMBean

    • com.sun.xml.txw2.TypedXmlWriter

    • org.jboss.marshalling.ByteOutput

    • org.osgi.framework.SynchronousBundleListener

    • com.sun.xml.txw2.DatatypeWriter

    • st.shaded.org.eclipse.jetty.alpn.ALPN$ServerProvider

    • st.shaded.org.eclipse.jetty.alpn.ALPN$ClientProvider

    • org.jboss.marshalling.ByteInput from any class loader

    • com.fasterxml.jackson.dataformat.xml.JacksonXmlModule

    • com.fasterxml.jackson.dataformat.xml.XmlMapper

    • st.shaded.org.eclipse.jetty.npn.NextProtoNego$ClientProvider

    • com.fasterxml.jackson.databind.cfg.MapperBuilder

    • st.shaded.org.eclipse.jetty.npn.NextProtoNego$ServerProvider

    • org.apache.commons.jxpath.ri.model.NodeIterator

    • org.jctools.queues.MpscArrayQueue from any class loader

    • org.apache.commons.jxpath.ri.model.NodePointerFactory

    • org.apache.xml.resolver.Catalog

    • com.sun.xml.txw2.Content

    • java.io.ObjectInputFilter

    • com.sun.xml.txw2.output.CharacterEscapeHandler

 

Solution:

As per our investigation, we found that these warning messages are coming from reflections library and version 0.10.2 is not throwing these warning messages. In fact, this logging is also not showing in the previous version of Transformer. reflection version library 0.9.10 and we are currently using version 0.9.12.

We have decided to upgrade to the latest version 0.10.2 to avoid these kinds of messages from org. reflections. As a workaround, you can change the log level to ERROR in the log4j properties file.

JIRA: TRANSFORMER-4427


0 replies

Be the first to reply!

Reply