|
Error
|
Possible cause(s)
|
Resolution/Workaround
|
|
BizPulse_ERR_202
|
Problem looking up jndi resources.
|
Make sure that the parameters to connect to the database in oebpsjndi.properties are correct.
|
|
BizPulse_ERR_236
|
Problem getting connection to database.
|
Make sure that the parameters to connect to the database in oebpsdb.properties are correct.
|
|
BizPulse_ERR_237
|
Problem getting connection to database.
|
Make sure that the parameters to connect to the database in oebpsdb.properties are correct.
|
|
BizPulse_ERR_238
|
Problem creating sequence object.
|
Make sure that the parameters to connect to the database in oebpsdb.properties are correct.
|
|
BizPulse_ERR_239
|
Problem fetching next sequence number.
|
Make sure that the parameters to connect to the database in oebpsdb.properties are correct.
|
|
BizPulse_ERR_560
|
EventReader caught database access error while reading events. The database might be down or unable to access database on network.
|
BPM Events keeps trying to establish connection with the database. Make sure that the database is up and running, and it is accessible from the machine where Business Process Server is running.
|
|
BizPulse_ERR_561
|
EventReader that was reading events was unable to establish connection to database. The database might be down or unable to access database on network.
|
Make sure that the database is up and running, and it is accessible from the machine where Business Process Server is running. Stop and restart BPM Events server after bringing database up.
|
|
BizPulse_ERR_562
|
EventReader caught unexpected exception while reading events.
|
Look at the embedded message for more details and try to rectify the problem. Stop and restart BPM Events server.
|
|
BizPulse_ERR_563
|
EventReader caught database access error while evaluating event. The database might be down or unable to access database on network.
|
Make sure that the database is up and running, and it is accessible from the machine where Business Process Server is running.
|
|
BizPulse_ERR_564
|
EventReader that was evaluating event was unable to establish connection to database. The database might be down or unable to access database on network.
|
Event Reader tried to establish a connection with the database but was unable to do so. Stop and restart BPM Events server after bringing database up.
|
|
BizPulse_ERR_565
|
Application server has marked a transaction for rollback. Exception thrown while accessing database in rule application has been handled by rule application and never thrown back to BPM Events.
|
BPM Events will rollback transaction. If auto recovery is set BPM Events will continue processing events.
|
|
BizPulse_ERR_566
|
EventReader caught unexpected exception while evaluating event. Probable cause could be that rules that invoke java API has thrown unchecked exception.
|
Stop and restart BPM Events server.
|
|
BizPulse_ERR_567
|
EventReader caught BPRuntimeException exception while evaluating event.
|
BPM Events will recover from the error. If auto recovery is set BPM Events will continue processing events.
|
|
BizPulse_ERR_568
|
EventReader caught unexpected exception while recovering from event.
|
Stop and restart BPM Events server.
|
|
BizPulse_ERR_569
|
EventReader will not try to recover and process events. EventReader caught unexpected exception while evaluating event.
|
Stop and restart BPM Events server.
|