The integration channel logs error messages using the Ariba Buyer API. It logs any abnormal condition that it encounters during processing, regardless of the trace level. It writes the text to an Ariba Buyer log file located in <Ariba server root>\logs and named AribaBuyer<nodename>Log.txt; for example, AribaBuyerNode1Log.txt.
The message contains a detailed description of the condition and the outcome and may also include extra information that may aid in debugging, such as business object dumps or stack traces (for exceptions).
Channel error messages are of two types:
Channel initialization errors are usually fatal, and will prevent the Ariba Buyer node from starting. Table 20 lists possible errors and the action you can take to remedy each one.
Table 20. Channel initialization errors
Error message | Description | Corrective action |
---|---|---|
Error accessing RMI registry on port xxx |
Fatal error. If the ChannelRemote cannot be started, the connector is not able to communicate with the channel. |
Verify the ChannelPort parameter specified in Parameters.table and change it if necessary. |
Error binding ChannelRemote object at registry: <url> Exception: <message text> |
Fatal error. If the ChannelRemote cannot be started, the connector is not able to communicate with the channel. |
Verify the ChannelPort parameter specified in Parameters.table. See the Exception message for more information. |
Error initializing ChannelRemote object. Exception: <xxx> |
An error occurred when starting the integration channel's remote object. |
Verify the ChannelPort parameter specified in Parameters.table. See the Exception message for more information. |
Error creating file: xxx |
The channel receives an error when attempting to create the specified directory or file. | Verify that:
|
Table 21 lists possible run-time errors and the action you can take to remedy each one.
Table 21. Channel run-time errors
Error message | Description | Corrective action |
---|---|---|
Exception processing Message: <topic name> Exception <error text> |
The message handler receives an error when trying to send a message to the connector. | See the error text for more information. |
The specified reply key was not found in the table. Key = xxx |
The message handler receives a message with a key not found in the reply table. |
Check log files to see if specified reply key was found and processed on another node. If not, rerun the event. If a node has been stopped or shut down, the reply key will be invalid. |
Received Exception connecting to Connector remote object. Exception <error text> |
Message handler's reference to the connector is missing or invalid. | Verify that:
|
The xxx parameter is not specified. |
The specified parameter is not found in the message configuration or message definition. |
Edit the message configuration or message definition accordingly. |
xxx has a null value |
A parameter in the reply received from the connector has a null value. |
Verify that this parameter is being set correctly by the map, adapter, or collaboration. |
Message Configuration not found for <topic name> in partition: <partition name> |
A message configuration entry cannot be found for the specified topic name in the specified partition. |
Verify that the specified partition exists in MessageConfiguration.table in the integration channel directory. |
Channel parameter <xxx> not set |
The specified parameter has not been set in the integration channel section of the Parameters.table file. |
Add the parameter to Parameters.table with the correct value. |
Processing for the Message with TopicName <xxx> has exceeded the timeout interval specified |
A reply for the message with the specified topic name has not been received within the allotted time. |
Verify that the Timeout parameter for the specified topic name has been set correctly in MessageConfiguration.txt.
|
ABRequestMessage Handler not found in table for: <partition - topic name> |
A message handler cannot be found for a message with the specified topic name and partition. |
Add an entry to MessageConfiguration.table for the specified topic name and partition. |
Reply for Message with TopicName <xxx> has no data for defined PullSchema objects |
The integration channel has received a response with missing data for the specified message. | Verify that:
|