JR51633: YOU RECEIVE THE ¢â‚¬ “SOAPSECURITYEXCEPTION: THE MESSAGE IS EXPIRED ¢â‚¬ ERROR WHEN

8.0.1.3-WS-BPM-IFJR51633
8.0.1.2-WS-BPM-IFJR51633
Version 8.5 Refresh Pack 6 for the IBM Business Process Manager products
Version 8.5.0 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• When you use web service integration with a security header in
  the response, you might receive  the following exception:
  
  com.ibm.wsspi.wssecurity.core.SoapSecurityException: the
  message is expired, the expire time is <TimeStamp> but the
  time now is <TimeStamp>
   at
  com.ibm.bpm.server.webservices.security.BPMWSSecurityHandler.tim
  estampConsume(BPMWSSecurityHandler.java:348)
  
   at
  com.ibm.bpm.server.webservices.security.BPMWSSecurityHandler.inv
  oke(BPMWSSecurityHandler.java:170)
  
  
  However, after comparing the time stamp, you notice that the
  message hasn't expired yet. Then, you might see this exception
  for multi-threading issue.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM Business Process Manager (BPM)          *
  *                  Standard                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  *                      When you use web service integration    *
  *                      with a security header in               *
  *                      the response, you might receive  the    *
  *                      following exception:                    *
  *                      com.ibm.wsspi.wssecurity.core.SoapSecur *
  *                      ityException: the                       *
  *                      message is expired, the expire time     *
  *                      is <TimeStamp> but the                  *
  *                      time now is <TimeStamp>                 *
  *                      at                                      *
  *                      com.ibm.bpm.server.webservices.security *
  *                      .BPMWSSecurityHandler.tim               *
  *                      estampConsume(BPMWSSecurityHandler.java *
  *                      :348)                                   *
  *                      at                                      *
  *                      com.ibm.bpm.server.webservices.security *
  *                      .BPMWSSecurityHandler.inv               *
  *                      oke(BPMWSSecurityHandler.java:170)      *
  *                      However, after comparing the time       *
  *                      stamp, you notice that the              *
  *                      message hasn't expired yet. Then, you   *
  *                      might see this exception                *
  *                      for multi-threading issue.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This issue is caused by multi-threading. The time stamp in the
  security token is parsed according to a certain format.
  However, if the parsing processes are issued in multiple
  threads, the result received is wrong and you receive the
  exception about the token being expired.
  

Problem conclusion

• A fix is available for IBM BPM V8.0.1.2 to fix the token
  expiry in multi-thread issue.
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR51633:
  
  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 APAR or SPR, enter JR51633, and click Continue.
  
  When you download fix packages, ensure that you also download
  the readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  

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

• R800 PSY

     UP