[
https://issues.apache.org/jira/browse/TIKA-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426378#comment-17426378
]
Lewis John McGibbney commented on TIKA-3453:
--------------------------------------------
OK so the problem lies in the tika-server source NOT with tika-docker or
tika-helm. Using main branch I can replicate as well
% java -jar tika-server-core-2.1.1-SNAPSHOT.jar
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
details.
Oct 08, 2021 2:05:20 PM org.apache.cxf.endpoint.ServerImpl initDestination
INFO: Setting the server's publish address to be http://localhost:9998/
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder" Defaulting to
> no-operation (NOP) logger implementation for tika-docker 2.0.0-BETA
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TIKA-3453
> URL: https://issues.apache.org/jira/browse/TIKA-3453
> Project: Tika
> Issue Type: Bug
> Components: docker, server
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Major
> Fix For: 2.1.1
>
>
> It looks like logging libraries are not being interpreted correctly from Java
> classpath.
> We need logging turned on so we can intercept anomalies.
> Investigating...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
