Re: WebObjects Deployment on Linux - queer out of memory exception
Re: WebObjects Deployment on Linux - queer out of memory exception
- Subject: Re: WebObjects Deployment on Linux - queer out of memory exception
- From: Pascal Robert <email@hidden>
- Date: Mon, 28 Oct 2013 21:32:29 -0400
This is the default limits on a CentOS 5 box. They are actually lowers than yours. But they might be using a container like OpenVZ that have other limits.
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 43533
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 43533
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
> These are the limits, but I don't see where the problem is, can you please have a look?
>
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f) unlimited
> pending signals (-i) 127260
> max locked memory (kbytes, -l) 64
> max memory size (kbytes, -m) unlimited
> open files (-n) 1024
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 10240
> cpu time (seconds, -t) unlimited
> max user processes (-u) 127260
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
>
> Maybe the max locked memory is my problem? I don't see anything with threads in the listing.
>
> Regards,
>
> Ute
>
>
> Am 26.10.2013 um 19:36 schrieb Pascal Robert:
>
>> Please send your replies to the mailing list instead of directly to me…….
>>
>>> Thanks a lot, for the link. On the system itself I did a top and it looked as if 3GB free Memory where available,
>>> that should be enough. But this is not a "real" server but a server partition on a web server hoster, so maybe there are limits
>>> from the server installation.
>>
>> So they are probably putting small limits on the number of files or other resources that you can use. I guess you have root (or sudo) access? Run « ulimit -a » to see resource limits.
>>
>>>
>>> Am 25.10.2013 um 11:14 schrieb Pascal Robert:
>>>
>>>>
>>>> Le 2013-10-25 à 04:59, ute Hoffmann <email@hidden> a écrit :
>>>>
>>>>> Hi,
>>>>> I'm have a WebObjects Deployment scenario where I cannot get the app to start.
>>>>>
>>>>> After a long trail of removing Issues I get this error message, when I try to start from shell.
>>>>>
>>>>> Starting the App via JavaMonitor: App dies without log, even with 288M allocated.
>>>>> With the same allocated memory Xmx the same app runs without problems on another server..
>>>>>
>>>>> DEBUG NSLog - === Begin Internal Transaction
>>>>> DEBUG NSLog - evaluateExpression: <com.webobjects.jdbcadaptor.MySQLPlugIn$MySQLExpression: "SELECT t0.bedeutung, t0.id, t0.wert FROM adminmaster t0" withBindings: >
>>>>> DEBUG NSLog - 28 row(s) processed
>>>>> DEBUG NSLog - === Commit Internal Transaction
>>>>> WARN NSLog - A fatal exception occurred: unable to create new native thread
>>>>> <main> java.lang.OutOfMemoryError: unable to create new native thread
>>>>
>>>> What about memory on the system itself? See http://javaeesupportpatterns.blogspot.de/2012/09/outofmemoryerror-unable-to-create-new.html
>>>
>>>
>>>>
>>>>> The database access happens in the Application start process.
>>>>>
>>>>> Any idea where the problem could be? 28 rows cannot be a real memory problem, The table in question is standalone,
>>>>> no connections whatsoever to other tables.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Ute
>>>>> _______________________________________________
>>>>> Do not post admin requests to the list. They will be ignored.
>>>>> Webobjects-dev mailing list (email@hidden)
>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>
>>>>> This email sent to email@hidden
>>>>
>>>
>>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden