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

Mirth Project | Saju Nair | 3 years ago
  1. 0

    Working channel in 2.2.1 is giving error in 3.0.0 In 2.2.1 the activemq-all-5.1.0.jar was copied in mirthconenct/lib/externals. But in 3.0.0 since there is no folder called lib,I copied the same to /server-lib/externals. While deploying the channel,its giving error. ERROR 2013-10-10 12:50:36,715 [Thread-1] com.mirth.connect.server.Mirth: http.port port is already in use: 8081 ERROR 2013-10-10 12:50:36,716 [Thread-1] com.mirth.connect.server.Mirth: https.port port is already in use: 8443 ERROR 2013-10-10 12:52:04,313 [pool-3-thread-1] com.mirth.connect.donkey.server.channel.Channel: Error stopping Source connector for channel RIS-HIS Patient Update - 34 (e86e6a5c-d09f-4132-adb6-1dd27f1df4b7). com.mirth.connect.donkey.server.StopException: Failed to close JMS connection at com.mirth.connect.connectors.jms.JmsReceiver.onStop(JmsReceiver.java:99) at com.mirth.connect.donkey.server.channel.SourceConnector.stop(SourceConnector.java:102) at com.mirth.connect.donkey.server.channel.Channel.stop(Channel.java:688) at com.mirth.connect.donkey.server.channel.Channel.access$2500(Channel.java:79) at com.mirth.connect.donkey.server.channel.Channel$StartTask.call(Channel.java:1868) 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.StopException: Failed to close the JMS connection at com.mirth.connect.connectors.jms.JmsClient.stop(JmsClient.java:148) at com.mirth.connect.connectors.jms.JmsReceiver.onStop(JmsReceiver.java:97) ... 10 more Caused by: org.apache.activemq.ConnectionClosedException: The connection is already closed at org.apache.activemq.ActiveMQConnection.checkClosed(ActiveMQConnection.java:1271) at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(ActiveMQConnection.java:1258) at org.apache.activemq.ActiveMQConnection.stop(ActiveMQConnection.java:497) at org.apache.activemq.ActiveMQConnection.close(ActiveMQConnection.java:552) at com.mirth.connect.connectors.jms.JmsClient.stop(JmsClient.java:146) ... 11 more ERROR 2013-10-10 12:52:04,426 [Thread-2] com.mirth.connect.server.controllers.DonkeyEngineController: Error deploying channel e86e6a5c-d09f-4132-adb6-1dd27f1df4b7. 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

    Mirth Project | 3 years ago | Saju Nair
    com.mirth.connect.donkey.server.StartException: com.mirth.connect.donkey.server.StartException: Failed to initialize JMS message consumer for destination "topic://dynamicTopics/dhl7PatientUpdateSubsc"
  2. 0

    Working channel in 2.2.1 is giving error in 3.0.0 In 2.2.1 the activemq-all-5.1.0.jar was copied in mirthconenct/lib/externals. But in 3.0.0 since there is no folder called lib,I copied the same to /server-lib/externals. While deploying the channel,its giving error. ERROR 2013-10-10 12:50:36,715 [Thread-1] com.mirth.connect.server.Mirth: http.port port is already in use: 8081 ERROR 2013-10-10 12:50:36,716 [Thread-1] com.mirth.connect.server.Mirth: https.port port is already in use: 8443 ERROR 2013-10-10 12:52:04,313 [pool-3-thread-1] com.mirth.connect.donkey.server.channel.Channel: Error stopping Source connector for channel RIS-HIS Patient Update - 34 (e86e6a5c-d09f-4132-adb6-1dd27f1df4b7). com.mirth.connect.donkey.server.StopException: Failed to close JMS connection at com.mirth.connect.connectors.jms.JmsReceiver.onStop(JmsReceiver.java:99) at com.mirth.connect.donkey.server.channel.SourceConnector.stop(SourceConnector.java:102) at com.mirth.connect.donkey.server.channel.Channel.stop(Channel.java:688) at com.mirth.connect.donkey.server.channel.Channel.access$2500(Channel.java:79) at com.mirth.connect.donkey.server.channel.Channel$StartTask.call(Channel.java:1868) 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.StopException: Failed to close the JMS connection at com.mirth.connect.connectors.jms.JmsClient.stop(JmsClient.java:148) at com.mirth.connect.connectors.jms.JmsReceiver.onStop(JmsReceiver.java:97) ... 10 more Caused by: org.apache.activemq.ConnectionClosedException: The connection is already closed at org.apache.activemq.ActiveMQConnection.checkClosed(ActiveMQConnection.java:1271) at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(ActiveMQConnection.java:1258) at org.apache.activemq.ActiveMQConnection.stop(ActiveMQConnection.java:497) at org.apache.activemq.ActiveMQConnection.close(ActiveMQConnection.java:552) at com.mirth.connect.connectors.jms.JmsClient.stop(JmsClient.java:146) ... 11 more ERROR 2013-10-10 12:52:04,426 [Thread-2] com.mirth.connect.server.controllers.DonkeyEngineController: Error deploying channel e86e6a5c-d09f-4132-adb6-1dd27f1df4b7. 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

    Mirth Project | 3 years ago | Saju Nair
    com.mirth.connect.donkey.server.StartException: com.mirth.connect.donkey.server.StartException: Failed to initialize JMS message consumer for destination "topic://dynamicTopics/dhl7PatientUpdateSubsc"
  3. 0

    ActiveMQ JNDI Lookup Issues

    Stack Overflow | 5 years ago | Rachel
    javax.naming.NamingException: scheme java not recognized
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Gatling JMS api available for testing

    Google Groups | 3 years ago | Jason Koch
    akka.actor.ActorInitializationException: exception during creation
  6. 0

    Hibernate: Could not bind factory to JNDI

    com.br | 1 year ago
    javax.naming.NamingException: scheme java not recognized

    2 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. javax.naming.NamingException

      scheme topic not recognized

      at org.apache.activemq.jndi.ReadOnlyContext.lookup()
    2. ActiveMQ :: Core
      ReadOnlyContext.lookup
      1. org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:211)
      1 frame
    3. Java RT
      InitialContext.lookup
      1. javax.naming.InitialContext.lookup(InitialContext.java:392)
      1 frame
    4. com.mirth.connect
      Channel$StartTask.call
      1. com.mirth.connect.connectors.jms.JmsClient.getDestination(JmsClient.java:190)
      2. com.mirth.connect.connectors.jms.JmsReceiver.onStart(JmsReceiver.java:70)
      3. com.mirth.connect.donkey.server.channel.SourceConnector.start(SourceConnector.java:88)
      4. com.mirth.connect.donkey.server.channel.Channel$StartTask.call(Channel.java:1858)
      5. com.mirth.connect.donkey.server.channel.Channel$StartTask.call(Channel.java:1780)
      5 frames
    5. Java RT
      Thread.run
      1. java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      2. java.util.concurrent.FutureTask.run(FutureTask.java:138)
      3. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      4. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      5. java.lang.Thread.run(Thread.java:662)
      5 frames