Thanks again for the suggestion. It looks much different in 2.2.0 with the slf4j error gone. Now, though, it seems to ignore my log4j2.xml settings. The next thing to tackle. ;-)
INFO [main] 16:11:57,065 org.apache.tika.server.core.TikaServerProcess Starting Apache Tika 2.2.0 server
INFO [main] 16:11:57,609 org.apache.cxf.endpoint.ServerImpl Setting the server's publish address to be http://localhost:9998/
INFO [main] 16:11:57,650 org.eclipse.jetty.util.log Logging initialized @1627ms to org.eclipse.jetty.util.log.Slf4jLog
INFO [main] 16:11:57,695 org.eclipse.jetty.server.Server jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.7+10
INFO [main] 16:11:57,735 org.eclipse.jetty.server.AbstractConnector Started ServerConnector@1436a7ab{HTTP/1.1, (http/1.1)}{localhost:9998}
INFO [main] 16:11:57,735 org.eclipse.jetty.server.Server Started @1713ms
WARN [main] 16:11:57,742 org.eclipse.jetty.server.handler.ContextHandler Empty contextPath
INFO [main] 16:11:57,754 org.eclipse.jetty.server.handler.ContextHandler Started o.e.j.s.h.ContextHandler@2a1debfa{/,null,AVAILABLE}
INFO [main] 16:11:57,766 org.apache.tika.server.core.TikaServerProcess Started Apache Tika server 3fa770f1-00d4-4bc3-9061-e0b83586eb5e at http://localhost:9998/
INFO [main] 16:11:57,609 org.apache.cxf.endpoint.ServerImpl Setting the server's publish address to be http://localhost:9998/
INFO [main] 16:11:57,650 org.eclipse.jetty.util.log Logging initialized @1627ms to org.eclipse.jetty.util.log.Slf4jLog
INFO [main] 16:11:57,695 org.eclipse.jetty.server.Server jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.7+10
INFO [main] 16:11:57,735 org.eclipse.jetty.server.AbstractConnector Started ServerConnector@1436a7ab{HTTP/1.1, (http/1.1)}{localhost:9998}
INFO [main] 16:11:57,735 org.eclipse.jetty.server.Server Started @1713ms
WARN [main] 16:11:57,742 org.eclipse.jetty.server.handler.ContextHandler Empty contextPath
INFO [main] 16:11:57,754 org.eclipse.jetty.server.handler.ContextHandler Started o.e.j.s.h.ContextHandler@2a1debfa{/,null,AVAILABLE}
INFO [main] 16:11:57,766 org.apache.tika.server.core.TikaServerProcess Started Apache Tika server 3fa770f1-00d4-4bc3-9061-e0b83586eb5e at http://localhost:9998/
-- Josh
----- Original message -----
From: "Josh Burchard" <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: Failed to load slf4j
Date: Mon, Dec 20, 2021 1:58 PM
Thanks for the reply Konstantin.Yes I'll be upgrading to 2.2.1 for sure. I didn't see the issue already in Jira so I thought maybe I'm the only one and I'm doing something incorrectly. I'll give 2.2.0 a try now and see if it's resolved already.-- Josh----- Original message -----
From: "Konstantin Gribov" <[email protected]>
To: [email protected]
Cc:
Subject: Re: Failed to load slf4j
Date: Mon, Dec 20, 2021 1:40 PM
Josh,I could reproduce this issue but I would recommend to update tika-server to 2.2.0 or wait a couple of days for 2.2.1, it should be released soon since vote for 2.2.1 rc3 is already in progress.--Best regards,Konstantin Gribov.On Mon, Dec 20, 2021 at 7:53 PM Josh Burchard <[email protected]> wrote:I'm using the Tika 2.1 server and I want to start making sure exceptions and other interesting issues get logged to a file. Unfortunately I always get this error no matter what I've tried:w64 [C:\] "C:\Program Files\AdoptOpenJDK\jdk-11.0.7.10-hotspot\bin\java.exe" -Dlog4j.configurationFile="file:C:\tmp\log4j2Tika.xml" -jar "C:\tmp\tika-server21.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.
Dec 20, 2021 11:44:04 AM org.apache.cxf.endpoint.ServerImpl initDestination
INFO: Setting the server's publish address to be http://localhost:9998/I must be doing something silly but I can't figure out what that may be. The only search hits I've gotten on this error seem to be Maven related and I'm not building from source, I just have the downloaded jar.
