PM28568: XMLACCESS EXPORTS FAIL IN THE PRESENCE OF ORPHANED PORTLET INSTA NCES.

APAR status

• Closed as program error.

Error description

• XMLAccess exports fail in the presence of orphaned portlet
  instances, that point to portlet definitions that have been
  deleted. The SLChecker tool cannot be used to resolve the
  situation, as also the export including orphaned data (required
  for the initial SLCheckerTool input) is affected by the
  failure.
  
  The SystemOut.log shows an exception similar to the one below:
  ----
  [12/3/10 0:58:49:134 CET] 00000032 Engine        E
  com.ibm.wps.command.xml.Engine processSax EJPFB0002E: Exception
  occurred.
  
  com.ibm.wps.command.xml.XmlCommandException: EJPXA0001E: An
  error occurred while processing the XML configuration request.
  [wsrp-customized-portletinstance Z5_MLSU3F540GVO70I6L0QIH1ADE6]
  at com.ibm.wps.command.xml.items.PortletInstanceItem
  .load(PortletInstanceItem.java:443)
  at com.ibm.wps.command.xml.ExportEngine.loadItem(ExportEngine
  .java:555)
  at com.ibm.wps.command.xml.ExportEngine.loadItem(ExportEngine
  .java:624)
  at com.ibm.wps.command.xml.ExportEngine
  .exportPortal(ExportEngine.java:132)
  ..
  at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1563)
  Caused by: com.ibm.wps.pe.om.common.ResourceDeletedException:
  No
  portlet definition found for PortletEntity:
  PortletInstance: com.ibm.wps.datastore.impl
  .PortletInstanceImpl@1d23de88
  objectID: [ObjectIDImpl 'Z5_MLSU3F540GVO70I6L0QIH1ADE6',
  PORTLET_ENTITY, VP: 0, [Domain: comm], DB:
  0000-B6723F5E21007E7C8034156819836ACE]
  created: 1291333834474
  lastModified: 1291333834474
  sessionScopeObjectID: [ObjectIDImpl
  'Z5_MLSU3F540GVO70I6L0QIH1ADE6', PORTLET_ENTITY, VP: 0,
  [Domain:
  comm], DB: 0000-B6723F5E21007E7C8034156819836ACE]
  portletDescriptorObjectID: [ObjectIDImpl
  'Z3_MLSU3F540GVO70I6L0QIH127A0', PORTLET_DEFINITION, VP: 0,
  [Domain: rel], DB: 0000-B6723F5E21007E7C803415681983380A]
  wscInstanceHandle: null
  wspIsProvided: true
  wspIsProducerOfferedInstance: false
  parentObjectID: <null>
  preferencesScopeID: <null>
  validationBase: -1831420378
  validationState: true
  jsrData: true
  isPoolInstance: false
  preferences: {preference_EditPreferenceEventType
  .highlighted=[modifiable: true, dbvalue:
  value_EditPreferenceEventType.highlighted, jsrvalue: null]}
  
  at com.ibm.wps.pe.om.entity.impl.PortletEntityImpl
  .getPortletDefinition(PortletEntityImpl.java:152)
  at com.ibm.wps.pe.factory.om.impl.ActionProviderFactoryImpl
  .getSD(ActionProviderFactoryImpl.java:85)
  at com.ibm.wps.pe.factory.om.impl.ActionProviderFactoryImpl
  .getEndpointProvider(ActionProviderFactoryImpl.java:168)
  at com.ibm.wps.pe.om.common.impl.CommunicationEndpointsImpl
  .<init>(CommunicationEndpointsImpl.java:48)
  at com.ibm.wps.pe.om.entity.impl.PortletEntityImpl
  .getCommunicationEndpointLayer(PortletEntityImpl.java:187)
  at com.ibm.wps.command.xml.items.PortletInstanceItem
  .loadPortletDynamicEvents(PortletInstanceItem.java:1351)
  at com.ibm.wps.command.xml.items.PortletInstanceItem
  .load(PortletInstanceItem.java:441)
  ... 35 more
  ----
  

Local fix

• Improved code robustness to enable handling of orphaned portlet
  instances.
  

Problem summary

• XMLAccess exports fail in the presence of orphaned portlet
  instances, that point to portlet definitions that have been
  deleted. The SLChecker tool cannot be used to resolve the
  situation, as also the export including orphaned data (required
  for the initial SLCheckerTool input) is affected by the
  failure.
  

Problem conclusion

• PM28568 is included in WebSphere Portal Version 7.0.0.1.
  

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

  WEBSPHERE PORTA

• Fixed component ID

  5724E7600

Applicable component levels

• R700 PSY

     UP