Skip to main content

WASService.sh and ulimit.... a tricky combo


From version 7 onward, the Application Server scripts and configuration scripts have the good manner to set by themselves the right ulimit valu. So ulimit is now less a problem than it was before. The problem is that, sometime when dealing with linux services,things do not always get right.

For example you get exceptions such as

[11/14/13 12:06:15:483 CET] 00000066 exception     E com.ibm.ws.wim.adapter.ldap.LdapAdapter authenticateWithPassword
                                 com.ibm.websphere.wim.exception.WIMSystemException: CWWIM4520E  The 'javax.naming.CommunicationException: ldapus.ldap.domain.com:389 [Root exception is java.net.SocketException: Too many open files]' naming exception occurred during processing.

(In case you are asking, yes, network connections are counted as open files)

That's why I strongly suggest to modify your /etc/security/limits.conf (on RedHat) before restarting your machine, after you added WASService.sh service to your linux box. We added to the file the following two lines to the /etc/security/limits.conf

*               soft    nofile            32768
*               hard   nofile            32768

and then restarted the machine and had my Connections environment working.




Comments

Unknown said…
Io l'avrei chiamato "Collabora et Labora"... perchè non amo molto "l'ora" :-) Ciao Franceschiello ;-)
12/04/2013 09:50:00 AM
Post a Comment

Popular posts from this blog

Multiple controllers with Spring Boot

Remember, when you want to have multiple controllers with Spring Boot, you should always name them differently in the annotation, otherwise they will not work So these two together will NOT work (or just one of them will work) These two instead WILL work.
2 comments
Read more

The "Code-Rich" Organization: How Automatic Code Generation Will Revolutionize Everything

  I put on paper a couple of thoughts about AI and Large Language Models (LLM) for automatic code generation in the development process. My thesis is that the current organizations are mostly “code-thin”, where only the basic Business Processes are modeled through software, while in the future we will have “code-rich" organizations boosted through the abundant and cheap AI and LLM Generated software code. These “code-rich” organizations, where every possible business process is software based - will outperform the usual "code-thin" organizations, where software is “hand-made” and expensive. Feedback would be very, very appreciated. https://www.linkedin.com/pulse/code-rich-organization-how-automatic-code-generation-de-collibus
Post a Comment
Read more