Common sources of error

Following are four general types of errors commonly encountered in setting up user exits, and the steps to take to correct them.

File location errors

It is crucial that the WebSphere Partner Gateway system be able to find the user exit classes. A Class Not Found exception in either log can occur if:

Additional file location problems can arise if, in a multi-box, split topology setup, the appropriate user exits are not deployed with all instances of receivers or routers, as necessary.

Resolution Make sure that the class files are properly loaded in the classpath and that the exact name and location of the user exit class files match the details specified during the upload of the XML descriptor files through the Community Console. Make sure all appropriate files exist in all appropriate places.

Handler failure errors

Failure of a preprocessing handler in the receiver component or of either type of handler in the sender component, or failure in an unpackaging, protocol processing, or packaging handler in the router component will produce an error in the appropriate logs and in the Community Console. Turning on Debug mode will produce a more detailed error report. The error will result in the message or business document not being processed further, and, in the case of an HTTP receiver preprocessing failure, a 500 response code being sent back to the initiating host.

Resolution Correct the problem in the user exit code, reload the class files, and restart the component

Processing mode errors

When a document protocol supports synchronous processing, the defined target must have a SyncCheck handler specified. If the protocol does not support synchronous processing, a postprocess handler must not be specified.

Resolution Make sure that the user exits you specify are appropriate for the defined processing mode

File update errors

You can update user exit information in the system in either of two ways:

If you update the class files, restart the appropriate components to make sure that the changes are effective. Uploading new XML descriptor files for existing user exits (assuming that the files have the same name and designate the same class) immediately changes whatever attributes and attribute values that are set. In this case, any documents that are processed after the new descriptor files are uploaded will be processed as described in those new files.

Resolution Updating class files requires a component restart to be effective; updating XML descriptor files takes effect immediately

Copyright IBM Corp. 2003, 2005