CWYBS0001-0999: Adapter Foundation Classes
- CWYBS0001
- The adapter is starting.
- Severity
- 0 : Information
- Response
- No action is required.
- CWYBS0002
- The adapter is stopping.
- Severity
- 0 : Information
- Response
- No action is required.
- CWYBS0006
- Event manager: <insert_0> could not be initialized.
- Severity
- 40 : Stop Error
- Explanation
- There was a problem establishing resources and/or connections necessary for retrieving events from the target enterprise information system (EIS).
- Response
- Check that the target enterprise information system (EIS) for inbound events is on-line.
- CWYBS0007
- An error was encountered while polling for events: <insert_0>
- Severity
- 20 : Error
- Explanation
- The adapter was unable to detect or retrieve inbound events from the target enterprise information system (EIS).
- Response
- Check the state of the enterprise information system (EIS), and verify that the data in the event store table refers to data in the enterprise information system (EIS).
- CWYBS0010
- An error occurred during endpoint activation
- Severity
- 20 : Error
- Explanation
- This error can occur if too many endpoints are active or if invalid properties were given in the ActivationSpec.
- Response
- Check the ActivationSpec for invalid properties, and that the enterprise information system (EIS) is active.
- CWYBS0011
- Polling has started.
- Severity
- 0 : Information
- Response
- No action is required.
- CWYBS0012
- The adapter failed to start polling: <insert_0>
- Severity
- 20 : Error
- Explanation
- The adapter was unable to detect and/or retrieve inbound events from the target enterprise information system (EIS).
- Response
- Check the state of the J2EE server. The server may be low on memory or other resources.
- CWYBS0013
- The adapter has stopped polling.
- Severity
- 0 : Information
- Response
- No action is required.
- CWYBS0500
- Recovery has completed.
- Severity
- 0 : Information
- Explanation
- In-progress event recovery is complete.
- Response
- No action is required.
- CWYBS0501
- Event recovery has failed :<insert_0>
- Severity
- 20 : Error
- Response
- Check the event distribution table, the event store table, and the object in the enterprise information system (EIS) to verify that the object exists.
- CWYBS0502
- Event list could not be sent. Error: <insert_0>
- Severity
- 20 : Error
- Explanation
- The event list could not be sent to the endpoint.
- Response
- Verify that the target application is online and that the event exists in the enterprise information system (EIS).
- CWYBS0503
- Adapter could not persist events. Error: <insert_0>
- Severity
- 20 : Error
- Explanation
- The events could not be stored in the event distribution table.
- Response
- Ensure that the event distribution table exists and is in a consistent state.
- CWYBS0504
- Failed to send event. Error: <insert_0>
- Severity
- 20 : Error
- Explanation
- The event list could not be sent to the endpoint.
- Response
- Verify that the target application is online, and that the event exists in the enterprise information system (EIS).
- CWYBS0505
- Logging event before delivering to the endpoint.
- Severity
- 0 : Information
- Explanation
- Logging event before delivering to the endpoint.
- Response
- No action is required.
- CWYBS0506
- The event could not be retrieved. Error: <insert_0>
- Severity
- 20 : Error
- Explanation
- An attempt was made to retrieve the complete event from the enterprise information system (EIS), but it was unsuccessful.
- Response
- Verify that the event exists in the enterprise information system (EIS) and that the business object definition is correct and in the right location.
- CWYBS0507
- The driver class was not found in class path: <insert_0>
- Severity
- 20 : Error
- Explanation
- An attempt was made to load the driver class through reflection, but the class load failed.
- Response
- Verify that the driver class is a class for an XADataSource and it is in your class path.
- CWYBS0508
- The property for XADataSource: <insert_0> is invalid.
- Severity
- 20 : Error
- Explanation
- An attempt was made to set a value in the XADataSource, but it was unsuccessful.
- Response
- Verify that the property exists in the XADataSource.
- CWYBS0509
- A Class cast exception occurred during event delivery. Did not receive a WBIRecord.
- Severity
- 20 : Error
- Response
- The adapter code is incorrect. Verify that getObjectForEvent returns an instance of WBIRecord.
- CWYBS0510
- A Common Base Event could not be sent to the Common Event Infrastructure.
- CWYBS0511
- During recovery, a pending event could not be retrieved from the Event Store. It is in the event distribution table. EventID: <insert_0>
- Severity
- 20 : Error
- Explanation
- An event in the event distribution table is not present in the event store. This is an inconsistent state that must be manually recovered.
- Response
- Determine whether this event can be skipped. If it can be skipped, delete it from the event distribution table; otherwise you must be re-create it.
- CWYBS0512
- The event has been delivered.
- Severity
- 0 : Information
- Explanation
- An event was delivered.
- Response
- No action is required.
- CWYBS0600
- A connection to the DataSource <insert_0> was established successfully.
- Severity
- 0 : Information
- Explanation
- The given connection parameters were correct and a connection has been established with the DataSource. The adapter can proceed with relevant operations.
- Response
- No action is required
- CWYBS0601
- A connection to the DataSource <insert_0> failed with the following reason <insert_1>.
- Severity
- 0 : Information
- Explanation
- A connection to the DataSource could not be established. The given connection parameters may be incorrect.
- Response
- Check that the connection parameters are correct. Verify the connection parameters with your J2EE server administrator.
- CWYBS0602
- Adapter is attempting to prepare SQL statements in the given connection to DataSource.
- Severity
- 0 : Information
- Explanation
- Preparation of SQL statements provides more efficient database access. Adapter is attempting to prepare SQL statements.
- Response
- No action is required.
- CWYBS0603
- An attempt to prepare SQL statements was completed successfully.
- Severity
- 0 : Information
- Explanation
- An attempt to prepare SQL statements on the connection was completed successfully.
- Response
- No action is required.
- CWYBS0604
- Adapter could not prepare SQL statements. Error: <insert_0>.
- Severity
- 0 : Information
- Explanation
- An attempt to prepare SQL statements failed.
- Response
- Check the trace and correct the errors.
- CWYBS0605
- Table <insert_0> was created successfully.
- Severity
- 0 : Information
- Explanation
- The SQL query to create the table was successful and the table did not exist previously.
- Response
- No action is required.
- CWYBS0606
- Table <insert_0> already exists in the database.
- Severity
- 0 : Information
- Explanation
- The SQL query trying to create the table failed as the table already existed in the DataSource. The adapter will continue with the existing records.
- Response
- No action is required.
- CWYBS0607
- Table <insert_0> already exists in the database with <insert_1> records.
- Severity
- 0 : Information
- Explanation
- The SQL query trying to create the table failed as the table already existed in the DataSource. It will continue with the existing records.
- Response
- No action is required.
- CWYBS0608
- Adapter could not create the Table <insert_0>. Error: <insert_1>
- Severity
- 0 : Information
- Response
- Check the Schema/Table name or the connection parameters. Verify the parameters with your J2EE server administrator.
- CWYBS0609
- Adapter is attempting to create Table <insert_0>.
- Severity
- 0 : Information
- Explanation
- Adapter is trying to create the table using the given connection properties.
- Response
- No action is required.
- CWYBS0610
- BLANK
- Severity
- 0 : Information
- Explanation
- Unused Message ID reserved for Getters and Setters methods.
- Response
- No action is required.
- CWYBS0611
- BLANK
- Severity
- 0 : Information
- Explanation
- Unused Message ID reserved for Getters and Setters methods.
- Response
- No action is required.
- CWYBS0650
- An SQL Exception occurred with the message <insert_0>, while trying to <insert_1>.
- Severity
- 0 : Information
- Explanation
- The SQL query to do the above operation failed with the above mentioned message.
- Response
- Check that the table and the corresponding columns exist in the database and that the connection exists in your J2EE server. Contact your database administrator to verify the connection properties. Try again with the changed connection properties.
- CWYBS0651
- The event with event id:<insert_0> was not found in the event table.
- Severity
- 20 : Error
- Response
- Check that the table name and other connection details are correct. Also verify if the event id exists in the event table.
- CWYBS0652
- Exception occurred with the following message:<insert_0>, while trying:<insert_1>.
- Severity
- 20 : Error
- Response
- Take appropriate action based on the exception message or contact your administrator.
- CWYBS0690
- The value of the <insert_0> is: <insert_1>.
- Severity
- 20 : Error
- Explanation
- This is to trace the value stored in the property. <null> implies no value is stored.
- Response
- No user action is required.
- CWYBS0691
- Number of event records found :<insert_0>.
- Severity
- 20 : Error
- Explanation
- A query returned the specified number of event records. If zero is returned it implies no records were found matching.
- Response
- No user action is required.
- CWYBS0692
- Message:<insert_0>.
- Severity
- 20 : Error
- Explanation
- A query returned the specified number of event records. If zero is returned it implies no records were found matching.
- Response
- No user action is required.
- CWYBS0693
- Length of EVENTDATA column in EVENT Table is less than needed.
- Severity
- 20 : Error
- Explanation
- Event data of failed event is a XML text which can be more than 255 characters.
- Response
- Drop the old event table <insert_0> manually.
- CWYBS0694
- The interceptor(s) <insert_0> were not initialized correctly.
- Severity
- 20 : Error
- Explanation
- Ensure that the interceptors are placed in the class path of the Adapter.
- Response
- Ensure that the fully qualified names of the interceptors are accurate.