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

Receiving empty alert messages

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

  • Receiving empty alert messages

    Hi,

    The alert message will look like this:
    Mirth problem on channel: ${ChannelName}
    Time : 1211363480332
    Exception: ${Error}
    We are using Mirth 1.6.1.2750
    Error Template:
    Mirth problem on channel: ${ChannelName}
    Time : ${SYSTIME}
    Exception: ${ERROR}
    Error Matching Field:
    .*
    Event logged at that time are:
    Which were gone 1 minute 20 seconds later
    java.sql.SQLException: Listener refused the connection with the following error:
    ORA-12519, TNS:no appropriate service handler found
    The Connection descriptor used by the client was:
    <my-ip>:<my-port>:CSI

    at oracle.jdbc.driver.DatabaseError.throwSqlException (DatabaseError.java:112)
    at oracle.jdbc.driver.DatabaseError.throwSqlException (DatabaseError.java:261)
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnecti on.java:387)
    at oracle.jdbc.driver.PhysicalConnection.<init>(Physi calConnection.java:414)
    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnect ion.java:165)
    at oracle.jdbc.driver.T4CDriverExtension.getConnectio n(T4CDriverExtension.java:35)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriv er.java:801)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at com.webreach.mirth.connectors.jdbc.JdbcConnector.g etConnection(JdbcConnector.java:510)
    at com.webreach.mirth.connectors.jdbc.JdbcMessageRece iver.processMessage(JdbcMessageReceiver.java:158)
    at org.mule.providers.TransactedPollingMessageReceive r$MessageProcessorWorker.doInTransaction(Transacte dPollingMessageReceiver.java:159)
    at org.mule.transaction.TransactionTemplate.execute(T ransactionTemplate.java:72)
    at org.mule.providers.TransactedPollingMessageReceive r$MessageProcessorWorker.run(TransactedPollingMess ageReceiver.java:149)
    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(Unknown Source)

    {}
    Why do we get empty alert mail messages (20), while there was clearly something going on.

  • #2
    Re:Receiving empty alert messages

    When we changed ${Error} to ${ERROR} we can see the exception contents

    Comment


    • #3
      Re:Receiving empty alert messages

      Note that ${ChannelName} should be ${channelName}, but this feature will not be available until after 1.7.1.
      Gerald Bortis | Chief Information Officer | Mirth Corporation

      Comment


      • #4
        Re:Receiving empty alert messages

        Is it possible to format the ${SYSTIME} variable to a human readable format?

        Comment

        Working...
        X