activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Korny Sietsma <ko...@sietsma.com>
Subject javax.naming.NamingException: Something already bound at testQueue
Date Wed, 27 Jul 2016 13:51:54 GMT
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; }

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message