This message indicates the exit status of an internal Data Object Broker process. In this case the process stopped after detecting a problem. Look for previous error messages that may indicate the specific problem.
This problem may occur during abend situations if parts of the Data Object Broker have stopped unexpectedly. If there are no apparent reasons for this problem to occur then this message may indicate a Data Object Broker internal problem.
If you suspect that this is a Data Object Broker internal problem then contact TIBCO Support. Be prepared to submit a copy of the Data Object Broker log file and any core file produced as a result of this problem.
This problem may occur during abend situations if the internal communication mechanism has been damaged. If there are no apparent reasons for this problem to occur then this message may indicate a Data Object Broker internal problem.
If you suspect that this is a Data Object Broker internal problem then contact TIBCO Support. Be prepared to submit a copy of the Data Object Broker log file and any core file produced as a result of this problem.
The Data Object Broker has received a shutdown request. This can occur in the following ways: a SHUTDOWN operator command is received, a shutdown request is issued from an Execution Environment, a "hrncr shutdown" or "hrncr stop" command is issued, or a SIGTERM signal is sent to the hrncr supervisor process of the Data Object Broker.
An attempt to create the shared rules buffer, used by local Execution Environments, has failed. Look for a previous error message to indicate the specific problem.
The Data Object Broker has received a kill request. The Object Service Broker System Administrator has issued the "hrncr kill" command, or a SIGABRT signal has been sent to the hrncr supervisor process of the Data Object Broker.
The Data Object Broker was unable to start an internal process. The specific reason for the failure is indicated by the errno value that should be part of this message. The most likely cause of failure is a shortage of memory or process entries in the system. It may also be the result of a configured limit on the number of processes.
This message indicates the exit status of an internal Data Object Broker process. In this case, the process was terminated by a signal. If the signal is SIGKILL, the process was likely terminated as part of the cleanup during an abnormal termination of the Data Object Broker. Signals such as SIGFPE, SIGSEGV, and SIGBUS are exception conditions raised by the system that indicate an internal Data Object Broker problem.
If you suspect that this is a Data Object Broker internal problem then contact TIBCO Support. Be prepared to submit a copy of the Data Object Broker log file and any core file produced as a result of this problem.
A very busy system may account for the delay in the startup. Otherwise the Data Object Broker is likely hanging as it attempts to access either communications or files.
If this problem is due simply to a busy system, increase the value of the TIMEOUTSTART parameter in the crparm file. Verify that the devices and file systems that hold the Pagestore are available, and that TCP/IP communications are responding.
The Data Object Broker is abending because one or more Data Object Broker processes have stopped without being asked to stop. Subsequent messages should indicate the status of each of the internal processes and should help identify which process stopped unexpectedly.
The Data Object Broker is abending because the Object Service Broker system administrator issued the "hrncr kill" command, or because a SIGABRT signal was sent to the hrncr supervisor process.
The Data Object Broker is abending because a signal was received that was not anticipated. The signal was likely sent explicitly from the Object Service Broker System Administrator's account, or from a user with root authority. If there is no explanation for the signal then this may indicate an internal Data Object Broker problem.
If you suspect that this is a Data Object Broker internal problem then contact TIBCO Support. Be prepared to submit a copy of the Data Object Broker log file and any core file produced as a result of this problem.
This message traces the failure of an operating system function. A subsequent message will usually indicate the effects of the failure. The errno value may be useful in determining the cause of the problem.
Consult the appropriate system programming manual for your system to determine the meaning of the errno value. Your system administrator may be needed to help diagnose the problem.
This message traces the initial detection of a failure in the Data Object Broker. A subsequent message will usually indicate the effects of the failure. This message may indicate a Data Object Broker internal problem.
If you suspect that this is a Data Object Broker internal problem then contact TIBCO Support. Be prepared to submit a copy of the Data Object Broker log file and any core file produced as a result of this problem.
This message traces the failure of an operating system function. A subsequent message will usually indicate the effects of the failure. The errno value may be useful in determining the cause of the problem.
Consult the appropriate system programming manuals for your system to determine the meaning of the errno value. The system administrator may be needed to help diagnose the problem.
This message traces the failure of an internal Data Object Broker function. A subsequent message will usually indicate the effects of the failure. This message may indicate a Data Object Broker internal problem.
If you suspect that this is a Data Object Broker internal problem then contact TIBCO Support. Be prepared to submit a copy of the Data Object Broker log file and any core file produced as a result of this problem.
This message traces the failure of an internal Data Object Broker function. A subsequent message will usually indicate the effects of the failure. This message may indicate a Data Object Broker internal problem.
If you suspect that this is a Data Object Broker internal problem then contact TIBCO Support. Be prepared to submit a copy of the Data Object Broker log file and any core file produced as a result of this problem.
This information message in the DOB log displays the communications adapter IP address and the socket port number for the listening port for all connections to the DOB. The information is displayed to assist DOB administrators debug connection problems with the DOB.
On Windows, the DOB was started as a service but an "HRNCR STOP" or "HRNCR SHUTDOWN" command was entered on the command line to shut down the DOB. This is not permitted.
This message appears when the Data Object Broker is shut down. It is an information message, indicating how many pages are still available at the redolog high-water mark of usage.
