Q

JCo connectivity, out of memory problem

We have a JCO client trying to execute a BAPI and get a table containing 10,000 rows. The IBM's proxy based RFC

API has no problem doing it. However, when we changed it to JCo, we have the out of memory error from middle ware (listed below.) Is there any way to change buffer size. What is the problem? Can you help us? Thanks very much. Error message: java.lang.OutOfMemoryError: out of memory at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeExecute(Native Method) at com.sap.mw.jco.rfc.MiddlewareRFC$Client.execute(MiddlewareRFC.java:76 0) at com.sap.mw.jco.JCO$Client.execute(JCO.java:2378) at com.sap.mw.jco.JCO$Client.execute(JCO.java:2313) at com.bcone.util.JcoProcessor.extractToRepository(JcoProcessor.java:281 ) at com.bcone.util.JcoProcessor.processExtract(JcoProcessor.java:231)


Out of memory can be fixed by increasing the space allocation for the JVM (details differ between VMs). There is no limited buffer in JCo as far as I know. JCo may need a little bit more space since it marshalls the complete table from C to Java in order to provide much better performance.


This was first published in May 2002

Dig deeper on SAP Java and J2EE

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close