Threads

The Threads page provides both a view of how Rhapsody operates and recovery control in the event of serious failures, such as runaway routes or hung communication points. In most cases, Rhapsody should recover automatically. If not, these controls provide a way to attempt further recovery without having to bring down the engine, which may disconnect a number of additional running interfaces.

Occasionally, individual processes lock up and are difficult to bring back under control; for example, runaway routes or hung communication points. Normally, when a communication point or route is stopped, the automatic shutdown process completes the following actions:

1. Signals the component to shut down cleanly.
2. If the component is still running after approximately 30 seconds, a shutdown interrupts the threads running the component.
3. If the component is still running after a further 30 seconds or so, a shutdown forcibly stops the threads running the component.

If completing the above steps fails to stop a thread, that thread is most likely stuck in native code and Rhapsody will not be able to stop it automatically. However, the thread can be stopped manually from the Threads page.

A warning banner is displayed under the page heading with the following text: Interrupting or stopping threads is only recommended in extreme circumstances for advanced Rhapsody users.

There are four tables displayed on this page:

• Route Execution Threads - displays all threads allocated to route processing. They are not dependent on the number of routes as every thread can process messages from any route. If a route exists within the Route column it will link to the Route Properties Page.
• Message Collector Timeout Threads - displays threads controlling the timeouts of message collectors. If a filter exists within the Filter column it will link to the Filter Details Page.
• Administration Threads - displays threads processing IDE commands. Each IDE connection has a thread associated with it. This allows specific connections to be terminated as required.
• Communication Point Threads - displays all threads associated with communication points.