Kbase 21620: SonicMQ: How To Avoid a Broker Hang on Solaris 2.8
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/12/2001 |
|
SUMMARY:
This Knowledge Base Solution explains a possible reason for a hung (not responding) SonicMQ version 3.5 broker on Solaris 2.8.
EXPLANATION:
With SunOS 5.8 the default soft limit of the number of possible file descriptors is 256. While typically sufficient to install SonicMQ Version 3.5 and also to run the basic examples which come with the product, it might not always be sufficient to run a real application in production with many users and connections. Use this command to check the limit of possible file descriptors:
ulimit -n
That number is including the number of possible socket connections as well. If the limit is reached, no new connections to the broker can get created, though existing connections are continuously working fine.
Another known scenario is that the broker is not able to start in a clustered environment, or if using dynamic routing as soon as that limit is reached. This problem is documented in SonicMQ Release Notes, entry [970], but also applies if an ORACLE database is used over JDBC as broker database for SonicMQ.
SOLUTION:
Increase the ulimit before starting the SonicMQ broker on
Solaris 2.8. Use the command, ulimit -n <number>, where number
is the number of file descriptors needed. Or, add the following parameters to the /etc/system file and reboot,
set rlim_fd_cur=2048
set rlim_fd_max=2048
as suggested within the Release Notes ( file docs/Release.htm )
References to Written Documentation:
SonicMQ documentation Release Notes
Progress Knowledge Base Solutions:
19225, "Apptivity-Server Cannot Send reply-connection closed-Oracle"
19767, "'Table Does Not Exist' Starting SonicMQ Broker on Solaris"
19823, "SonicMQ: 'Too many open files' Error on Solaris"