IWS Webservices Sessions Do Not Timeout
(Doc ID 2093034.1)
Last updated on FEBRUARY 20, 2024
Applies to:Oracle Utilities Meter Data Management - Version 220.127.116.11 and later
Information in this document applies to any platform.
**Disclaimer:** This KM article may include the following abbreviations:
MDM - Oracle Utilities Meter Data Management
OUAF/FW - Oracle Utilities Framework
IWS - Inbound Web Service
In Meter Data Management 18.104.22.168 / Oracle Utilities Application Framework 22.214.171.124 IWS (Internal Web Services) don't really use session and weblogic defaults to keep sessions open for at least 1 hour after being inactive. With webservice calls, this means that weblogic is hanging on to session data for each request for at least 1 hour. In a high load environment, this not only results in increased memory but when the sessions are finally reclaimed, the garbage collector can render the web server unusable for a periods of time.
This can be controlled via two Weblogic session management configuration values.
- Session timeout (timeout-secs) is the amount of time that must elapse before an inactive session can be reclaimed.
- Session invalidation (invalidation-interval-secs) is how frequently weblogic runs the session reclamation code.
Unless the IWS configuration has been manually edited, navigate to Deployments -> Webservices -> Configuration in the Weblogic console and note that the Session Timeout is 3600 seconds.
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