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

Working Channel Stops & Shows as a stopped channel

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

  • Working Channel Stops & Shows as a stopped channel

    This is the error from the log.

    INFO 2008-02-20 10:53:20,194 [Thread-10] com.webreach.mirth.server.Mirth: shutting down mirth due to normal request
    INFO 2008-02-20 10:55:32,078 [Thread-0] com.webreach.mirth.server.Mirth: starting mirth server...
    ERROR 2008-02-20 10:55:45,250 [Thread-0] org.mule.impl.model.seda.SedaModel: Error starting component [6cc51cdf-d713-45aa-950d-cb2303f176f2]
    org.mule.providers.FatalConnectException: ReconnectStrategy "org.mule.providers.SingleAttemptConnectionStrateg y" failed to reconnect receiver on endpoint "jdbc://query"

    I have an outbound channel, running in production environment, it has sent 53,000 messages. Ever so often It will just stop and the above error is the error that is in the log file.

    I am running version 1.3.2 built on 1.3.07.

    Thanks for any info,
    Bobbie
Working...
X