TIBCO BusinessWorks™ ProcessMonitor scenarios when the Messages will be put on the error queue.
Article ID: KB0086046
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessWorks ProcessMonitor | - |
| Not Applicable | - |
Description
Resolution:
Messages will be put on the error queue only if the TIBCO BusinessWorks™ ProcessMonitor(BWPM) server classifies them to be not valid for processing or retry of processing while the database is running.
Examples are:
1). Invalid XML payload.
2). Unique constraint violations in the DB.
3). Referential integrity violations.
Examples of when the server automatically will retry:
1). Database connection loss.
2). JDBC timeout.
Messages will be put on the error queue if after retrying the DB connection fails or if JDBC times out. If any of the following situations are reported to the BWPM server (by the JDBC driver), the server will stop processing data and wait for the user to correct the situation and then resume:
1). Database is full.
2). Database connection becomes disconnected or the database reconnection fails.
Note: the .error queue will never automatically be read by the BWPM server. A user has to inspect the cause for each message and either remove it from the queue or move it back to the event queue.
Messages will be put on the error queue only if the TIBCO BusinessWorks™ ProcessMonitor(BWPM) server classifies them to be not valid for processing or retry of processing while the database is running.
Examples are:
1). Invalid XML payload.
2). Unique constraint violations in the DB.
3). Referential integrity violations.
Examples of when the server automatically will retry:
1). Database connection loss.
2). JDBC timeout.
Messages will be put on the error queue if after retrying the DB connection fails or if JDBC times out. If any of the following situations are reported to the BWPM server (by the JDBC driver), the server will stop processing data and wait for the user to correct the situation and then resume:
1). Database is full.
2). Database connection becomes disconnected or the database reconnection fails.
Note: the .error queue will never automatically be read by the BWPM server. A user has to inspect the cause for each message and either remove it from the queue or move it back to the event queue.
Issue/Introduction
TIBCO BusinessWorks™ ProcessMonitor scenarios when the Messages will be put on the error queue.
Feedback
Yes
No
Powered by
