Peter, Have a look at https://sourceforge.net/tracker/index.php?func=detail&aid=482875&group_id=22866&atid=376685
I think this fix might have broken your app. The code in org.jboss.naming.ENCFactory does a synchronized(encs) when manipulating the cache, but I don't think the garbage collector will respect this? I suspect the WeakHashMap might be broken because of concurrent access. I'll do some more testing when I've had some sleep. Regards, Adrian >From: Peter Levart <[EMAIL PROTECTED]> >To: "Scott M Stark" <[EMAIL PROTECTED]>, "Scott M Stark" ><[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> >Subject: Re: [JBoss-dev] JNDI view of java:comp context from Jetty broken >Date: Fri, 30 Nov 2001 17:42:33 +0100 > >On Friday 30 November 2001 12:38, Scott M Stark wrote: > > I just looked at the latest build with the jbosstest.ear from the >testsuite > > module > > and the DebugServlet http://localhost:8080/jbosstest/DebugServlet > > is displaying the full java:comp context correctly: > > > >I tried that too and it is displaying it correctly for me too. I don't know >why it is working for that particular test app and why not for my app. So I >did a fresh checkout of jboss-all and I created a minimal jbosstest.war >composed of only the: > > DebugServlet.java, Util.java & web.xml. > >Attached to the message you will find it. Not displaying java:comp. > >Please, can you try it? Am I missing something? Can you make it display the >java:comp/env/Strings/s1 ? > > >Peter ><< jbosstest.war >> _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
