Direct links to fixes
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 number
JR51633
Reported component name
BPM STANDARD
Reported component ID
5725C9500
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-10-28
Closed date
2014-12-11
Last modified date
2014-12-11
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
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
16 October 2021