IJ31176: MMI CALLS TO REMOTE SERVERS FAIL WITH SERIALIZATION ERROR FOR WEBLOGIC

APAR status

• Closed as program error.

Error description

• ERROR DESCRIPTION: for weblogic - MMI calls to remote servers
  fail with serialization error
  PROBLEM: When configuring the Work center in a weblogic
  environment, the customer receives the error below.:
  SystemOut.log:
  17 Nov 2020 11:25:15:007 [ERROR] [Mx761TstUIServer1]
  [CID-MXOSLC-30099] error marshalling arguments; nested
  exception is:
   java.io.NotSerializableException:
  weblogic.utils.collections.ArrayMap
  java.rmi.MarshalException: error marshalling arguments; nested
  exception is:
   java.io.NotSerializableException:
  weblogic.utils.collections.ArrayMap
   at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:157)
  
  Browser trace:
  GET
  /MaxiTst/oslc/members/MTAuMS4yNTIuMjAyOjEzNDAwL014NzYxVHN0SUZTZX
  J2ZXIx HTTP/1.1
  Host: thallium.domain1.chelan:7183
  Connection: keep-alive
  accept: application/json
  User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64)
  AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.150
  Safari/537.36
  Referer: http://thallium.domain1.chelan:7183/MaxiTst-x/
  Accept-Encoding: gzip, deflate
  Accept-Language: en-US,en;q=0.9
  Cookie:
  JSESSIONID=BsyNPNktYOFYCVnNmOpop-yyctxGLXj4TnX9E2g-kGe9KC1mL31y!
  578791675
  HTTP/1.1 500 Internal Server Error
  Date: Wed, 10 Feb 2021 18:38:52 GMT
  Content-Type: application/json
  X-Frame-Options: SAMEORIGIN
  X-XSS-Protection: 1
  X-Content-Type-Options: nosniff
  Content-Length: 184
  {"Error":{"reasonCode":null,"message":"error marshalling
  arguments; nested exception is:
  \n\tjava.io.NotSerializableException:
  weblogic.utils.collections.ArrayMap","statusCode":"500"}}
  EXPECTED RESULT: Do not get the error in Weblogic environments
  ENVIRONMENT (SYSTEM INFO):
  App Server Weblogic Application Server 12.2.1.3.0
  Version
  Tivoli's process automation engine 7.6.1.1-IFIX20200522-1523
  Build 20190514-1348 DB Build V7611-365 HFDB Build HF7611-13
  IBM Maximo Asset Management Work Centers 7.6.0.4 Build $build$
  DB Build V7604-119
  IBM Maximo Asset Management Scheduler 7.6.7.3 Build
  20190514-1348 DB Build V7673-78 HFDB Build HF7673-12
  IBM Tpae Integration Framework
  7.6.1.1-MIF_7611_IFIX.20200504-1653 Build 20190422-1259 DB
  Build V7611-01
  IBM Maximo for Utilities 7.6.0.2-20200522-1028 Build
  20171128-1353 DB Build V7602-68 HFDB Build HF7602-13
  IBM Maximo Spatial Asset Management 7.6.0.5-20200525-1808 Build
  20190522-1410 DB Build V7605-09 HFDB Build HF7605-07
  IBM Maximo Asset Management 7.6.1.1 Build 20190514-1348 DB
  Build V7611-01
  IoT Connection Utility 7.6.0.2 Build 20190426-2206 DB Build
  V7602-07
  Server OS Linux 3.8.13-118.19.4.el7uek.x86_64
  Server DB Oracle 19.0 (Oracle Database 19c Enterprise Edition
  Release 19.0.0.0.0 - Production Version 19.9.0.0.0)
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following
  maintenancepackage:
  Release 7.6.1.3 of Base Services
  

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

  SYSTEM PERFORMA

• Fixed component ID

  5724R46PF

Applicable component levels