Can you open a JIRA for this at https://issues.apache.org/jira/browse/ARTEMIS? Big kudos if you can also add a test to org.apache.activemq.artemis.tests.integration.jms.SimpleJNDIClientTest which reproduces the failure.
Justin ----- Original Message ----- From: "Korny Sietsma" <ko...@sietsma.com> To: users@activemq.apache.org Sent: Wednesday, July 27, 2016 8:51:54 AM Subject: javax.naming.NamingException: Something already bound at testQueue Hi - I'm doing some Artemis testing. I have a Jepsen process that spawns 10 threads, each of which connects to the same queue using the name "dynamicQueues/testQueue" And I get an exception on one of the threads: javax.naming.NamingException: Something already bound at testQueue at org.apache.activemq.artemis.jndi.ReadOnlyContext.internalBind(ReadOnlyContext.java:162) at org.apache.activemq.artemis.jndi.LazyCreateContext.lookup(LazyCreateContext.java:34) at org.apache.activemq.artemis.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:281) at org.apache.activemq.artemis.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:248) at javax.naming.InitialContext.lookup(InitialContext.java:417) This looks identical to the problem described in this thread from 2009: http://blog.gmane.org/gmane.comp.java.activemq.user/month=20090101/page=39 "Looks like a concurrency bug we should work around. In the mean time - > how about adding a synchronized block around looking up a queue in > JNDI?" I can easily avoid this - I was planning to ditch JNDI anyway - but I wonder if someone should think about fixing it... - Korny -- Kornelis Sietsma korny at my surname dot com http://korny.info .fnord { display: none !important; }