IBM Support

PH21708: UCD SERVER LOGS FLOODED BY TOMCAT NPE ERRORS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • If you upgrade to 7.0.5.0, you will notice that the server logs
    are being flooded by NullPointerExceptions. This is a known
    issue of the Tomcat version that is shipped with 7.0.5.0.
    
    2019-12-18 18:33:06,200 IST ERROR
    https-jsse-nio-0.0.0.0-8443-exec-4
    org.apache.coyote.http11.Http11NioProtocol - Error reading
    request, ignored
    java.lang.NullPointerException
    	at
    org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.getSslSu
    pport(NioEndpoint.java:1415)
    	at
    org.apache.coyote.AbstractProtocol$ConnectionHandler.process(Abs
    tractProtocol.java:802)
    	at
    org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(Nio
    Endpoint.java:1504)
    	at
    org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcess
    orBase.java:49)
    	at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
    utor.java:1142)
    	at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
    cutor.java:617)
    	at
    org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(T
    askThread.java:61)
    	at java.lang.Thread.run(Thread.java:745)
    

Local fix

  • NA, need to upgrade tomcat version with fix pack
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All end users on all supported browsers.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If you upgrade to 7.0.5.0, you will notice that the server   *
    * logs                                                         *
    * are being flooded by NullPointerExceptions. This is a known  *
    * issue of the Tomcat version that is shipped with 7.0.5.0.    *
    *                                                              *
    * 2019-12-18 18:33:06,200 IST ERROR                            *
    * https-jsse-nio-0.0.0.0-8443-exec-4                           *
    * org.apache.coyote.http11.Http11NioProtocol - Error reading   *
    * request, ignored                                             *
    * java.lang.NullPointerException                               *
    * 	at                                                          *
    * org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.getS *
    * slSu                                                         *
    * pport(NioEndpoint.java:1415)                                 *
    * 	at                                                          *
    * org.apache.coyote.AbstractProtocol$ConnectionHandler.process *
    * (Abs                                                         *
    * tractProtocol.java:802)                                      *
    * 	at                                                          *
    * org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun *
    * (Nio                                                         *
    * Endpoint.java:1504)                                          *
    * 	at                                                          *
    * org.apache.tomcat.util.net.SocketProcessorBase.run(SocketPro *
    * cess                                                         *
    * orBase.java:49)                                              *
    * 	at                                                          *
    * java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool *
    * Exec                                                         *
    * utor.java:1142)                                              *
    * 	at                                                          *
    * java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo *
    * lExe                                                         *
    * cutor.java:617)                                              *
    * 	at                                                          *
    * org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.r *
    * un(T                                                         *
    * askThread.java:61)                                           *
    * 	at java.lang.Thread.run(Thread.java:745)                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fixed in version 7.0.5.1                                     *
    ****************************************************************
    

Problem conclusion

  • Fix is provided in IBM UrbanCode Deploy 7.0.5.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH21708

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    705

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-02-03

  • Closed date

    2020-02-12

  • Last modified date

    2020-02-12

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels



Document information

More support for: IBM UrbanCode Deploy

Software version: 705

Reference #: PH21708

Modified date: 12 February 2020