PM80511: DASHBOARD ENVIRONMENT IS STUCK ON THE SPLASH SCREEN

APAR status

• Closed as program error.

Error description

• When developing a new application with Worklight Studio, if a
  Dashboard environment is added, trying to run it will result in
  a the application being hung on the initial splash screen.
  Nothing appears in the Worklight Studio console.
  

Local fix

• There is currently no work around for this issue.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Any user with an application including a    *
  *                  Dashboard environment which tries to        *
  *                  connect to the Worklight Server.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: While there aren't any error messages   *
  *                      in the Worklight Studio console, the    *
  *                      following network activity can be       *
  *                      seen using network tools like           *
  *                      Wireshark.  These messages appear       *
  *                      several times.                          *
  *                      110818 46.947775000 9.xx.xx.xx          *
  *                      9.xx.xx.xx HTTP 121 POST                *
  *                      /apps/services/api/nell/dashboard/init  *
  *                      HTTP/1.1                                *
  *                      (application/x-www-form-urlenco         *
  *                      ded)                                    *
  *                      110821 46.948107000 9.xx.xx.xx          *
  *                      9.xx.xx.xx HTTP 862 HTTP/1.1 401        *
  *                      Unauthorized (application/json)         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The issue is due to a regression in the challenge handling
  mechanism.  The network traffic noted in the problem
  description illustrates the failed interaction.
  

Problem conclusion

• The code was modified to restore session cookie management to
  the Dashboard environment.
  
  The fix for this APAR is currently targetted for inclusion in
  fixpack 5.0.5.0.
  

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

  MOBILE FNDTN EN

• Fixed component ID

  5725G9200

Applicable component levels

• R500 PSY

     UP