Warnings in Tomcat log

Products

• CA Service Desk Manager
• CA Service Management - Service Desk Manager

Issue/Introduction

After upgrading to CA Service Desk Manager 17.2, the following warning messages have started to be written in Tomcat log just after the SDM service starts. Do they cause any problem?

INFO: Starting ProtocolHandler [https-jsse-nio-8446]
Aug 26, 2019 4:30:29 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [http-nio-8080]
Aug 26, 2019 4:30:29 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3673 ms
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.tomcat.util.buf.ByteBufferUtils (file:/D:/CA/SC/tomcat/8.5.6/lib/tomcat-util.jar) to method java.nio.DirectByteBuffer.cleaner()
WARNING: Please consider reporting this to the maintainers of org.apache.tomcat.util.buf.ByteBufferUtils
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Aug 26, 2019 4:32:22 PM org.apache.tomcat.util.buf.ByteBufferUtils <clinit>
WARNING: Cannot use direct ByteBuffer cleaner, memory leaking may occur
ava.lang.IllegalAccessException: class org.apache.tomcat.util.buf.ByteBufferUtils cannot access class jdk.internal.ref.Cleaner (in module java.base) because module java.base does not export jdk.internal.ref to unnamed module @10bdf5e5
                at java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)     
                at java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
                at java.base/java.lang.reflect.Method.invoke(Method.java:558)
                at org.apache.tomcat.util.buf.ByteBufferUtils.<clinit>(ByteBufferUtils.java:49)
                at org.apache.tomcat.util.net.SocketBufferHandler.expand(SocketBufferHandler.java:155)
                at org.apache.tomcat.util.net.SecureNioChannel.processSNI(SecureNioChannel.java:320)
                at org.apache.tomcat.util.net.SecureNioChannel.handshake(SecureNioChannel.java:174)
                at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1387)
                at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
                at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
                at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
                at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
                  at java.base/java.lang.Thread.run(Thread.java:834)

Environment

CA Service Desk Manager 17.2

Resolution

The messages are harmless. No problems will be caused by the messages and they can be safely ignored.