The SPR description describes the problem perfectly:
Fix for a memory leak when passing strings from Java back to LotusScript, which had caused LS2J Error: Threw java.lang.OutOfMemoryError.
It looks like we will be upgrading to 6.5.3 or higher.
LS2J Error: Threw java.lang.OutOfMemoryError
I have been working on a project that moves data to and from LDAP using JNDI and Java. I have built document based LEI type engine using LotusScript and wanted to take advantage of it but had to use Java talk to LDAP. The best fit seemed LS2J, based Julian’s LS2J example everything looked great. All the testing was going great both updating and reading LDAP. Then I started receiving LS2J Error: Threw java.lang.OutOfMemoryError. Having written Java code in Domino before I went through my code making sure that everything was set to null; when I was done. Still the problem existed.
The SPR description describes the problem perfectly:
It looks like we will be upgrading to 6.5.3 or higher.
The SPR description describes the problem perfectly:
It looks like we will be upgrading to 6.5.3 or higher.
Hi – Did this fix your problem?
Thanks,
Martina
After we upgraded to 6.5.3 I started getting StackOverFlowError as described here:
http://www.chadsmiley.com/chadsmiley/home.nsf/plinks/LS2J_StackOverflowError
IBM was willing to give me a hot fix for the server, but I had already converted my code to LotusScript becuase of our projects time line. I believe the fix was going to make 6.5.5, but I am not sure.
Hope that helps.