JR55646: YOU MIGHT RECEIVE A LOCKTIMEOUT EXCEPTION WHEN YOU USE MICROSOFT SQL SERVER

bpm.8570.cf2016.06.delta.repository.2of2
bpm.8570.cf2016.06.delta.repository.1of2

APAR status

• Closed as fixed if next.

Error description

• In a Microsoft SQL server environment that has a multi-member
  AppTarget cluster, the event manager might throw a LockTimeout
  exception like the following exception:
  
  CWLLG0579E: An exception occurred while trying to acquire a
  synchronous queue.
  com.lombardisoftware.core.TeamWorksException: Lock request time
  out period exceeded.
   at
  com.lombardisoftware.core.TeamWorksException.asTeamWorksExceptio
  n(TeamWorksException.java:136)
   at
  com.lombardisoftware.utility.db.DbUtils$1.doInTransaction(DbUtil
  s.java:105)
   at
  com.lombardisoftware.server.core.TXCommand$3.call(TXCommand.java
  :93)
   at
  com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
  rt$3.doInTransaction(ProgrammaticTransaction Support.java:500)
   at
  org.springframework.transaction.jta.WebSphereUowTransactionManag
  er$UOWActionAdapter.run(WebSphereUow
  TransactionManager.java:306)
   at
  com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderNewUO
  W(EmbeddableUOWManagerImpl.java: 791)
   at
  com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.runUnderUOW(E
  mbeddableUOWManagerImpl.java:370)
   at
  org.springframework.transaction.jta.WebSphereUowTransactionManag
  er.execute(WebSphereUowTransactionManager. Java:252)
   at
  com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
  rt.executeInNewTransaction(ProgrammaticTransacti
  onSupport.java:488)
   at
  com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
  rt.execute(ProgrammaticTransactionSupport.java:349)
   at
  com.lombardisoftware.server.core.TXCommand.executeInDeadlockRetr
  yLoop(TXCommand.java:91)
   at
  com.lombardisoftware.utility.db.DbUtils.executeInTransaction(DbU
  tils.java:100)
   at
  com.lombardisoftware.server.scheduler.TaskLoader.acquireSyncQueu
  e(TaskLoader.java:811)
   at
  com.lombardisoftware.server.scheduler.TaskLoader.run(TaskLoader.
  java:581)
   at
  com.lombardisoftware.client.delegate.common.WebsphereDelegateHel
  per$3$1.run(WebsphereDelegateHelper.java:107)
   at
  java.security.AccessController.doPrivileged(AccessController.jav
  a...
  

Local fix

• In the 60Database.xml file, locate the SELECT statement of the
  <loader-find-sync-queue-query> tag to look like this:
  
     <loader-find-sync-queue-query>
        SELECT TOP 1 SYNC_QUEUE_ID, DESCRIPTION
        FROM LSW_UCA_SYNC_QUEUE WITH (ROWLOCK,UPDLOCK,READPAST)
        WHERE QUEUE_OWNER IS NULL OR QUEUE_OWNER NOT IN  (%alive%)
        ORDER BY SYNC_QUEUE_ID
    </loader-find-sync-queue-query>
  
  For information about the 60Database.xml file, see ?The
  99Local.xml and 100Custom.xml configuration files)
  (http://www.ibm.com/support/knowledgecenter/SSFPJS_8.5.6/com.ibm
  .wbpm.admin.doc/topics/managing_twks_config_settings.html?lang=e
  n).
  
  Although this topic warns you not to change the 60Database.xml,
  to apply a local fix you must change the 60Database.xml file.
  

Problem summary

• The problem occurs when three or more cluster members try to
  access the same set of event manager tasks: the first event
  manager locks them and the others wait for the locks to be
  released. If the other cluster members wait longer than the lock
   timeout interval specifies, the exception is thrown.
  
  PROBLEM CONCLUSION -
  This issue will be corrected in an upcoming IBM BPM V8.5
  cumulative fix.
  
  To determine whether the cumulative fix is available and
  download it if it is, complete the following steps on Fix
  Central:
  
  1. Select IBM Business Process Manager with your edition from
  the product selector, the installed version to the fix pack
  level, and your platform, and then click Continue.
  2. Select Text, enter ?cumulative fix?, and click Continue.
  

Problem conclusion

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

  BPM STANDARD

• Fixed component ID

  5725C9500

Applicable component levels

• R857 PSY

     UP