300mb message crashes server (unix/oracle)

[Former Member]

Hi everybody,

Using File Adapter (FTP), I exchange a 300MB message and the server stopped, the sdm and dispatcher are running but the server always shows the message "waiting for starting" and does not work.

I've got the error:

FATAL: Caught OutOfMemoryError! Node will exit with exit code

666java.lang.OutOf

MemoryError

at

java.io.ByteArrayOutputStream.toByteArray(ByteArrayOutputStream.java:

154)

at com.sap.aii.adapter.xi.ms.XIMessage.render(XIMessage.java:1111)

at

com.sap.aii.adapter.xi.ms.XIMessage.getTransportHeaders(XIMessage.jav

a:519)

at

com.sap.aii.af.ra.ms.impl.ServicesImpl.transmit(ServicesImpl.java:625

)

at

com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.ja

va:349)

at

com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.invokeHandler(SendC

onsumer.java:341)

at

com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(SendConsu

mer.java:112)

at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:834)

at

com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)

at

com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:3

7)

at

java.security.AccessController.doPrivileged(AccessController.java:215

)

at

com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.ja

va:100)

at

com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:1

70)

</verbosegc>

Thanks for any help,

Renato Lima

[Former Member]

In order to access this parameter, use the configtool, cluster-data->instance<number>->server<number>, two clicks. You will see a screen with the all parameters of java initializations, including Max Heap Size (MB).

Regards,

Renato.

[ravi_raman2]

Renato,

Increasing the java heap size is only a temporary solution, this can be a bigger problem later on, as increasing the heap size would mean now the jvm now has to expend more resources to monitor the threads instead of executing the tasks.......a deadlock here can be very painful to debug...not tough..painful.

Regards

Ravi Raman

[Former Member]

We increased the max heap size to 6GB and solved the problem.

[Former Member]

Hi Renato !

Could you tell me where is that parameter to change?

Thanks !

Regards,

Matias.

[Former Member]

Hi Renato,

In general I can support what was said already before. Try to reduce the size of your file. The best throughput in XI is reached if the XI message sizes are between 100KB and 2MB. Depending on you scenario processing the 300MB file this might not be the case.

Can you please provide some information how you increased the Java heap ?

- did you add Java server nodes ?

- What is the heap size of each server node ?

- Which UX you are using ?

Thanks in advance,

Juergen

[Former Member]

For 300 MB adapter egnie based on java crashes becaue out of memeory so split file use this option in file adapter.

before restarting ur server remove the 300MB file from file folder and restart it.

Regards

Sreeram.G.Reddy

[Former Member]

hi renato,

have a look at the below thread...here some practical experiences about file size limit is shared...

also can u take a look at shravya blog in processing huge files...

/people/sravya.talanki2/blog/2005/11/29/night-mare-processing-huge-files-in-sap-xi