My Oracle Support Banner

Heavy Deploy / Undeploy or Instance Invocations Trigger Memory Leak and java.lang.OutOfMemory in SOA (Doc ID 1236484.1)

Last updated on AUGUST 09, 2018

Applies to:

Oracle SOA Platform - Version and later
Information in this document applies to any platform.


You have recently adopted Oracle Fusion Middleware and may be using it in a development or test environment, where a large volume of composite deployments and undeployments may be taking place and/or composite instances are being invoked a large number of times between container restarts.

Using java memory tools like Visual Java and JRockit Mission Control to examine memory consumption by the Java heap, you notice that the WebLogic Managed Server running the BPEL process manager is seeing higher than expected levels of memory utilization. The memory utilization shows sustained and continued upward growth and memory used does not fall after periods of inactivity (where it can be confirmed that no deployments/undeployments or instance invocations have taken place) or after a Full GC is invoked.

Intermittently you may also be seeing:

  1. java.lang.OutOfMemory errors, which cause the managed server to fail and need to be restarted.

  2. Deployments of composites (both new deployments and re-deployments) fail with a weblogic.transaction.internal.TimedOutException error:

    Deploying on partition "default" of "/Farm_soa_domain/soa_domain/soa_server1"...
    Deploying on "/Farm_soa_domain/soa_domain/soa_server1" failed!
    Error during deployment: Deployment Failed: Error occurred during deployment of component:
    FulfillCreateProspect to service engine: implementation.bpel for composite: FulfillCreateProspect:
    javax.ejb.EJBException: TransactionRolledback.: weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 20 seconds

    at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(
    at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(
    at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(
    at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(
    at weblogic.transaction.internal.WLSTimer.timerExpired(
    at; nested exception is: weblogic.transaction.internal.TimedOutException:
    Transaction timed out after 20 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!

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