BPEL process OutOfMemory error

Question

Hi,
I have following processes:
Requester (BPEL) > EBS (OSB) > Provider (BPEL)
A large payload request is received by Requester and in Provider I have db adapter calls in a loop and as per business logic it has to perform more than 512 db adapter requests but this provider fails after about 3 mins. Another strange thing is that another BPEL instance also gets automatically instantiated after 3 mins which also fails.  
I get following main exceptions in EM log:
1.
Message transaction status statusSTATUS_ACTIVE
Supplemental Detail java.lang.OutOfMemoryError: allocLargeObjectOrArray: [C, size 9716016
at oracle.soa.common.util.NonSyncStringBuffer.ensureFreeSpace(NonSyncStringBuffer.java:210)
at oracle.soa.common.util.NonSyncStringBuffer.append(NonSyncStringBuffer.java:513)
2.
Thread ID [ACTIVE].ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'
ECID 6cd8828aacee5923:-58ca31b1:1430a4058ba:-8000-000000000010a79e
Message javax.xml.soap.SOAPException: OWS-12042 :read is alrady timed out
Supplemental Detail at oracle.j2ee.ws.saaj.soap.MessageImpl.saveChangesSoapOnly(MessageImpl.java:1187)
I have tested this on both DEV and SIT environments and getting same issue on both servers.

Answer 1

Hi,
The OutOfMerroryError is one that I encountered at my current project several times.
When a large payload is received, it is put in memory once. But when you use this payload in a transformation or assign it is put in memory each time it is used in a copy rule. If this is done in a loop it will put it in memory as many times it is used in the transformation.
What I understand is that the specific action is performed 512 times? If so the payload can be put in memory each time.
The error Supplemental Detail java.lang.OutOfMemoryError: allocLargeObjectOrArray: [C, size 9716016] lets you know that is had 97Mb less available then needed.
I easy option is to make your heap size of the JVM larger. The error does occur when the heap size is full.
-Xms<size>  set initial Java heap size
-Xmx<size>  set maximum Java heap size
-Xss<size>  set java thread stack size
-Xms512m -Xmx1152m -Xss256m
Other option is to look if you can perform transformation without using the large payload. Do you need to assign the large payload for all the 512 db adapter requests?