IJ45639: APAR - 7.6.1.3 - TYPE 'COM/IBM/TIVOLI/MAXIMO/IOTF/FLDIOTMAPPINGPROPERTY' (CURRENT FRAME, STACK[0]) IS NOT ASSIGNABLE TO 'COM/IBM

APAR status

• Closed as program error.

Error description

• User is not able to login to Maximo after upgrading from 7612 to
  7613. Getting below error on SystemOut:
  
  [2/27/23 9:00:39:939 EST] 00000075 ServletWrappe E
  com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0271E:
  Uncaught init() exception created by servlet
  [MAXIMOStartupServlet] in application [MAXIMOUI]:
  java.lang.VerifyError: JVMVRFY041 invokespecial of wrong
  initializer;
  class=com/ibm/tivoli/maximo/iotservices/FldIoTMappingProperty,
  method=<init>(Lpsdi/mbo/MboValue;)V, pc=2
  Exception Details:
   Location:
     com/ibm/tivoli/maximo/iotservices/FldIoTMappingProperty.<ini
  t>(Lpsdi/mbo/MboValue;)V@2: JBinvokespecial
   Reason:
     Type 'com/ibm/tivoli/maximo/iotf/FldIoTMappingProperty'
  (current frame, stack[0]) is not assignable to
  'com/ibm/tivoli/maximo/iotservices/FldIoTMappingProperty'
   Current Frame:
     bci: @2
     flags: { flagThisUninit }
     locals: { 'uninitializedThis', 'psdi/mbo/MboValue' }
     stack: { 'com/ibm/tivoli/maximo/iotf/FldIoTMappingProperty' }
  
  	at java.lang.Class.forNameImpl(Native Method)
  	at java.lang.Class.forName(Class.java:297)
  	at psdi.mbo.MboValueInfo.getCustomClass(MboValueInfo.java:197)
  	at psdi.mbo.Mbo.generateMboValueInstance(Mbo.java:912)
  	at psdi.mbo.Mbo.getMboValue(Mbo.java:1192)
  	at psdi.mbo.Mbo.isNull(Mbo.java:3167)
  	at psdi.app.signature.MaxUser.init(MaxUser.java:303)
  	at psdi.mbo.Mbo.initialize(Mbo.java:1017)
  	at psdi.mbo.MboSet.generateMboInstance(MboSet.java:2291)
  	at psdi.mbo.MboSet.fetchMbosActual(MboSet.java:2980)
  	at psdi.mbo.MboSet.fetchMbos(MboSet.java:2910)
  	at psdi.mbo.MboSet.getMbo(MboSet.java:2126)
  	at psdi.mbo.MboSet.isEmpty(MboSet.java:4422)
  	at psdi.security.SecurityService.getUserMbo(SecurityService.ja
  va:2437)
  	at psdi.security.SecurityService.getUserInfo(SecurityService.j
  ava:2368)
  	at psdi.security.SecurityService.getSystemUserInfo(SecuritySer
  vice.java:3163)
  	at psdi.security.SecurityService.authenticateUserM(SecuritySer
  vice.java:2116)
  	at psdi.security.SecurityService.authenticateUser(SecurityServ
  ice.java:2084)
  	at psdi.iface.util.SecurityUtil.getNewUserInfo(SecurityUtil.ja
  va:212)
  	at psdi.util.logging.LoggingService$LogUploadReqMonitor.<init>
  (LoggingService.java:359)
  	at
  psdi.util.logging.LoggingService.init(LoggingService.java:103)
  	at
  psdi.server.ServiceCoordinator.init(ServiceCoordinator.java:154)
  
  	at psdi.server.MXServer.init(MXServer.java:2724)
  	at psdi.server.MXServer.start(MXServer.java:3870)
  	at psdi.servlet.MAXIMOStartupServlet.init(MAXIMOStartupServlet
  .java:116)
  
  
  Work around:
  To follow document
  https://www.ibm.com/support/pages/node/6618875. But after using
  this workaround, whenever user will run updatedb again, this
  error on SystemOut and the login issue can be seen again.
  
  REPORTED IN VERSION:
  Maximo 7.6.1.2
  

Local fix

• To follow document
  https://www.ibm.com/support/pages/node/6618875
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * See this technote                                            *
  * https://www.ibm.com/support/pages/node/6618875               *
  ****************************************************************
  

Problem conclusion

• A fix for this APAR will be included in a future release.
  

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

  MAXIMO SYSTEMS

• Fixed component ID

  5724R46AV

Applicable component levels