Composite Failing With WSM-00254 : The Message Is Expired. Check The Timestamp Element In The Message in Prod server but not in Dev server
(Doc ID 2520140.1)
Last updated on NOVEMBER 15, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.3.0 version, Workflow Service Engine
(Gathering more info...)
Composite failing with WSM-00254 : The message is expired. Check the timestamp element in the message
There were no changes to server configuration and client application also not seeing navigation to setup
"agent.clock.skew" and "agent.expire.time" this issue is in WLS 12.2.1.3 instance
This issue is impacting all integrations in PROD environment
ERROR
-----------------------
WSM-00254 : The message is expired. Check the timestamp element in the message
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Prod Oracle Linux server's system time is 6 - 7 minutes slower than the Dev Oracle Linux server's system time which is exactly the real time of day.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot run the composite on Prod server but it's working fine on Dev server.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |