Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Using Messages With Identifiers : EE: Execution Environment

EE: Execution Environment
S6BEE001I
Completed Activation of Execution Environment
Execution Environment
The Execution Environment has been successfully activated.
No action required.
S6BEE002I
Completed Deactivation of Execution Environment
Execution Environment
The Execution Environment has been successfully deactivated.
No action required.
S6BEE008E
Binding area could not be created
Execution Environment
Binding area creation failed.
Check the binding area parameters in client defaults.
S6BEE009E
There was insufficient memory to create a binding area
Execution Environment
Binding area creation failed due to a shortage of memory.
Try to kill some processes.
S6BEE010E
Could not create shared memory
Execution Environment
Shared memory creation failed.
Contact TIBCO Support.
S6BEE011E
Could not release existing binding area, because the shared memory segment is in use
Execution Environment
Failed to release existing binding area because it is being used.
Contact TIBCO Support.
S6BEE012E
OS would not permit release existing binding area
Execution Environment
Release of existing binding area failed.
Contact TIBCO Support.
S6BEE013E
Could not remove locks for shared binding area
Execution Environment
Remove locks failed for shared binding area.
Contact TIBCO Support.
S6BEE014E
Could not create locks for binding area
Execution Environment
Create locks failed for binding area.
Contact TIBCO Support.
S6BEE015I
Peer servers started
Execution Environment
Peer gateways started.
No action required.
S6BEE016I
... data servers started
Execution Environment
The listed data gateways successfully started.
No action required.
S6BEE017E
Data Server ... terminated because ...
Execution Environment
The indicated gateway disconnected for the given reason.
See the log file for more details.
S6BEE020I
... server ... started
Execution Environment
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.
S6BEE021E
... server ... connection lost, server likely failed
Execution Environment
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.
S6BEE022E
... server ... failed because ...
Execution Environment
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.
S6BEE023I
... server ... restarted
Execution Environment
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.
S6BEE024I
... server ... terminated normally
Execution Environment
The peer server or rules-based gateway has terminated normally. It was likely stopped through a Data Object Broker command.
No action needs to be taken.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved