How to avoid starting up WAS at boot time on Linux with system default nofile 1024 instead of set value 65536 in /etc/security/limits.conf ?
![]()
We are to switch our CLM (RTC/RRC) 5.0.2 from Windows/Tomcat to Linux/WAS: While planning we found "Important: If you use a system startup script such as /etc/init.d/was or /etc/rc.*/SXXWebSphere to start WebSphere® Application Server at system boot up time, init.d invokes the startup scripts with the maximum number of file descriptors set to 1024 instead of the system default value that is set in /etc/security/limits.conf (65536). To avoid this problem, after a system boot up, manually run /etc/init.d/was restart from a root shell. This will ensure that WebSphere Application Server is restarted with the correct file descriptor limit."
Would it be effective to modify the OOTB WAS startup script to start with logging in to our service account (with su - svc_clm) before executing the rest of the script, to avoid the manual restart step? (Obvious that we have no previous experience installing WAS or CLM with WAS though our CLM was switched from Linux/WAS to Windows/Tomcat in 2013 for internal convenience)
At that time nofile was set (on the old server):
* hard nofile 65536
* soft nofile 65536
but nproc was not set as required now to:
* hard nproc 10000
* soft nproc 10000
|
Accepted answer
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.