![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Completed Activation of Execution EnvironmentThe Execution Environment has been successfully activated.Completed Deactivation of Execution EnvironmentThe Execution Environment has been successfully deactivated.Check the binding area parameters in client defaults.There was insufficient memory to create a binding areaBinding area creation failed due to a shortage of memory.Could not release existing binding area, because the shared memory segment is in useFailed to release existing binding area because it is being used.Release of existing binding area failed.Remove locks failed for shared binding area.The listed data gateways successfully started.The indicated gateway disconnected for the given reason.The Execution Environment started a new peer or rules-based gateway.This message is generated during Execution Environment initialization, when peers or rules-based gateways are defined for the Execution Environment. No action need be taken.The Execution Environment was notified that a peer or rule-based gateway unexpectedly terminated. The gateway has likely failed.Review the session message log for the gateway to determine the cause of the failure and take corrective action. The file name for the log is determined by the gateway name displayed in the message. The path of the log file for the gateway is defined by the Execution Environment defaults for the gateway type.A peer or rules-based gateway has failed during initialization. The message displays the cause of the error.Review the cause of the error and take corrective action. Possibly more information can be found in the gateway's session log. The name of the log file is determined by the gateway name. The path of the log file is determined by the Execution Environment defaults for the gateway type.The Execution Environment has determined that a peer server rules-based gateway has failed and should be restarted.Review the session log for the gateway/server to determine the cause of the failure. The name of the file is determined by the name of the gateway/server. The path of the log file is defined in the defaults for the Execution Environment for the gateway/server type.The peer server or rules-based gateway has terminated normally. It was likely stopped through a Data Object Broker command.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |