...
This error message can be ignored, as a automatic cleanup job of MessageHandler tries to cleanup a database table, which has not yet been created.
MessageHandler Service resuses to start with SQLException
A known bug in MH prior to version 3.4 (on Windows only!) corrupts the status database. If you encounter the following log entry in wrapper.log upon startup of MH
| No Format |
|---|
INFO | jvm 1 | 2019/05/22 09:38:19 | Exception in thread "Thread-2" java.lang.IllegalStateException: log service cannot be started: java.sql.SQLException: Table already exists: STATUS in statement [CREATE CACHED TABLE status] Query: CREATE CACHED TABLE status (participant_id VARCHAR(255) NOT NULL, filename VARCHAR(255) NOT NULL, message_id VARCHAR(255), sent_date DATETIME, received_date DATETIME, status TINYINT NOT NULL, source TINYINT NOT NULL, UNIQUE (participant_id, filename)) Parameters: []
INFO | jvm 1 | 2019/05/22 09:38:19 | at ch.admin.suis.msghandler.common.MessageHandler.startLogService(MessageHandler.java:180)
INFO | jvm 1 | 2019/05/22 09:38:19 | at ch.admin.suis.msghandler.common.MessageHandler.run(MessageHandler.java:165)
INFO | jvm 1 | 2019/05/22 09:38:19 | at java.lang.Thread.run(Thread.java:748)
STATUS | wrapper | 2019/05/22 09:38:21 | <-- Wrapper Stopped |
the following workaround gets MH going again:
- Make sure that MH is not running.
- Remove the files of the MH database from the directory 'db'. The directory is located underneath the directory configured in the config element
<workingDir dirPath="..."/>in the config.xml file. - Start MH.
MessageHandler service fails to start with signature error
...