LANSA Integrator - Large XML files

This Q&A forum allows users to post and respond to "How Do I Do ....." questions. Please do not use to report (suspected) errors - you must use your regional help desk for this. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
Post Reply
cesarrafael
Posts: 3
Joined: Tue Dec 01, 2015 3:44 am

LANSA Integrator - Large XML files

Post by cesarrafael » Tue May 15, 2018 9:37 pm

Hi All,

We are currently using LI to create XML files that we have to deliver to the Central Bank periodically. It happens that some of these XMLs are extremely big due to the type and amount of information requested.
When creating these XMLs we are experiencing "Java heap" errors, possibly because everything is being written into memory first, only creating the xml file at the end of the function.
Conclusion: The job crashes, some dumps and traces are written, but no XML.
Tried to increase the heap memory, switch of tracing, etc, to no avail.
Anyone has any good tip to work around this issue?

We're using XMLBindFileService and Lansa 14Sp1

Thanks in advance,

kno_dk
Posts: 91
Joined: Tue Feb 23, 2016 12:00 am

Re: LANSA Integrator - Large XML files

Post by kno_dk » Wed May 16, 2018 6:29 am

Hi

I have the same problem when I read a large XML file with LI - a 64 mb xml file eat the 2 gb heap!

/Klaus

cesarrafael
Posts: 3
Joined: Tue Dec 01, 2015 3:44 am

Re: LANSA Integrator - Large XML files

Post by cesarrafael » Wed May 16, 2018 9:07 am

Have you fond any workaround for that, Klaus? Surely someone else should have had this problem before...
I also noticed that it's a little slow when "setting the fragments"....but I can try to fix that.

gerryc
Posts: 3
Joined: Fri Apr 21, 2017 8:32 pm

Re: LANSA Integrator - Large XML files

Post by gerryc » Fri Jun 01, 2018 7:31 pm

Hi,

Have you tried increasing the "-Xms" and "-Xmx" values in the JSM Administration file (JVMOptions parameter)?

For Windows:
Drive:\LansaInstallation\Integrator\JSMAdmin\jsmmgrdta.txt (https://docs.lansa.com/14/en/lansa093/c ... 4_0001.htm)

For iSeries:
Data Area JSMMGRDTA (https://docs.lansa.com/14/en/lansa093/c ... 5_0100.htm)

I had this problem and solved it by changing the value from:
JVMOptions=-Xms128M -Xmx128M -Xrs
to
JVMOptions=-Xms16384M -Xmx16384M -Xrs

Don't forget to restart the JSM after you've increased the values.

Hope this helps,
Gerry.

Post Reply