Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

Messages not storing?

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

  • Messages not storing?

    I have Store Message Data checked in my channels....but when I double click on a channel that has processed messages in the Dashboard, I don't see any messages stored!

    I had turned on With Errors Only for a while, but then deselected that and re-deployed my channels...but no messages show up.

    Any ideas as to where to look to fix this?

    Thx!

  • #2
    Re:Messages not storing?

    Try adjusting the date range
    Chris Lang

    Comment


    • #3
      Re:Messages not storing?

      OK...I checked the Mirth logs, and found the following Derby exception (I'm running current 1.7.0 SVN build).

      Any ideas on how to fix this? Do I need to blow my Mirth db away and re-create it from scratch? I've been just updating my build, but leaving the database intact.

      Thanks!

      ....Andrzej


      ERROR 2007-10-16 11:24:26,939 [ee64705d-68ad-487f-aec2-b5ac4e0a69ff_source_connector._httpEndpoint#-1488242828.receiver.4] com.webreach.mirth.server.controllers.MessageObjec tController: could not log message: id=b3afb6ca-d39c-47a1-85d9-f3519a867ed7
      com.ibatis.common.jdbc.exception.NestedSQLExceptio n:
      --- The error occurred in derby/derby-message.xml.
      --- The error occurred while executing update.
      --- Check the INSERT IGNORE INTO MESSAGE (ID, SERVER_ID, CHANNEL_ID, SOURCE, TYPE, DATE_CREATED, VERSION, IS_ENCRYPTED, STATUS, RAW_DATA, RAW_DATA_PROTOCOL, TRANSFORMED_DATA, TRANSFORMED_DATA_PROTOCOL, ENCODED_DATA, ENCODED_DATA_PROTOCOL, CONNECTOR_NAME, ERRORS, CORRELATION_ID, CONNECTOR_MAP, CHANNEL_MAP, RESPONSE_MAP, ATTACHMENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) .
      --- Check the SQL Statement (preparation failed).
      --- Cause: java.sql.SQLException: 'ATTACHMENT' is not a column in table or VTI 'APP.MESSAGE'.
      Caused by: java.sql.SQLException: 'ATTACHMENT' is not a column in table or VTI 'APP.MESSAGE'.
      at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeUpdate(GeneralStatement.java:91)
      at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.insert(SqlMapExecutorDelegate.java:447)
      at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.in sert(SqlMapSessionImpl.java:82)
      at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.ins ert(SqlMapClientImpl.java:59)
      at com.webreach.mirth.server.controllers.MessageObjec tController.writeMessageToDatabase(MessageObjectCo ntroller.java:199)
      at com.webreach.mirth.server.controllers.MessageObjec tController.updateMessage(MessageObjectController. java:171)
      at com.webreach.mirth.server.controllers.MessageObjec tController.setStatus(MessageObjectController.java :545)
      at com.webreach.mirth.server.controllers.MessageObjec tController.setSuccess(MessageObjectController.jav a:521)
      at com.webreach.mirth.connectors.file.FileMessageDisp atcher.doDispatch(FileMessageDispatcher.java:120)
      at com.webreach.mirth.connectors.file.FileMessageDisp atcher.doSend(FileMessageDispatcher.java:213)
      at org.mule.providers.AbstractMessageDispatcher.send( AbstractMessageDispatcher.java:166)
      at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:191)
      at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:130)
      at org.mule.routing.outbound.AbstractOutboundRouter.s end(AbstractOutboundRouter.java:85)
      at org.mule.routing.outbound.FilteringMulticastingRou ter.route(FilteringMulticastingRouter.java:89)
      at org.mule.routing.outbound.OutboundMessageRouter$1. doInTransaction(OutboundMessageRouter.java:78)
      at org.mule.transaction.TransactionTemplate.execute(T ransactionTemplate.java:48)
      at org.mule.routing.outbound.OutboundMessageRouter.ro ute(OutboundMessageRouter.java:82)
      at org.mule.impl.model.DefaultMuleProxy.onCall(Defaul tMuleProxy.java:247)
      at org.mule.impl.model.seda.SedaComponent.doSend(Seda Component.java:209)
      at org.mule.impl.model.AbstractComponent.sendEvent(Ab stractComponent.java:277)
      at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:201)
      at org.mule.routing.inbound.InboundMessageRouter.send (InboundMessageRouter.java:161)
      at org.mule.routing.inbound.InboundMessageRouter.rout e(InboundMessageRouter.java:128)
      at org.mule.providers.AbstractMessageReceiver$Default InternalMessageListener.onMessage(AbstractMessageR eceiver.java:492)
      at org.mule.providers.AbstractMessageReceiver.routeMe ssage(AbstractMessageReceiver.java:271)
      at org.mule.providers.AbstractMessageReceiver.routeMe ssage(AbstractMessageReceiver.java:243)
      at com.webreach.mirth.connectors.http.HttpMessageRece iver$HttpWorker.run(HttpMessageReceiver.java:156)
      at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
      at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.runTask(ThreadPoolExecutor. java:650)
      at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(ThreadPoolExecutor.java :675)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: java.sql.SQLException: 'ATTACHMENT' is not a column in table or VTI 'APP.MESSAGE'.
      at org.apache.derby.impl.jdbc.SQLExceptionFactory.get SQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.Util.generateCsSQLExcep tion(Unknown Source)
      at org.apache.derby.impl.jdbc.TransactionResourceImpl .wrapInSQLException(Unknown Source)
      at org.apache.derby.impl.jdbc.TransactionResourceImpl .handleException(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedConnection.handleE xception(Unknown Source)
      at org.apache.derby.impl.jdbc.ConnectionChild.handleE xception(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedPreparedStatement. <init>(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedPreparedStatement2 0.<init>(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedPreparedStatement3 0.<init>(Unknown Source)
      at org.apache.derby.jdbc.Driver30.newEmbedPreparedSta tement(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedConnection.prepare Statement(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedConnection.prepare Statement(Unknown Source)
      at sun.reflect.GeneratedMethodAccessor5.invoke(Unknow n Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at com.ibatis.common.jdbc.SimpleDataSource$SimplePool edConnection.invoke(SimpleDataSource.java:958)
      at $Proxy0.prepareStatement(Unknown Source)
      at com.ibatis.sqlmap.engine.execution.SqlExecutor.pre pareStatement(SqlExecutor.java:494)
      at com.ibatis.sqlmap.engine.execution.SqlExecutor.exe cuteUpdate(SqlExecutor.java:76)
      at com.ibatis.sqlmap.engine.mapping.statement.General Statement.sqlExecuteUpdate(GeneralStatement.java:2 00)
      at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeUpdate(GeneralStatement.java:78)
      ... 31 more

      Caused by:
      ERROR 42X14: 'ATTACHMENT' is not a column in table or VTI 'APP.MESSAGE'.
      at org.apache.derby.iapi.error.StandardException.newE xception(Unknown Source)
      at org.apache.derby.impl.sql.compile.ResultColumn.bin dResultColumnByName(Unknown Source)
      at org.apache.derby.impl.sql.compile.ResultColumnList .bindResultColumnsByName(Unknown Source)
      at org.apache.derby.impl.sql.compile.InsertNode.bind( Unknown Source)
      at org.apache.derby.impl.sql.GenericStatement.prepMin ion(Unknown Source)
      at org.apache.derby.impl.sql.GenericStatement.prepare (Unknown Source)
      at org.apache.derby.impl.sql.conn.GenericLanguageConn ectionContext.prepareInternalStatement(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedPreparedStatement. <init>(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedPreparedStatement2 0.<init>(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedPreparedStatement3 0.<init>(Unknown Source)
      at org.apache.derby.jdbc.Driver30.newEmbedPreparedSta tement(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedConnection.prepare Statement(Unknown Source)
      at org.apache.derby.impl.jdbc.EmbedConnection.prepare Statement(Unknown Source)
      at sun.reflect.GeneratedMethodAccessor5.invoke(Unknow n Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at com.ibatis.common.jdbc.SimpleDataSource$SimplePool edConnection.invoke(SimpleDataSource.java:958)
      at $Proxy0.prepareStatement(Unknown Source)
      at com.ibatis.sqlmap.engine.execution.SqlExecutor.pre pareStatement(SqlExecutor.java:494)
      at com.ibatis.sqlmap.engine.execution.SqlExecutor.exe cuteUpdate(SqlExecutor.java:76)
      at com.ibatis.sqlmap.engine.mapping.statement.General Statement.sqlExecuteUpdate(GeneralStatement.java:2 00)
      at com.ibatis.sqlmap.engine.mapping.statement.General Statement.executeUpdate(GeneralStatement.java:78)
      at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelega te.insert(SqlMapExecutorDelegate.java:447)
      at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.in sert(SqlMapSessionImpl.java:82)
      at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.ins ert(SqlMapClientImpl.java:59)
      at com.webreach.mirth.server.controllers.MessageObjec tController.writeMessageToDatabase(MessageObjectCo ntroller.java:199)
      at com.webreach.mirth.server.controllers.MessageObjec tController.updateMessage(MessageObjectController. java:171)
      at com.webreach.mirth.server.controllers.MessageObjec tController.setStatus(MessageObjectController.java :545)
      at com.webreach.mirth.server.controllers.MessageObjec tController.setSuccess(MessageObjectController.jav a:521)
      at com.webreach.mirth.connectors.file.FileMessageDisp atcher.doDispatch(FileMessageDispatcher.java:120)
      at com.webreach.mirth.connectors.file.FileMessageDisp atcher.doSend(FileMessageDispatcher.java:213)
      at org.mule.providers.AbstractMessageDispatcher.send( AbstractMessageDispatcher.java:166)
      at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:191)
      at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:130)
      at org.mule.routing.outbound.AbstractOutboundRouter.s end(AbstractOutboundRouter.java:85)
      at org.mule.routing.outbound.FilteringMulticastingRou ter.route(FilteringMulticastingRouter.java:89)
      at org.mule.routing.outbound.OutboundMessageRouter$1. doInTransaction(OutboundMessageRouter.java:78)
      at org.mule.transaction.TransactionTemplate.execute(T ransactionTemplate.java:48)
      at org.mule.routing.outbound.OutboundMessageRouter.ro ute(OutboundMessageRouter.java:82)
      at org.mule.impl.model.DefaultMuleProxy.onCall(Defaul tMuleProxy.java:247)
      at org.mule.impl.model.seda.SedaComponent.doSend(Seda Component.java:209)
      at org.mule.impl.model.AbstractComponent.sendEvent(Ab stractComponent.java:277)
      at org.mule.impl.MuleSession.sendEvent(MuleSession.ja va:201)
      at org.mule.routing.inbound.InboundMessageRouter.send (InboundMessageRouter.java:161)
      at org.mule.routing.inbound.InboundMessageRouter.rout e(InboundMessageRouter.java:128)
      at org.mule.providers.AbstractMessageReceiver$Default InternalMessageListener.onMessage(AbstractMessageR eceiver.java:492)
      at org.mule.providers.AbstractMessageReceiver.routeMe ssage(AbstractMessageReceiver.java:271)
      at org.mule.providers.AbstractMessageReceiver.routeMe ssage(AbstractMessageReceiver.java:243)
      at com.webreach.mirth.connectors.http.HttpMessageRece iver$HttpWorker.run(HttpMessageReceiver.java:156)
      at org.mule.impl.work.WorkerContext.run(WorkerContext .java:290)
      at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.runTask(ThreadPoolExecutor. java:650)
      at edu.emory.mathcs.backport.java.util.concurrent.Thr eadPoolExecutor$Worker.run(ThreadPoolExecutor.java :675)
      at java.lang.Thread.run(Thread.java:595)

      Comment


      • #4
        Re:Messages not storing?

        The SVN version is not stable, you need to use the 1.6.1 db.
        Chris Lang

        Comment


        • #5
          Re:Messages not storing?

          Any idea when you think the SVN version will stabilize?

          Thanks!

          Comment


          • #6
            Re:Messages not storing?

            :-) When it is tagged as 1.7.0
            Chris Lang

            Comment


            • #7
              Re:Messages not storing?

              It is tagged as 1.7.0 in the build-bat-template file in SVN. ;-)

              But all humour aside, when do you estimate it might become more stable? Hours? Days? Weeks?

              Thanks.

              Comment


              • #8
                Re:Messages not storing?

                We're looking at 3-4 weeks for completely stable. The client is getting the most work done to it, so the server should be stable sometime this week, however no promises.

                If you are seeing issues with the database in 1.7.0 by next week, please do let us know. We do admire the brave souls that run SVN-TRUNK but just be aware that things can break daily.

                Thanks!
                Chris Lang

                Comment


                • #9
                  Re:Messages not storing?

                  Good to know...much appreciate the insight.

                  I reverted to the released 1.6.1, and then had to back off from that. The HAPI fixes that I posted have not yet been incoroporated in the build, let alone the SVN repository (as far as I know), and those are critical to me....so I'll have to live with 1.7.0 SVN for the moment.

                  Don't have the time to back-port my source tree right now.

                  I notice that there are a few new db definitions that got checked in within the last day or two, so I'll try a refresh and clean build and see if that resolves the missing column issue.

                  I understand the caveat about running SVN-TRUNK, but will take that as a compliment to my bravery. ;-)

                  Let me know when you want the ant task source.

                  Comment


                  • #10
                    Re:Messages not storing?

                    The SVN trunk is now stable. I believe the DICOM changes for derby are now fully committed and functional.
                    Brendan Haverlock | Mirth Software Engineer | Mirth Corporation

                    Comment


                    • #11
                      Re:Messages not storing?

                      There are performance enhancements that will be checked in soon and might not be completely stable yet. I would proceed with caution.
                      Chris Lang

                      Comment


                      • #12
                        Re:Messages not storing?

                        Thanks Brendan/Chris.

                        Blowing away the derby db, and redeploying the latest SVN Trunk so that it would rebuild the database resolved the missing column exception.

                        My testing seems to show that everything that I'm doing works fine at the moment...so I'll plan on sticking with this SVN build for a while, till the performance stuff gets stabilized.

                        Thanks! Appreciate your heads up on this....might keep me from hurting myself. ;-)

                        Post edited by: [email protected], at: 10/16/2007 11:19

                        Comment

                        Working...
                        X