|
|
|
|
|
|
|
The session stopped as a result of an operator request or of a Data Object Broker request.
|
|
|
The Execution Environment stopped as a result of an operator request.
|
|
|
The Execution Environment closed as a result of an operator request.
|
|
|
The first rule of the session ended as a result of an uncaught exception.
|
Check the session logs. Review your application. Place the appropriate exception handler at the end of your first rule to catch the exception.
|
|
|
|
|
|
|
|
|
|
|
|
Your user account is set up so that it can log in to the system only during certain hours of the day. You should either get your account updated, or wait until you are permitted to log in.
|
|
The TIBCO Object Service Broker user ID does not match the operating system user ID.
|
System security is set to require the TIBCO Object Service Broker user ID to match the user's operating system user ID. Either change the security setting or log in with matching user IDs.
|
|
|
|
|
The Execution Environment to Data Object Broker internal connection limit is exceeded.
|
|
|
|
Finally, check the log files (Data Object Broker, Execution Environment, osMon, and session) for any other possible clue.
|
|
|
|
|
|
Check the contents of the @NLS1 table. If necessary, also check the log files (Data Object Broker, Execution Environment, osMon, and session) for any other possible clue.
|
|
|
|
|
TIBCO Object Service Broker cannot locate the path specified by the OS_ROOT environment variable.
|
|
|
|
Check the log files (Data Object Broker, Execution Environment, osMon, and session) for any possible clue.
|
|
|
|
|
The TIBCO Object Service Broker session failed to log in to the Data Object Broker.
|
Finally, check the log files (Data Object Broker, Execution Environment, osMon, and session) for any other possible clue.
|
|
TIBCO Object Service Broker failed to establish a connection to the client process.
|
|
|
|
If the client process was not explicitly killed, check your network connectivity. Otherwise, no action is required
|
|
The TIBCO Object Service Broker session failed to open a connection to the Data Object Broker.
|
Check the validity of the Data Object Broker node definition in the TIBCO Object Service Broker directory file (huron.dir).
Finally, check the log files (Data Object Broker, Execution Environment, osMon, and session) for any other possible clue.
|
|
|
Check whether the Data Object Broker host is still accessible via the network. Check the log files (Data Object Broker, Execution Environment, osMon, and session) for any other possible clue.
|
|
TIBCO Object Service Broker failed to establish a peer server connection to the Data Object Broker process.
|
Check the SERVERS Execution Environment parameter. Check the log files (Data Object Broker, Execution Environment, osMon, and session) for any other possible clue.
|
|
|
Check whether the Data Object Broker host is still accessible via the network. Check the log files (Data Object Broker, Execution Environment, osMon, and session) for any other possible clue.
|
|
The Execution Environment terminated due to a failure on its listening named pipe.
|
Check the operating system diagnostics for possible interprocess communication problems. For assistance, contact TIBCO Support.
|
|
|
Check the log files (Data Object Broker, Execution Environment, osMon, and session) for any possible clue. For assistance, contact TIBCO Support.
|
|
|
Check the log files (Data Object Broker, Execution Environment, osMon, and session) for any possible clue. For assistance, contact TIBCO Support.
|