Exiting mvDesigner

One known issue for FlashCONNECT 3.1 and mvDesigner 2.0 is that using the Quit Omnis command when exiting an mvDesigner application causes mvDesigner to crash.

Workaround

Use the Quit Omnis (Force quit) command instead.

Heartbeat

Warning—

(D3 only) The use of the Heartbeat feature on FlashCONNECT requires configuration settings on both the Web server and the D3 server. Incorrect settings of these parameters can cause a phantom lock to be left asserted by the heartbeat process.

To clear the phantom locks if the phantom scheduler appears to be hung (if phantom processes remain in the queue):

1.  Type list-locks (m to ensure that the heartbeat process has left a phantom lock set.

2.  Type clear-locks (m to release the lock.

NOTE—

•The m-option for the list-locks and clear-locks commands is available on 7.1 with patch A148 or later and 7.2 with patch A41 or later.

•Use caution when clearing phantom locks to avoid scheduler corruption.

For more information on the Heartbeat feature, see the FlashCONNECT Administration Guide on this CD.