My Oracle Support Banner

IWS Webservices Sessions Do Not Timeout (Doc ID 2093034.1)

Last updated on MARCH 01, 2019

Applies to:

Oracle Utilities Meter Data Management - Version 2.1.0.2 and later
Information in this document applies to any platform.

Symptoms

**Examples provided in this article do not represent real life personal/confidential information**

**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 2.1.0.2 / Oracle Utilities Application Framework 4.2.0.3 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.

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.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.