com.mirth.connect.donkey.server.StartException

com.mirth.connect.donkey.server.StartException: Failed to initialize JMS message consumer for destination "topic://dynamicTopics/dhl7PatientUpdateSubsc"

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web10

  • via Unknown by Saju Nair,
  • via Unknown by Saju Nair,
  • via Unknown by Unknown author,
  • Stack trace

    • com.mirth.connect.donkey.server.StartException: com.mirth.connect.donkey.server.StartException: Failed to initialize JMS message consumer for destination "topic://dynamicTopics/dhl7PatientUpdateSubsc" at com.mirth.connect.donkey.server.channel.Channel$StartTask.call(Channel.java:1880) at com.mirth.connect.donkey.server.channel.Channel$StartTask.call(Channel.java:1780) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: com.mirth.connect.donkey.server.StartException: Failed to initialize JMS message consumer for destination "topic://dynamicTopics/dhl7PatientUpdateSubsc" at com.mirth.connect.connectors.jms.JmsReceiver.onStart(JmsReceiver.java:88) at com.mirth.connect.donkey.server.channel.SourceConnector.start(SourceConnector.java:88) at com.mirth.connect.donkey.server.channel.Channel$StartTask.call(Channel.java:1858) ... 6 more Caused by: javax.naming.NamingException: scheme topic not recognized at org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:211) at javax.naming.InitialContext.lookup(InitialContext.java:392) at com.mirth.connect.connectors.jms.JmsClient.getDestination(JmsClient.java:190) at com.mirth.connect.connectors.jms.JmsReceiver.onStart(JmsReceiver.java:70) ... 8 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,