Announcement

Collapse
No announcement yet.

Could not prune database warning

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

  • Could not prune database warning

    Environment:
    Mirth 1.3.1, Java 1.5 Update 9, Windows XP Professional
    =============

    I see this warning message in mirth.log file but Mirth continues to process the incoming messages fine (processed more than 21,000 messages).

    =================

    WARN 2007-01-08 14:48:08,061 [DatabasePruner] com.webreach.mirth.server.util.DatabasePruner: could not prune database
    com.webreach.mirth.server.controllers.ControllerEx ception: java.sql.SQLException: Failed to start database 'mirthdb', see the next exception for details.
    at com.webreach.mirth.server.controllers.ChannelContr oller.getChannel(ChannelController.java:75)
    at com.webreach.mirth.server.util.DatabasePruner.prun eDatabase(DatabasePruner.java:67)
    at com.webreach.mirth.server.util.DatabasePruner.run( DatabasePruner.java:53)
    Caused by: java.sql.SQLException: Failed to start database 'mirthdb', see the next exception for details.
    at org.apache.derby.impl.jdbc.SQLExceptionFactory.get SQLException(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLExcepti on(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.newEmbedSQLExcepti on(Unknown Source)
    at org.apache.derby.impl.jdbc.Util.generateCsSQLExcep tion(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedConnection.newSQLE xception(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedConnection.bootDat abase(Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedConnection.<init>( Unknown Source)
    at org.apache.derby.impl.jdbc.EmbedConnection30.<init >(Unknown Source)
    at org.apache.derby.jdbc.Driver30.getNewEmbedConnecti on(Unknown Source)
    at org.apache.derby.jdbc.InternalDriver.connect(Unkno wn Source)
    at org.apache.derby.jdbc.AutoloadedDriver.connect(Unk nown Source)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at com.ibatis.common.jdbc.SimpleDataSource.popConnect ion(SimpleDataSource.java:580)
    at com.ibatis.common.jdbc.SimpleDataSource.getConnect ion(SimpleDataSource.java:222)
    at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTran saction.init(JdbcTransaction.java:48)
    at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTran saction.getConnection(JdbcTransaction.java:89)
    at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeQueryForList(GeneralStatement.jav a:123)
    at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.queryForList(SqlMapExecutorDelegate.java:615)
    at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.queryForList(SqlMapExecutorDelegate.java:589)
    at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.qu eryForList(SqlMapSessionImpl.java:118)
    at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.que ryForList(SqlMapClientImpl.java:95)
    at com.webreach.mirth.server.controllers.ChannelContr oller.getChannel(ChannelController.java:73)
    ... 2 more
    =================


    Any help to resolve this problem would be appreciated.

    Thanks,

  • #2
    Re: Could not prune database warning

    This warning message gets logged every 5 minutes.

    Comment


    • #3
      Re: Could not prune database warning

      For any kind of volume (over 1000 messages a day) we recommend using Postgres. Do you get the same error after restarting Mirth?

      -Chris
      Chris Lang

      Comment


      • #4
        Re: Could not prune database warning

        Chris,

        I was going to try a restart (stop and start the Mirth windows service) after 9:00 PM.

        We get more than 11,000 messages/day and our backend is SQL Server 2000. Until we have the Mirth package for SQL Server 2000, is stop and restart the workaround?

        Thanks

        Comment


        • #5
          Re: Could not prune database warning

          Stop and restart should work - this is due to an issue with Derby on Windows. After X number of messages/data stored connections can no longer be made. Interestingly enough, Derby on OS X and Linux has been able to handle 1,000,000+ messages in one session.

          -Chris
          Chris Lang

          Comment


          • #6
            Re: Could not prune database warning

            This warning message does not cause any problem processing the messages. Mirth continues to process the messages as expected but the mirth.log gets this warning every 5 minutes.

            Comment


            • #7
              Re: Could not prune database warning

              chrisl wrote:
              Stop and restart should work - this is due to an issue with Derby on Windows. After X number of messages/data stored connections can no longer be made. Interestingly enough, Derby on OS X and Linux has been able to handle 1,000,000+ messages in one session.

              -Chris
              Has this issue been resolved as of version 1.5.0.2272 for Windows?

              Comment


              • #8
                Re: Could not prune database warning

                No, this is going to be a problem with Derby until there is a new release (with Java 6 and the JavaDB, this might not be a problem, but we aren't going to force Mirth to only run on Java6).

                I would suggest using an external database if you are running into these limits. Postgre is our choice for an open-source, scalable solution to use with Mirth.
                Chris Lang

                Comment


                • #9
                  Re: Could not prune database warning

                  Is it your recommendation to use Postgres even if I'm not getting this error in the log? I get over 30,000 HL7 messages a day and in the couple of weeks I've been running Mirth the error has not appeared.

                  Am I correct in understanding that Postgres would replace Derby? Is there documentation on how to replace Derby? The Wiki and other documentation I've found outside the forum is typically empty or outdated.

                  Thanks for the reply.

                  Comment


                  • #10
                    Re: Could not prune database warning

                    If you are running Mirth with the server manager, there is a tab that allows you to point it to any other db that you want. You just need to run the createdb scripts for whichever database you are using. Otherwise, the conf folder contains the configuration files for the database.
                    Brendan Haverlock | Mirth Software Engineer | Mirth Corporation

                    Comment

                    Working...
                    X