javax.naming.NamingException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • ActiveMQ JNDI Lookup Issues
    via Stack Overflow by Rachel
    ,
  • Hibernate: Could not bind factory to JNDI
    via by Unknown author,
  • Error getting Context...
    via by 802457,
  • Gatling JMS api available for testing
    via by Jason Koch,
  • 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
    via by Saju Nair,
  • When testing our ICEpack sample application on Tomcat 6 with ActiveMQ 5.3 (I was also using Liferay but I don't think it was relevant to the basic issue), I had the following problem: INFO: Starting the ICEfaces Enterprise Push Server... Nov 27, 2009 6:44:40 PM com.icesoft.net.messaging.MessagePipeline publish SEVERE: com.icesoft.net.messaging.MessageServiceException: javax.naming.NamingException: Something already bound at icefacesPush at com.icesoft.net.messaging.jms.JMSAdapter.publish(JMSAdapter.java:198) at com.icesoft.net.messaging.MessagePipeline.publish(MessagePipeline.java:151) at com.icesoft.net.messaging.MessagePipeline$PublishTask.run(MessagePipeline.java:189) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:102) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:215) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:613) Caused by: javax.naming.NamingException: Something already bound at icefacesPush at org.apache.activemq.jndi.ReadOnlyContext.internalBind(ReadOnlyContext.java:150) at org.apache.activemq.jndi.LazyCreateContext.lookup(LazyCreateContext.java:36) at org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:258) at org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:228) at javax.naming.InitialContext.lookup(InitialContext.java:351) at com.icesoft.net.messaging.jms.JMSAdapter.lookUpTopic(JMSAdapter.java:514) at com.icesoft.net.messaging.jms.JMSAdapter.publish(JMSAdapter.java:194) ... 9 more Reverting back to ActiveMQ 5.1 allowed it to work as expected. It might be a threading issue when dynamically creating topics. From my quick search online, it may required us to synchronize our initial access to the topic so that it doesn't get automatically created and bound more than once.
    via by Deryk Sinotte,
  • 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
    via by Saju Nair,
  • When testing our ICEpack sample application on Tomcat 6 with ActiveMQ 5.3 (I was also using Liferay but I don't think it was relevant to the basic issue), I had the following problem: INFO: Starting the ICEfaces Enterprise Push Server... Nov 27, 2009 6:44:40 PM com.icesoft.net.messaging.MessagePipeline publish SEVERE: com.icesoft.net.messaging.MessageServiceException: javax.naming.NamingException: Something already bound at icefacesPush at com.icesoft.net.messaging.jms.JMSAdapter.publish(JMSAdapter.java:198) at com.icesoft.net.messaging.MessagePipeline.publish(MessagePipeline.java:151) at com.icesoft.net.messaging.MessagePipeline$PublishTask.run(MessagePipeline.java:189) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:102) at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:215) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:613) Caused by: javax.naming.NamingException: Something already bound at icefacesPush at org.apache.activemq.jndi.ReadOnlyContext.internalBind(ReadOnlyContext.java:150) at org.apache.activemq.jndi.LazyCreateContext.lookup(LazyCreateContext.java:36) at org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:258) at org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:228) at javax.naming.InitialContext.lookup(InitialContext.java:351) at com.icesoft.net.messaging.jms.JMSAdapter.lookUpTopic(JMSAdapter.java:514) at com.icesoft.net.messaging.jms.JMSAdapter.publish(JMSAdapter.java:194) ... 9 more Reverting back to ActiveMQ 5.1 allowed it to work as expected. It might be a threading issue when dynamically creating topics. From my quick search online, it may required us to synchronize our initial access to the topic so that it doesn't get automatically created and bound more than once.
    via by Deryk Sinotte,
    • javax.naming.NamingException: scheme java not recognized at org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:221) at javax.naming.InitialContext.lookup(InitialContext.java:417) at projectname.main(...)

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,