Issue 52044

--f46d04446bc1d5bfef04af973272
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello Sebb, Milamber , All,
I investigated this issue, particularly this part of issue

> stramge error for "JMS Subscriber - 001" - Response message:
> javax.naming.NamingException: Something already bound at Elite_To_MorphoT=
rak;

I created a simple test case and tried not to cache Context and it works
fine.
and in fact it is due to the fact that we cache Context and use it by many
threads.
From this:
http://download.oracle.com/javase/jndi/tutorial/beyond/misc/sync.html

I conclude we should not do caching as it is not mandatory that context is
Thread Safe (and it's not the case for AMQ one).

Do you remember why Context were cached ? was it because of bad performance=
s
if not cached ?
There are 2 solutions for that:

   - We remove caching
   - We add an  option in GUI to let user select if Context will be cached
   or not



--=20
Cordialement.
Philippe Mouawad.
Ubik-Ing=E9nierie

--f46d04446bc1d5bfef04af973272--