This content has been marked as final. Show 4 replies
Probably your file limit descriptor should be increased
Increase the File Descriptor limit
ulimit -n <to a proper value>
Or ask you system admin to set this in the limits.conf for your WLS Software owner
The common reason of running into FD limit exception is the increase in the FD consumption or low value configured for the ulimit.
In case increasing the ulimit value fixes the issue (which will only be the case if we have not properly configured the system) then we need to collect some lsof() output to check what is the state of the socket and in case there is not issue with the socket management.
Thus to start with tune ulimit and if this does not fix the issue collect lsof() output to check where are the FD's/socket consumed.
ulimit value was 1024 and after changing it to 4096 i am able to start em console but there is another issue.
I am changing this ulimit from putty and starting the server, so whenever that putty session gets closed, ulimit value is again getting reset to 1024 and em again goes to failed state.
Please let me know how to permanently change ulimit value.
To make this change permanent login with root user and edit file /etc/security/limits.conf
Add below fields for the user (for example here I have installed MW with weblogic user):
weblogic hard nofile 131072
weblogic soft nofile 131072
weblogic hard nproc 131072
weblogic soft nproc 131072
weblogic soft core unlimited
weblogic hard core unlimited
weblogic soft memlock 3500000
weblogic hard memlock 3500000