Signal use of the Java Virtual Machine within OpenAccess SDK Server
- Last Updated: May 12, 2026
- 1 minute read
- OpenAccess SDK
- Version 9.0
- Documentation
The following table summarizes the rules that apply if the OpenAccess Service starts the JVM on UNIX.
Signals Used by the JVM and OpenAccess SDK Server
| Signal | Use |
| SIGBUS, SIGSEGV, SIGILL | Must be handled by JVM. ServiceCatchException must be set to false. |
| SIGPIPE | Ignored. SIGPIPE must be always blocked or ignored. Not doing this may cause the server process to exit, for example, when a client has exited its application abnormally. |
| SIGUSR1, SIGUSR2 | Must be handled by the JVM. OpenAccess SDK Server is aware of this and takes the required action. |
| SIGINT, SIGTERM, SIGHUP | By default, the signal is handled by the VM. To disable this, use the -Xrs option. |
For more information on the handling of signals by a specific JVM on UNIX, please refer to the following websites:
| Signal | Document location |
| IBM Java | https://www.ibm.com/developerworks/ |
| Oracle Java | https://www.oracle.com/technetwork/java/javase/index-137495.html |
On Windows, the service template OpenAccessSDK900_OpenAccessSDK_Java uses the ServiceJVMOptions service attribute to reduce the use of signals. Set ServiceJVMOptions to -Xrs. Refer to the OpenAccess SDK Administrator’s Guide for more information.