Either the node has not been configured for the appropriate transport mechanism, or the system you are on does not have access to that transport mechanism.
Keep in mind that Object Service Broker uses IPC to communicate with a node on the same system, otherwise it chooses TCP/IP.
An inbound connection could not be accepted due to a system resource shortage. This is likely a temporary shortage that should be alleviated when other processes end, or other users logoff.
A connection could not be made to the target node. The specific reason for the failure may be indicated by an errno value that is part of the message, or by a previous message.
A connection was made to the target node, but the node rejected the logon. If this message occurs on a peer connection it may mean that the peer Data Object Broker has not been configured to expect a peer connection from the originator. It may also indicate that target node has run out of resources and is not able to accept the connection.
The Data Object Broker could not open a port on the particular transport mechanism. The specific reason for the failure may be indicated by an errno value that is part of the message, or by a previous message.
During the installation process, the installer indicated that SNA support was not available on the system. Consequently the current installation of TIBCO(r) Object Service Broker has not been linked to use the system's SNA services. The Data Object Broker, however, has been configured to use SNA to communicate with a peer Data Object Broker.
Either modify the Data Object Broker configuration so that connections to SNA nodes are not required, or (assuming that SNA services are available on the system) re-link TIBCO(r) Object Service Broker so that SNA connectivity is enabled. Refer to the Installation and Operations manual for instructions on how to re-link TIBCO(r) Object Service Broker to enable SNA connectivity.
A syntax error was detected while parsing the HCS configuration file. The offending token is included in the message along with a description of what was expected. A subsequent message should indicate the file name and line number where the problem occurred.
While scanning the HCS configuration file an invalid keyword was encountered. A subsequent message may identify where the problem occurred.
A definition in the HCS configuration file does not have a NAME attribute. A subsequent message should indicate the file name and line number where the problem occurred.
The HOST name specified in the node definition is not known at this system. The HOST name may be misspelled, or it may not be defined locally (in /etc/hosts) or at the name server.
Verify that the HOST name is spelled correctly. If the HOST name is correct then contact the system administrator to have the name defined using the appropriate facility. Adding the IP attribute to the node definition may allow you to proceed if you are simply trying to connect to a node.
A HOST attribute and an IP attribute have both been specified in the definition of the node, but the IP address does not correspond to the HOST name.
The SERVICE name specified in the node definition is not known at this system. The SERVICE name may be misspelled, or it may not be defined locally (in /etc/services) or at the name server.
Verify that the SERVICE name is spelled correctly. If the SERVICE name is correct then contact the system administrator to have the name defined using the appropriate facility. As an alternative replace the SERVICE name with an actual PORT number.
A SERVICE attribute and a PORT attribute have both been specified in the definition of the node, but the PORT number does not correspond to the SERVICE name.
The node NAME is greater than 9 characters long and no ALIAS or LU name has been given for the node. Although node names can be up to 16 characters in length, Object Service Broker requires an 8-character identifier that tags the node both internally and on administrative controls. On z/OS, this is the LU name. On Windows and Solaris, this is either the LU name (if it is given), the node NAME (if it is 8 characters or less in length), or the ALIAS.
While scanning a node definition in the HCS configuration file, the end of file was encountered. This probably means that the last attribute in the last node definition had a comma indicating there were more attributes to come.
This message traces the failure of a TCP/IP function. In most cases a subsequent message will indicate the effects of the failure (for instance, the loss of connection). The error description and/or errno value may be useful in determining TCP/IP communication problems.
This message indicates a failure of the Windows GetProcAddress function to find the indicated procedure. The Windows extended message gives additional information. Most likely cause is a corrupted DLL.
The list that fully describes all network interface configurations for the local machine cannot be obtained. This list is needed when determining if a node is local.
Contact TIBCO Support. Be prepared to submit a copy of all log files containing this message. Any Data Object Broker log file submitted should be from a Data Object Broker configured such that the ERRNOTRACE parameter has not been set N. This will ensure that the Data Object Broker log file will contain system and internal error tracing.
TCP keepalive polls can be activated by a user by using the keepalive parameter for a node in the huron.dir configuration file. On the Solaris platform TCP keepalive polls are implemented using a keepalive monitor thread and out-of-band TCP/IP messages. An error was detected when starting the monitor thread or when interfacing with the thread. Review the errno value to determine the cause of the failure.
TCP keepalive probes are enabled for a remote node by using the keepalive parameter for the definition of the node in the huron.dir configuration file. Review the errno to determine why the socket send of the keepalive probe failed.