PM12230: FRIENDLY URL FAILS AFTER CREATING RESOURCE TWICE.

APAR status

• Closed as program error.

Error description

• When a friendly name is re-used on a resource that has been
  deleted shortly before and then re-created, WebSphere Portal
  fails to resolve the friendly name and shows an error:
  
  Error 400: EJCBD0006E: The resolution of a URI failed. Refer to
  the stack trace for more detailed information.
  
  Likewise, the following exception occurs in the traces:
  
  ... ResolvedPrepr 2
  com.ibm.wps.resolver.portal.ResolvedPreprocessor
  handleResolution State
  after resolution: [<?xml version="1.0" encoding="UTF-8"?>
  
  ]
  ... ResolvedPrepr 2
  com.ibm.wps.resolver.portal.ResolvedPreprocessor process The
  resolution process failed.
  
  com.ibm.wps.resolver.impl.exceptions.ModelResolverException:
  EJPEG0111E:
  An unexpected exception has been caught.
  at com.ibm.wps.resolver.friendly.cor.FriendlyResolver
  .resolve(FriendlyResolver.java:287)
  at com.ibm.portal.resolver.helper.CORResolutionService
  .resolve(CORResolutionService.java:113)
  at com.ibm.wps.resolver.portal.ResolvedPreprocessor
  .resolve(ResolvedPreprocessor.java:953)
  at com.ibm.wps.resolver.portal.ResolvedPreprocessor
  .handleResolution(ResolvedPreprocessor.java:447)
  at com.ibm.wps.resolver.friendly.preprocessors
  .FriendlyPreProcessor.handleResolution(FriendlyPreProcessor
  .java:178)
  at ...
  
  Caused by: com.ibm.wps.model.exceptions
  .NlsDataException:EJPEG0111E: An
  unexpected exception has been caught.
  
  ...
  
  Caused by: com.ibm.wps.ac.ResourceNotFoundException:
  EJPSB0002E:
  
  Exception occurred while loading the resource with ObjectID
  [ObjectIDImpl '6_18M131M41OVQ60IS1J3O8Q1822', CONTENT_NODE, VP:
  0,
  [Domain: comm], DB: 0000-01D9308225017F6D80E4610E8C744042].
  at com.ibm.wps.ac.impl.ResourceManagerDataAccess
  .loadResourceByExternalID(ResourceManagerDataAccess.java:238)
  at com.ibm.wps.ac.impl.ResourceManagerDataAccess
  .getResourceByExternalID(ResourceManagerDataAccess.java:268)
  at com.ibm.wps.ac.impl.ResourceManager
  .getParentResourceByExternalChildID(ResourceManager.java:1019)
  at com.ibm.wps.ac.impl.ApplicationAwareFullEntitlementsEngine
  .checkForContentNode(ApplicationAwareFullEntitlementsEngine
  .java:383)
  at com.ibm.wps.ac.impl.ApplicationAwareFullEntitlementsEngine
  .setContext(ApplicationAwareFullEntitlementsEngine.java:322)
  at com.ibm.wps.ac.impl.ApplicationAwareFullEntitlementsEngine
  .checkParentPath(ApplicationAwareFullEntitlementsEngine
  .java:237)
  at com.ibm.wps.ac.impl.PermissionCollectionHelper
  .filterResources(PermissionCollectionHelper.java:242)
  at com.ibm.wps.ac.impl.AccessControlImpl
  .filterResources(AccessControlImpl.java:166)
  at com.ibm.wps.ac.impl.AccessControlFederator
  .filterResources(AccessControlFederator.java:954)
  at com.ibm.wps.model.content.impl.ContentModelImpl
  .findChildrenIDsByMetaData(ContentModelImpl.java:2511)
  

Local fix

Problem summary

