URGENT: IS4.6 restart issue

Has anyone had an issue where a webMethods Integration Server spontaneously restarts itself? If so, I would appreciate you sharing your experience.

We are running IS4.6 on Windows NT with jdk1.3.0_08.


J Silver

Make that jdk1.3.1_08.

We had that problem - support said it was possibly because a process got interrupted when writing the server.cnf file - end result was that the server spontaneously lost it’s license key.

Was the issue ever resolved?

No. Support’s solution was to monitor the server.cnf file. to figure out what’s causing the problem in the first place. We’re upgrading to 6.0.1, so hopefully that problem disappears with the new software.

Of course, in your case, it might be a different issue too.

Solved by adding the parameter -xrs to the command in server.bat that starts the java service.

what does the -xrs do??

From a parallel discussion I started at wmusers.com:

Posted by Rob Eamon

Reduces usage of operating-system signals by the Java virtual machine (JVM). This option is available beginning with J2SE 1.3.1. In J2SE 1.3.0, the Shutdown Hooks facility was added to allow orderly shutdown of a Java application. The intent was to allow user cleanup code (such as closing database connections) to run at shutdown, even if the JVM terminates abruptly.

The JVM watches for console control events to implement shutdown hooks for abnormal JVM termination. Specifically, the JVM registers a console control handler which begins shutdown-hook processing and returns TRUE for CTRL_C_EVENT, CTRL_CLOSE_EVENT, CTRL_LOGOFF_EVENT, and CTRL_SHUTDOWN_EVENT.

The JVM uses a similar mechanism to implement the pre-1.2 feature of dumping thread stacks for debugging purposes. Sun’s JVM uses CTRL_BREAK_EVENT to perform thread dumps.

If the JVM is run as a service (for example, the servlet engine for a web server), it can receive CTRL_LOGOFF_EVENT but should not initiate shutdown since the operating system will not actually terminate the process. To avoid possible interference such as this, the -Xrs command- line option has been added beginning with J2SE 1.3.1. When the -Xrs option is used on Sun’s JVM, the JVM does not install a console control handler, implying that it does not watch for or process CTRL_C_EVENT, CTRL_CLOSE_EVENT, CTRL_LOGOFF_EVENT, or CTRL_SHUTDOWN_EVENT.

There are two consequences of specifying -Xrs:
Ctrl-Break thread dumps are not available.
User code is responsible for causing shutdown hooks to run, for example by calling System.exit() when the JVM is to be terminated.