java.lang.OutOfMemoryError After Multiple Re-Deployments

(Doc ID 1328844.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle SOA Platform - Version: and later   [Release: 11gR1 and later ]
Information in this document applies to any platform.


Redeploying SOA composite multiple times (with same name and version) in a continous loop leads to java.lang.OutOfMemoryError

Following steps were used to reproduce the problem:

  1. Deploy composite
  2. Call the composite using wget
  3. Redeploy the composite with the same name and version

The problem happens after around 270th redepoyment

Previously, the Out Of Memory (OOM) error was happening just by continously redeploying the composite. The error was fixed by applying 3 patches mentioned in <Document 1236484.1>. However, calling the composite between the deployments seems leads to java.lang.OutOfMemoryError again.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms