Kbase P3936: Exception : Commit of transaction 1377 failed: progress.message.broker.ei: java.io.EOFException when
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/28/2005 |
|
Status: Unverified
FACT(s) (Environment):
SonicMQ 3.0
FACT(s) (Environment):
Cloudscape Database
SYMPTOM(s):
Exception : Commit of transaction 1377 failed: progress.message.broker.ei: java.io.EOFException when starting the SonicMQ
Exception appears in console of SonicMQ
CAUSE:
You have deleted the files (there should be files Txn1377 etc. in the Broker log directory)
CAUSE:
You were using disks with cached writes and the files was not synced to disk; the end marker might be missing from the transaction files.
CAUSE:
You were using disks with cached writes or the log was on a network drive, there was a broker crash, and the recovery log was not properly synced to disk (the last few blocks never made it). On next next startup, the Broker tries to recover transactions that were in fact committed (the commit record didn't make it to disk.)
FIX:
1. Reinitialize the broker to get rid of the messages. If reinitializing the Broker does not help, you can live with them since these errors do not affect the future operation of the Broker.
2. To completely get rid of the messages, it is also possible to re-create completely the Database.