db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Pendleton <bpendle...@amberpoint.com>
Subject Re: [jira] Commented: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception
Date Sat, 12 Apr 2008 23:15:08 GMT
> Well, on a second check, it's definitely memory-related. Check this bit out:
> E.java.io.IOException: java.io.IOException: Cannot allocate memory
>         at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
>         at java.lang.Runtime.execInternal(Native Method)
>         at java.lang.Runtime.exec(Runtime.java:566)
> How should I proceed? Do I inflate the swap file?

Yes, this sounds like a situation where adding swap space would work fine.

I'd say, triple the amount of swap space that you currently have configured,
and try the test run again.



View raw message