IBM E02HRLL-G Administration Guide - Page 173
Resolving ClassNotFoundException for User Exit classes
View all IBM E02HRLL-G manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 173 highlights
Optionally, you can change the value of the attributes bcg.alertNotifications.mailFrom and bcg.alertNotifications.mailReplyTo. Resolving ClassNotFoundException for User Exit classes The ClassNotFoundException error can occur when a required class is not found for the following user exits: v Receiver user exits v Custom Actions user exit v Sender user exits If the ClassNotFoundException error occurs, verify the following information: 1. If the user exits are related to Receiver user exits, check that the corresponding jar or classes are present in either of the following folders: v /Receiver/lib/userexits v /Receiver/lib/userexists/ classes 2. If the user exits are related to the document manager, check that the corresponding jar or classes are present in the following folders: v /Router/lib/userexits v /Router/lib/userexits/classes 3. If the jar or class files for the user exits are present in the correct location, verify that the corresponding user exits shared library has the correct entries. To do this: a. Open the WebSphere Application Server Admin Console. b. Go to Environment > Shared Libraries. c. Look for BCG_RCVR_USEREXISTS and BCG_ROUTER_USEREXITS. d. Edit the shared library information in these attributes and ensure that the corresponding jars or classes are added to the class path. Reprocessing events and business documents that fail to log to the database If WebSphere Partner Gateway fails to log an event or a document status to its database, the data is placed into the DATALOGERRORQ queue for later reprocessing when the problem is resolved. To reprocess these failed events and documents, use the manual utility reprocessDbLoggingErrors.sh. This utility dequeues all the events and documents from DATALOGERRORQ and re-queues them into DATALOGQ. This enables the DocumentLogReceiver to log the events and documents into the database again. The utility stops after it processes all the existing events and documents in DATALOGERRORQ. Any events and document that fails to log will be placed into the DATALOGERRORQ again; however, this time, the utility ensures that the event or document is reprocessed only once (that is, the utility does not enter an endless loop with failing events and documents). To run the reprocessDbLoggingErrors.sh or reprocessDBLoggingErrors.bat utility: 1. Verify that the any variables are correctly defined in reprocessDbLoggingErrors.sh on any router: Chapter 17. Troubleshooting 167