Closed cookie33 closed 4 years ago
I've tried this out with HRLS 1.0.5 and Handle 9.2.0 but could not reproduce these errors. Independent of whether the servlet is installed or not, I get just a warning related to SLF4J that is, however, different from what you got:
"2019-12-03 12:26:07.242+0100" 25 Started new run. "2019-12-03 12:26:07.243+0100" 25 Handle.net Server Software version 9.2.0 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.
Whe are using Centos 7.7:
$ cat /etc/redhat-release
CentOS Linux release 7.7.1908 (Core)
And openjdk
version:
$ java -version
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)
What are you using?
p.s. the SLF4J warning we also get. But according to CNRI that is NOT a problem.
The answer of CNRI about the SLF4J warning:
This can be ignored, as the component that is using SLF4J is little-used and does not have important log information.
If you wish to suppress the error message, you can add this JAR file
https://repo1.maven.org/maven2/org/slf4j/slf4j-simple/1.7.25/slf4j-simple-1.7.25.jar
to the "lib" directory of your Handle distribution. This is the solution that will be used in the eventual handle-9.2.1 release.
We also have a jetty.xml file in the directory with config.dct:
<?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd">
<!-- =============================================================== -->
<!-- Configure the Jetty Request Log -->
<!-- =============================================================== -->
<Configure id="Server" class="org.eclipse.jetty.server.Server">
<!-- =========================================================== -->
<!-- Configure Request Log -->
<!-- =========================================================== -->
<Get id="handler" name="handler" />
<Set name="handler">
<New id="Handlers" class="org.eclipse.jetty.server.handler.HandlerCollection">
<Set name="handlers">
<Array type="org.eclipse.jetty.server.Handler">
<Item>
<Ref id="handler"/>
</Item>
<Item>
<New id="RequestLog" class="org.eclipse.jetty.server.handler.RequestLogHandler"/>
</Item>
</Array>
</Set>
</New>
</Set>
<Ref id="RequestLog">
<Set name="requestLog">
<!-- Use AsyncNCSARequestLog for improved request latency -->
<New id="RequestLogImpl" class="org.eclipse.jetty.server.NCSARequestLog">
<Set name="filename"><Env name="HANDLE_SVR"/>/logs/jetty-request.log-yyyy_MM_dd</Set>
<Set name="filenameDateFormat">yyyyMMdd</Set>
<Set name="retainDays">0</Set>
<Set name="append">true</Set>
<Set name="extended">false</Set>
<Set name="logCookies">false</Set>
<Set name="LogTimeZone">GMT</Set>
</New>
</Set>
</Ref>
</Configure>
Reproduced when the problem was introduced. We had the following problem on startup:
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.
For that CNRI advised to install:
https://repo1.maven.org/maven2/org/slf4j/slf4j-simple/1.7.25/slf4j-simple-1.7.25.jar
We installed it in the lib directory of the handle server:
wget https://repo1.maven.org/maven2/org/slf4j/slf4j-simple/1.7.25/slf4j-simple-1.7.25.jar
After this we see the errors with hrls
reverse lookup servlet.
Obsolete. In handle version 9.3.0 this error does not occur anymore. It just complains about SLF4J being present two times. But it works.
So close issue
With handle version 9.2.0
slf4j-api-1.7.25.jar
is installed in the handlelib
directory. To get rid of errors also following is installed in the directory:slf4j-simple-1.7.25.jar
. Without the reverse lookup.war the error log looks as follows:Than we add the reverse lookup servlet:
It than gives loads of errors/warnings: