PK96805: XMLACCESS ISSUES ILLEGALSTATEEXCEPTION: TIMEOUT WHILE WAITING FOR READ LOCKS TO BE RELEASED

APAR status

• Closed as program error.

Error description

• The following exceptions are found in the logs when running
  large XMLAccess script on a node that is currently accessed:
  
  Caused by: java.lang.IllegalStateException: Timeout while
  waiting for read locks to be released. Write lock was not
  acquired.
  
  Those exceptions are accompanied by 5 sec wait cycles of the
  XMLAccess process.
  
  The APAR fixes and issue with xmlaccess processing of the
  request parameter synchronous-cache-update (default=false).
  Additionally, two new configuration parameters are introduced
  for the ThreadsafeContentModel class that issues the
  IllegalStateException:
  
  WP ConfigService:
  content.topology.writelock.timeout=<milliseconds>
  (default=25000)
  - This setting controls the maximum wait time to optain a
  writable model before issuing a timeout warning.
  
  content.topology.writelock.dump=true|false (default=false)
  -> This setting controls if a java core dump should be written
  in case of a timeout event for debugging.
  
  Use the WAS admin console - Resource Environment Providers - to
  add or change the settings and restart the Portal Server
  afterwards.
  
  Observed stacktrace:
  
  com.ibm.wps.services.events.ReflectHandler invoke() EJPFD0021E:
  Error while invoking an event handler.
    java.lang.reflect.InvocationTargetException
  Caused by: java.lang.IllegalStateException: Timeout while
  waiting for read locks to be released. Write lock was not
  acquired.
   at
  com.ibm.wps.model.content.impl.ThreadsafeContentModelImpl.writeB
  gin(ThreadsafeContentModelImpl.java:131)
   at
  com.ibm.wps.model.content.impl.ContentModelImpl.invalidate(Conte
  tModelImpl.java:997)
  

Local fix

• A possible workaround is to use the following two request
  attributes for
  xmlaccess:
  transaction-level="none"
  synchronous-cache-update="true"
  

Problem summary

• The following exceptions are found in the logs when running
  large XMLAccess script on a node that is currently accessed:
  
    Caused by: java.lang.IllegalStateException: Timeout while
  waiting for read locks to be released. Write lock was not
  acquired.
  
  Those exceptions are accompanied by 5 sec wait cycles of the
  XMLAccess process.
  

Problem conclusion

• The APAR fixes and issue with xmlaccess processing of the
  request parameter synchronous-cache-update (default=false).
  Additionally, two new configuration parameters are introduced
  for the ThreadsafeContentModel class that issues the
  IllegalStateException:
  
  WP ConfigService:
  content.topology.writelock.timeout=<milliseconds>
  (default=25000)
  content.topology.writelock.dump=true|false (default=false)
  
  Use the WAS admin console - Resource Environment Providers - to
  add or change the settings and restart the Portal Server
  afterwards.
  
  Manual Steps:
     None
  
  Failing Module(s):
     XML Access
  
  Affected Users:
     All Users
  
  Version Information:
      Portal Version(s): 6.1.0.1
       Pre-Requisite(s): PK95161
        Co-Requisite(s): ---
  
      Portal Version(s): 6.1.0.2
       Pre-Requisite(s): PK95161
        Co-Requisite(s): ---
  
  Platform Specific:
     This fix applies to all platforms.
  
  A fix is available from Fix Central:
  
  http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
  ?apar=PK96805&productid=WebSphere%20Portal&brandid=5
  
  You may need to type or paste the complete address into your Web
  browser.
  

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

• R61A PSY

     UP

• R61B PSY

     UP