Not enough memory space on solaris 10

[Yesenia]

Hello all,
I am running with several task submission clients pumping task to my application on Solaris 10 system for near about the time of 24hrs duration. After some hours, I am receiving an error message as :

"Not enough memory space exception" .

I have installed and configured the solaris 10 on default configurations configured up already by SUN. Any suggestion would be appreciated.. please help me out from this error message .

[Quinton]

I am running with an E25K and returns the similar error after the migration procedure of Solaris (9 => 10) after some hours. I made the installation of the solaris resource manager for handling the sessions on main server. Right now, when I look at the system then I found that the system is semi-stable, but error message as : prstat: not enough memory: Not enough space

occurs for example after making the configuration of prstat. Any idea ??

[BansiJI]

I was just trying to find the approrpriate result for this very and I got something which can be or not , I wanted to share with you all. I found that a project and a large number of file-descriptors groups for example :10000, ulimit -n 1024 then prstat started functioning once again ..

PROJID NPROC SIZE RSS MEMORY TIME CPU PROJECT
0 93 9495M 7860M 98% 0:03:04 1.1% system
1 6 28M 17M 0.2% 0:00:00 0.1% user.root
200 1 3048K 2392K 0.0% 0:00:00 0.0% group.mqm
3 10 46M 25M 0.3% 0:00:00 0.0% #default

[Glenny]

The shell that we always associate to work with the tcsh. So I have used to go with the go with the # limit descriptors 1024.

ulimit -a.

time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) 0
nofiles(descriptors) 1024
vmemory(kbytes) unlimited

Actually, In case of prstat, it complained again: >prstat
prstat: not enough memory: Not enough space

Any suggestions regarding this ? If this issue is referenced with only prstat, then this is not a issue for us. But if we are running with different issues (bind crashes) on this system. From vmstat, memory is not a actually issue :

[Macarenas]

The Virtual Swap Reserved is near about 12GB. This is the similar as the application memory capable to display in the prtmem output. This is just because for every application page a associated backing storage is already allocated on disk even though this is not currently in use. This space is just in situation where the system achieves at the critical shortage and the page has to be copied out to the disk at the time of writing procedure.

[Shawn-Roger]

I am the same issue using the IBM 1.5.0_13-b05 JRE on Solaris 10 while installing a software but I am not sure how to resolve this issue . I think that if it's talking about disk space or virtual memory. I would like to be sure about what system reference is failing in the native ways and what the errno is. My system is only a SunBlade 100 (one of my friend suggest me that he got something used ones for sale for near about $20) and it's already increased out at 2GB of hard memories . My filesystems seems fine so I am just going through more toward virtual memory.

[lorenz]

I got the exact same thing going on with me on a 2 GB SunBlade 2500, when launching another one Eclipse workbench. I also primarily tested whether one of the filesystems was full but that switched out not to be the situation . So, I moved at my swap status:

[~] $ swap -s
total: 2340120k bytes allocated + 1141408k reserved = 3481528k used, 167312k available
[~] $