> I apologize for not researching further before asking, but I'm hoping you
> (someone) knows of the top of your head.
>
> >This is a bug in the JAAS login config file class.
> Has this been reported to Sun?
>
Yes.
> >The workaround it to have a single thread force a
> >load of the login configuration file so that when the frames all try to
> >access secured beans they don't cause the ConfigFile to be loaded
> >by multiple threads.
> Not sure what the implications of the bug are. Is the config file something
> that gets loaded into cache once? Per user, or global, or could I have the
> problem when any two people try to login at the same time? If global, is
> there a call I can put into a static block somewhere (or in the servlet init
> method) that will go ahead and load the file. If the problem occurs per
> user, this could be a huge deal, if it is global, at worst I can add it to
> the list of things to do when restarting JBoss, "login to clear threading
> errors".
>
Its loaded only once unless explicity reloaded.
> >I thought I added a synchronization that would prevent this
> >from happening.
> Where did you add this synchronization. 1) I want to make sure I have the
> right version, 2) If I do, I'll be happy to explore and see why my code
> still breaks.
>
The synchronization was removed so what your seeing is expected. You
could force a load of the auth.conf file on server startup by either creating an
mbean or a servlet that is loaded on startup that created a LoginContext.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