• When a friendly name is re-used on a resource that has been
  deleted shortly before and then re-created, WebSphere Portal
  fails to resolve the friendly name and shows an error:
  
    Error 400: EJCBD0006E: The resolution of a URI failed. Refer
  to the stack trace for more detailed information.
  
  Accordingly, the following exception occurs in the traces:
  
    [3/24/10 13:54:37:062 EDT] 000000df ResolvedPrepr 2
  com.ibm.wps.resolver.portal.ResolvedPreprocessor
  handleResolution State after resolution: [<?xml version="1.0"
  encoding="UTF-8"?>]
    [3/24/10 13:54:37:062 EDT] 000000df ResolvedPrepr 2
  com.ibm.wps.resolver.portal.ResolvedPreprocessor process The
  resolution process failed.
    com.ibm.wps.resolver.impl.exceptions.ModelResolverException:
  EJPEG0111E: An unexpected exception has been caught.
    at
  com.ibm.wps.resolver.friendly.cor.FriendlyResolver.resolve(Frien
  dlyResolver.java:287)
    at
  com.ibm.portal.resolver.helper.CORResolutionService.resolve(CORR
  esolutionService.java:113)
    at
  com.ibm.wps.resolver.portal.ResolvedPreprocessor.resolve(Resolve
  dPreprocessor.java:953)
    at
  com.ibm.wps.resolver.portal.ResolvedPreprocessor.handleResolutio
  n(ResolvedPreprocessor.java:447)
    at
  com.ibm.wps.resolver.friendly.preprocessors.FriendlyPreProcessor
  .handleResolution(FriendlyPreProcessor.java:178)
    at ...
  
    Caused by:
  com.ibm.wps.model.exceptions.NlsDataException:EJPEG0111E: An
  unexpected exception has been caught.  ...
  
    Caused by: com.ibm.wps.ac.ResourceNotFoundException:
  EJPSB0002E: Exception occurred while loading the resource with
  ObjectID [ObjectIDImpl '6_18M131M41OVQ60IS1J3O8Q1822',
  CONTENT_NODE, VP: 0, [Domain: comm], DB:
  0000-01D9308225017F6D80E4610E8C744042].
    at
  com.ibm.wps.ac.impl.ResourceManagerDataAccess.loadResourceByExte
  rnalID(ResourceManagerDataAccess.java:238)
    at
  com.ibm.wps.ac.impl.ResourceManagerDataAccess.getResourceByExter
  nalID(ResourceManagerDataAccess.java:268)
    at
  com.ibm.wps.ac.impl.ResourceManager.getParentResourceByExternalC
  hildID(ResourceManager.java:1019)
    at
  com.ibm.wps.ac.impl.ApplicationAwareFullEntitlementsEngine.check
  ForContentNode(ApplicationAwareFullEntitlementsEngine.java:383)
    at
  com.ibm.wps.ac.impl.ApplicationAwareFullEntitlementsEngine.setCo
  ntext(ApplicationAwareFullEntitlementsEngine.java:322)
    at
  com.ibm.wps.ac.impl.ApplicationAwareFullEntitlementsEngine.check
  ParentPath(ApplicationAwareFullEntitlementsEngine.java:237)
    at
  com.ibm.wps.ac.impl.PermissionCollectionHelper.filterResources(P
  ermissionCollectionHelper.java:242)
    at
  com.ibm.wps.ac.impl.AccessControlImpl.filterResources(AccessCont
  rolImpl.java:166)
    at
  com.ibm.wps.ac.impl.AccessControlFederator.filterResources(Acces
  sControlFederator.java:954)
    at
  com.ibm.wps.model.content.impl.ContentModelImpl.findChildrenIDsB
  yMetaData(ContentModelImpl.java:2511)
  

Problem conclusion

• The problem is caused by the fact that with lazy page
  deletion enabled (= default), there are actually two pages with
  the same friendly name in the database. However, one is already
  deregistered in PAC, but if wrongly configured PAC will throw an
  exception for, rather than ignore, resources already deleted.
  
  Failing Module(s):
     Portal Access Control
  
  Affected Users:
     All Users
  
  Version Information:
     Portal Version(s): 6.1.0.3
      Pre-Requisite(s): ---
       Co-Requisite(s): ---
  
  Manuel Steps:
     None
  
  Platform Specific:
     This fix applies to all platforms.
  
  PM12230 is part of Cumulative Fix 04 for Portal 6.1.0.3 /
  6.1.5.0.
  
  The Cumulative Fix is available on Fix Central:
  
  http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
  r?apar=PM11273&productid=WebSphere%20Portal&brandid=5
  

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

• R61C PSY

     UP