Connector error handling

The connector logs any abnormal condition that it encounters during processing, regardless of the trace level. It writes the text to the connector log file.

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).

Connector error messages are of two types:

Table 18 lists possible initialization errors and the action you can take to remedy each one.

Table 18. Connector initialization errors

Error message Description Corrective action
An Exception occurred
attempting to bind the
ABConnectorRemote
object to the RMI
Registry using
name <name>
Exception: <error text>
Fatal error. If the ConnectorRemote
cannot be started, the channel is not
able to communicate with the
connector.
Set the ConnectorPort property correctly
in the connector application
configuration properties.


See the error text for more information.

Could not connect to the
remote object of the
ABChannel
The connector cannot connect to any
channel nodes at initialization.
Verify that:

  • The Ariba Buyer server is
    started.

  • The connector application
    configuration property Nodes
    is set correctly.
Error connecting to
remote object
<node name>,
using URL: <url>
The connector cannot connect to the
channel's remote object on the specified
Ariba Buyer node.
Set the Nodes property correctly in the
connector application configuration
properties.
Connector property not
specified: <name>
The specified property is not set. Set the named property correctly in the
connector application configuration
properties.

Table 19 lists possible run-time errors and the action you can take to remedy each one.

Table 19. Connector run-time errors

Error message Description Corrective action
Collaboration name not
found in Business Object:
<name>
The connector attempts to send a
business object that does not have
the collaboration
application-specific property set.
Set the Collaboration property correctly
in the business object-level application-
specific information in the specified
business object definition.
Connector failed to
deliver business object:
<BO name>
The gotApplEvent returns an error. Check the log files for more information.
Failed to deliver business
object: <BO name>
because the connector is
not active.
The gotApplEvent returns an error.
Attempted to deliver a business object to
an inactive connector.
Verify that the connector is active.
Connector failed to
deliver business object:
<BO name> because no
subscription was found.
The gotApplEvent returns an error. Verify that the business object is
subscribed to by a collaboration.
Invalid verb specified:
<verb> for business
object: <BO name>
The verb in a message sent to the
connector is not supported by the
business object.
Verify that:

  • The Verb parameter is set
    correctly in
    MessageConfiguration.table.

  • All supported verbs are correctly set
    in the business object definition.
The attribute <xxx> was
not found in the Business
Object <BO name>
The connector is processing a message
containing a field that does not have a
corresponding attribute in the business
object definition.
Verify that the business object
definition is correctly set up.
The Buyer Connector
does not poll. Set
the Connector
property PollFrequency
to "No" to avoid this
message.
The Ariba Buyer connector does not poll. Set the connector standard property
PollFrequency to No.
The business object
<name> is not defined
A business object definition with the
specified name cannot be found.
Create the specified business object
using the ODA.
The value specified for
attribute <name> is not a
valid type
The specified attribute in the message
object does not have the same type as
the attributes in the business object
definition.
Verify the business object definition and
recreate it using the ODA if necessary.
The attribute: <name>
was not found in
the business object
definition:
<BO name>
The attribute specified in the message
object is not in the specified business
object definition.
Verify the business object definition and
recreate it using the ODA if necessary.
An error occurred during
the processing of the
business object: <BO
name>. Exception: <error
text>
An error occurred after the connector
sent the specified business object.
Check the error text for more information.
An exception occurred
unbinding the remote
object from the RMI
Registry.Name <name>
Exception: <error text>
There was a problem unbinding the
connector's remote object from the
registry. This may prevent the connector
from binding its remote object to the
RMI registry the next time the
connector is started.
Verify the ConnectorPort property in the
connector application configuration
properties. Check the error text for
more information.


You may have to restart the system
before attempting to start the connector.

A SpecNameNotFound
exception occurred when
adding the child business
object: <child BO name>
to the business object:
<parent BO name>
The connector is attempting to add the
specified child business object to an
n-cardinality attribute of the specified
parent business object.
Verify that the cardinality is correctly set
for the parent business object.
Exception occurred
instantiating class for
type: <name>.
Exception: <error text>
The class specified in the attributes
App Spec Info could not be instantiated.
Verify that the specified class is in the
classpath.


See the error text for more information.

No String constructor
found for type: <class
name>
The class specified in the attributes
App Spec Info does not have a
constructor that accepts one
string parameter.
The class specified in the metadata
cannot be used if it does not have a
string constructor.
An error occurred
on sending
object to Channel on
node: <name>.
Exception: <error text>
The specified error occurred on sending
an object to the channel.
See the error text for more information.


Check the Ariba Buyer logs for more
information.

Reply key: <key> for
object not found in
Channel on Node:
<node name>
The connector has sent an object to the
channel with a reply key that the channel
does not have in its table.
The reply key may be invalid, or may
exist on another node. Check the logs to
see if another node has processed the
object.


The request may have timed out and
the reply key has been removed from
the table. Check the logs to verify.

An error occurred
on sending
the business object: <BO
name> to Channel. Check
the logs for more
information.
An error occurred while sending the
specified business object to the channel.
Check the logs for more information.
An error occurred
on creating
a java.util.Date object
from the String "xxx".
Locale: <locale>
The Date string does not match the
default format or the formats specified
in the DateFormats parameter in
the connector application
configuration properties.
Specify the correct format string in the
connector application configuration
properties.


See the API for
java.text.SimpleDateFormat
for information on specifying date
format strings.

The business object for
TopicName: <topic name>,
variant: <variant name>,
partition: <partition
name> is not defined
A matching business object definition
could not be found for the specified
topic name, variant and partition.
Create a matching business object
definition using the ODA.


Specify a business object prefix in the
VariantMappings connector application
configuration property.

Variant prefix not
specified for variant:
<variant name>
A prefix for the specified variant could
not be found in the VariantMappings
connector application
configuration property.
Specify a business object prefix in the
VariantMappings connector application
configuration property.

Copyright IBM Corp. 1997, 2003