Visibroker files in /tmp directory
- Product Name: VisiBroker for C++
- Product Version: 7.0
- Product Component: ORB, Communication
- Platform/OS Version: All
When you start your VisiBroker application, several files are created in the /tmp directory that appear to be related to the ORB. The files have the following name pattern: orb_pid_# orb_pid_#_sem orb_pid_#_shm where pid is the application process ID, and # is a number of unknown source. You would like to know the answers to the following questions.
1. Whether or not these files can be safely deleted while their application is running?
2. If they should not be deleted, whether it is possible to configure the location where these files to be created in?
These files are being used for the local IPC communication between client and server if they are running on the same machine. If you are not using local IPC when the client and server are on the same machine, it may result in a performance hit as there is an overhead of traversing the TCP/IP stack. As a result, CPU utilization will be increased when local IPC is not used.
These files will be deleted automatically if the server is shutdown using Ctrl-C (signal 2/SIGINT and 15/SIGTERM), or through orb->shutdown(true). If the server is killed using -9 (SIGKILL) signal, the server cannot clean up these files. Therefore there is a chance that the number of such files will be growing if the server is not terminated gracefully. It will remain in the system until the next reboot.
There is no harm on deleting these files that are left over by the previous run except those belongs to the server process that is currently running. List the running server process PIDs to find out.
By default, shared memory is used in HP, AIX and Linux for local IPC communication. These can be turned off, please refer to the product documentation for details. Unix domain socket is also used for local IPC communication. To avoid the creation of above files, you can set property vbroker.se.default.local.manager.enabled=false. However it will also disable Unix domain socket for local IPC and it will fall back to using TCP/IP socket communication for local machine Clients.
The enhancement request CR 7337 to make it configurable to have these files write to the location specified by the user is addressed in the Service Pack Level 4.