NextGen Connect 3.10.1 Released!

NextGen (Mirth) Connect 3.10.1 is now available as an appliance update and on our GitHub page. This release contains bug fixes. See the release notes for the list of fixes.

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

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

not able to start the channel

  • Filter
  • Time
  • Show
Clear All
new posts

  • not able to start the channel

    I am using Mirth and not able to start the channel with the following errors:

    [2014-11-24 09:53:05,350] ERROR ( 910): Startup recovery interrupted for channel IDX TEST connection-WW(f7adef39-53c4-458a-a1ac-e20432e7f58e)
    at java.util.concurrent.locks.AbstractQueuedSynchroni zer.doAcquireSharedInterruptibly(Unknown Source)
    at java.util.concurrent.locks.AbstractQueuedSynchroni zer.acquireSharedInterruptibly(Unknown Source)
    at java.util.concurrent.FutureTask$Sync.innerGet(Unkn own Source)
    at java.util.concurrent.FutureTask.get(Unknown Source)
    at ocessUnfinishedMessages(
    at java.util.concurrent.FutureTask$Sync.innerRun(Unkn own Source)
    at Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker( Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$ (Unknown Source)
    at Source)

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

    [2014-11-24 09:53:05,351] ERROR (com.mirth.connect.server.servlets.ChannelStatusSe rvlet:94): com.mirth.connect.donkey.server.StartException: Failed to start channel.

    at art(

    at art(

    at com.mirth.connect.donkey.server.Donkey.startChanne l(

    at com.mirth.connect.server.controllers.DonkeyEngineC ontroller.startChannel( :332)

    at com.mirth.connect.server.servlets.ChannelStatusSer vlet.doPost(

    at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)

    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)

    at org.eclipse.jetty.servlet.ServletHolder.handle(Ser

    at org.eclipse.jetty.servlet.ServletHandler.doHandle(

    at Handle(

    at Handle(

    at org.eclipse.jetty.servlet.ServletHandler.doScope(S

    at Scope(

    at Scope(

    at org.eclipse.jetty.server.handler.ScopedHandler.han dle(

    at org.eclipse.jetty.server.handler.HandlerList.handl e(

    at org.eclipse.jetty.server.handler.HandlerWrapper.ha ndle(

    at org.eclipse.jetty.server.Server.handle( :363)

    at org.eclipse.jetty.server.AbstractHttpConnection.ha ndleRequest(

    at ntent(

    at org.eclipse.jetty.server.AbstractHttpConnection$Re questHandler.content( 92)

    at org.eclipse.jetty.http.HttpParser.parseNext(HttpPa

    at org.eclipse.jetty.http.HttpParser.parseAvailable(H

    at org.eclipse.jetty.server.AsyncHttpConnection.handl e(


    at dle(

    at$1.r un(

    at Job(

    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.r un(

    at Source)
    Caused by: java.util.concurrent.CancellationException

    at java.util.concurrent.FutureTask$Sync.innerGet(Unkn own Source)

    at java.util.concurrent.FutureTask.get(Unknown Source)

    at art(

    ... 29 more
    Not sure what they are. Can you help? Thanks,

  • #2
    When your channel starts up, it will attempt to first finish any unfinished messages. You are halting the channel before that recovery can finish, which is why you see that error.

    Let your channel finish recovering messages first. If it's truly stuck on a particular message, you can stop/halt the channel, then delete the problem message, then start it back up. Unfinished messages show up in the message browser as grey/italic.
    Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

    Nicholas Rupley
    Work: 949-237-6069
    Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.

    - How do I foo?
    - You just bar.