PI42575: MIGRATE WORKLIGHT 6.2 TO MFPF V7 WITH TOMCAT SERVER FARM WILL FAIL

IBM MobileFirst Platform Foundation Interim Fix README for 7.0

APAR status

• Closed as program error.

Error description

• Trying to migrate Worklight 6.2 to MobileFirst V7 with Tomcat
  server farm
   will cause the deployed application to not be displayed in the
  MobileFirst Platform Operations
  console.
  There will be no problem to log-in to the MobileFirst Platform
  Operations Console, but after log in
  the following message will appear:
  "No runtime environment deployed in this server".
  The error message in the server log:
  com.ibm.worklight.admin.jmx.
  ManagementMXBeanImpl registerFarmMember
  SEVERE: Farm member registering failed for node with server ID
  "....." for runtime ".....".
  
  Worklight Versions Affected:
  7.0
  
  Initial Impact:
  low
  

Local fix

• no local fix provided
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MobileFirst Platform console users                           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When the runtime starts in a Tomcat of a server farm using   *
  * Oracle the runtime fails to register in the administration   *
  * database with the following exception :                      *
  *                                                              *
  * com.ibm.worklight.admin.jmx.ManagementMXBeanImpl             *
  * registerFarmMember                                           *
  * SEVERE: Farm member registering failed for node with server  *
  * ID <server> for runtime <runtime>                            *
  *                                                              *
  * This is caused by the following openjpa exception :          *
  *                                                              *
  * org.apache.openjpa.persistence.PersistenceException:         *
  * oracle.sql.BLOB                                              *
  *                                                              *
  * FailedObject: prepstmnt 7926055 INSERT INTO FARM_CONFIG      *
  * (PROJECT_NAME, SERVERID, ADMIN_PWD, ADMIN_USER, APPSERVER,   *
  * HEARTBEAT_TIME, HOSTNAME, PORT, STATUS, TOMCAT_PORT)         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * -                                                            *
  ****************************************************************
  

Problem conclusion

• The issue was due to an openjpa defect with Oracle where
  inserting a lob column with a null value fails. The ADMIN_PWD
  column is of type BLOB and  "none" is now inserted during the
  runtime registration.
  

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

• R700 PSY

     UP