com.icesoft.net.messaging.MessageServiceException: javax.naming.NamingException: Something already bound at icefacesPush

ICEsoft JIRA Issue Tracker | Deryk Sinotte | 7 years ago
  1. 0

    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.

    ICEsoft JIRA Issue Tracker | 7 years ago | Deryk Sinotte
    com.icesoft.net.messaging.MessageServiceException: javax.naming.NamingException: Something already bound at icefacesPush
  2. 0

    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.

    ICEsoft JIRA Issue Tracker | 7 years ago | Deryk Sinotte
    com.icesoft.net.messaging.MessageServiceException: javax.naming.NamingException: Something already bound at icefacesPush
  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

      Something already bound at icefacesPush

      at org.apache.activemq.jndi.ReadOnlyContext.internalBind()
    2. ActiveMQ :: Core
      ReadOnlyContext.lookup
      1. org.apache.activemq.jndi.ReadOnlyContext.internalBind(ReadOnlyContext.java:150)
      2. org.apache.activemq.jndi.LazyCreateContext.lookup(LazyCreateContext.java:36)
      3. org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:258)
      4. org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:228)
      4 frames
    3. Java RT
      InitialContext.lookup
      1. javax.naming.InitialContext.lookup(InitialContext.java:351)
      1 frame
    4. com.icesoft.net
      MessagePipeline$PublishTask.run
      1. com.icesoft.net.messaging.jms.JMSAdapter.lookUpTopic(JMSAdapter.java:514)
      2. com.icesoft.net.messaging.jms.JMSAdapter.publish(JMSAdapter.java:194)
      3. com.icesoft.net.messaging.MessagePipeline.publish(MessagePipeline.java:151)
      4. com.icesoft.net.messaging.MessagePipeline$PublishTask.run(MessagePipeline.java:189)
      4 frames
    5. Backport of JSR 166
      ThreadPoolExecutor$Worker.run
      1. edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
      2. edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
      3. edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:102)
      4. edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:215)
      5. edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
      6. edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
      6 frames
    6. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:613)
      1 frame