Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via ICEsoft JIRA Issue Tracker by Deryk Sinotte, 1 year ago
javax.naming.NamingException: Something already bound at icefacesPush
via ICEsoft JIRA Issue Tracker by Deryk Sinotte, 2 years ago
javax.naming.NamingException: Something already bound at icefacesPush
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)	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)