Announcement

Collapse
No announcement yet.

Not logging messages due to key constraint

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Not logging messages due to key constraint

    A few days ago Mirth stopped logging my messages. Now I can't right click view messages and resend failed messages. I looked in the log and found this:

    ERROR 2007-07-26 13:35:48,686 [287a12d4-d1dd-4341-8b09-797dbb6ae176_source_connector._jdbcEndpoint#195122 1117.receiver.9] com.webreach.mirth.server.controllers.MessageObjec tController: could not log message: id=e2511049-c31f-41d6-87d5-6321907115eb
    com.ibatis.common.jdbc.exception.NestedSQLExceptio n:
    --- The error occurred in derby/derby-message.xml.
    --- The error occurred while applying a parameter map.
    --- Check the Message.insert-message-param.
    --- Check the statement (update failed).
    --- Cause: java.sql.SQLIntegrityConstraintViolationException: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL070524042827070' defined on 'MESSAGE'.

    Is there a way to correct this? I did clone a couple channels recently, could this have caused a channel to keep the same identity which a message is logged by?

    Post edited by: marchias, at: 07/26/2007 12:25

  • #2
    Re:Not logging messages due to key constraint

    anyone?

    Comment


    • #3
      Re:Not logging messages due to key constraint

      This is a common issue, and have been posted before.

      You've reached the max number of messages in the Derby database. You have some options:

      --> Export all the channels, remove the mirthdb folder and replace it with a new one (you can get it by downloading mirth for unix, uncompressing it).

      --> > Export all the channels, and configure mirth to use a new db (oracle, mysql, postgress, sqlserver, etc.)

      Comment


      • #4
        Re:Not logging messages due to key constraint

        Thanks I'll try the first option and let you know.

        Comment

        Working...
        X