Error handling

All messages generated by the connector are stored in a message file named BIA_EJBConnector.txt. (The name of the file is determined by the LogFileName standard connector configuration property.) Each message has a message number followed by the message:

Message number
Message text

The connector handles specific errors as described in the following sections.

ClassNotFound for proxy

An exception is raised when the connector cannot find a given remote interface in the EJB JAR file provided by the user for exchanging data with the connector. The connector logs the error, which includes the name of the class not found, and returns a FAIL code.

InstantiationException in Loader

When the connector receives the enterprise bean class name and tries to create an object of that class, an exception is raised if it cannot create the object instance. The connector logs the error, which includes the class name of the object that cannot be instantiated, and returns a FAIL code.

IIlegal AccessException in Loader or Invoker

The connector raises an exception due to invalid code or improper access (public or private) on a method.

The connector logs the error and returns a FAIL code.

NoSuchMethodException in Invoker

The connector raises an exception if a method is specified on the business object that does not exist in the corresponding enterprise bean object. Since methods are loaded dynamically, this exception is raised when the method is not found in the class.

The connector logs the error and returns a FAIL code.

InvocationTargetException in Invoker

The connector raises an exception when the EJB application (with which the connector is exchanging business objects) raises an exception.

The connector logs the error and returns a FAIL code.

Invalid argument (CXIgnore) in a method object in Invoker

The connector raises an exception when a method is included in the business object's verb ASI, but the arguments of that method have not been populated.

The connector logs the error and returns a FAIL code.

Cast failure or wrong attribute type

The connector raises an exception if an EJB object method takes or returns a different data type than what has been specified in the business object.

The connector logs the error and returns a FAIL code.

Invalid verb ASI

The connector raises an exception if the verb ASI of the business object being passed to it is formatted incorrectly or uses improper syntax. Examples of this include a verb ASI that does not contain a proper method sequence.

The connector logs the error and returns a FAIL code.

App response timeout

The connector raises an exception if it loses the connection to the Application Server where the enterprise beans are deployed or if it cannot invoke an EJB method due to a connection failure.

The connector logs the error and returns a FAIL code.

Copyright IBM Corporation 2003, 2005. All Rights Reserved.