PI36182: TOMCAT FAILED TO START WITH MOBILEFIRST RUNTIME IS DEPLOYED ON LINUX

IBM MobileFirst Platform Foundation Interim Fix README for 6.3

APAR status

• Closed as program error.

Error description

• On some Linux machine, Tomcat failed to start when MobileFirst
  runtime is deployed.  The problem is on certain Linux, the HTTP
  protocol is not available when Tomcat started.  And with the
  latest Apache HTTP client 4.3, there is no socket timeout hence
  Tomcat is waiting infinitely.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Mobile First Platform running on Tomcat                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When defining a MobileFirst Platform runtime in a Tomcat     *
  * server, the server hangs during the startup and never starts *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• When the runtime starts it needs to send a http ping request to
  check that the admin services is available. If the admin
  services is not available, the runtime retries every 2s the ping
  request during 2 mns. After 2 mns if still not successful an
  exception is emitted by the runtime.
   When the first http ping request is sent Tomcat can have not
  yet initialized the http protocol. As the default timeout is
  infinite, the http request never returns, the thread is waiting
  infinitely and so Tomcat is blocked since the Tomcat startup is
  done in sequence and not in parallel.
  The fix sets a timeout of 2 seconds. So if the http protocol is
  not available, there is a timeout error after 2s handled by the
  runtime that will retry every 2s during 2 mns. So the thread is
  no more blocked and Tomcat can continue to start the server.
  When the http protocol is initialized the next ping will
  succeed.
  

Temporary fix

Comments

APAR Information

• 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

  WL/MFPF CONSUME

• Fixed component ID

  5725I4301

Applicable component levels

• R630 PSY

     UP