com.icesoft.net.messaging.MessageServiceException

javax.naming.NamingException: Something already bound at icefacesPush

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 Deryk Sinotte,
  • via Unknown by Deryk Sinotte,
  • via Unknown by Unknown author,
  • Stack trace

    • 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

    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,