My Oracle Support Banner

GET Request To Soap 1.1 Service With WSM Policy Causes Memory Leak (Doc ID 2446475.1)

Last updated on SEPTEMBER 13, 2018

Applies to:

Oracle Service Bus - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

GET request to soap 1.1 service with WSM policy causes memory leak

If client sends http GET request to OSB soap 1.1 service without WSM policy there is no memory leak and client receives html table.

If client sends http GET request to OSB soap 1.1 service with WSM policy appropriate class is added to com.bea.wli.sb.service.disi.handlerchain.handlers.DISIContextInfoStore.disiContextRequestMap and never released and client receives xml error.

ERROR
-----------------------



Changes

 

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
Changes
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.