1975
WQS initialise failed, connected to shared memory for NodeName
Description
The WQS process has failed to start because of a shared memory conflict. This can happen if, for example, the iProcess Engine is restarted and another application allocates to itself the shared memory key that iProcess expects to use when it restarts.
NodeName is either:
| • | blank, if the conflict is with a non-iProcess application, or |
Draft comments: How do you tell what the conflict is with in this case?
| • | the node name of another that is running on the same computer, if the WQS process has connected to the WQSINDEX shared memory for that iProcess node. |
|
Note |
This error message is only applicable on UNIX systems. |
Appears In
SWDIR\logs\sw_error
Severity
1 (Critical)
Action
To resolve this problem, do one of the following:
| • | If the shared memory is from an node that is no longer required, remove it by using the UNIX ipcrm utility or by rebooting the computer. |
|
Note |
You can use the UNIX ipcs utility to list shared memory segments. |
| • | If the shared memory conflict is with another node on the same computer, use the SWDIR\util\swadm command to change the value of the SHMKEY_ID process attribute for this . This value is a single character (the default is “x”) that is used to build the shared memory key. |
See Also
The following sections in the TIBCO iProcess Engine: Administrator's Guide:
| • | “SHMKEY_ID”, for a detailed description of this process attribute. |
| • | “Set a Process Attribute”, for more information about the SWDIR\util\swadm command. |