Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@geronimo.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <24502831.post@talk.nabble.com>
Date: Wed, 15 Jul 2009 10:52:26 -0700 (PDT)
From: Kory Markevich <Kory_Markevich@ACL.com>
To: user@geronimo.apache.org
Subject: Re: EJB & Web App losing Subject
In-Reply-To: <ACDFAD78-EB02-4797-BDE2-DBE70757EF57@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <24485373.post@talk.nabble.com>
 <A6DFBC7A-4ED3-4E79-A9DB-83C461EFBAFA@yahoo.com>
 <24487458.post@talk.nabble.com>
 <3203679B-8142-4BB8-A767-B8AF8BBF3F16@yahoo.com>
 <24502397.post@talk.nabble.com>
 <ACDFAD78-EB02-4797-BDE2-DBE70757EF57@yahoo.com>


djencks wrote:
> 
> Subject subject = getSpringAuthenticatedSubject();
> ContextManager.registerSubject(subject); //if the subject is cached in  
> a session this should only happen once when the subject is first  
> authenticated/constructed.
> 
> //the following should happen on every request
> ContextManager.setCallers(subject, subject);
> try {
> //process request
> } finally {
>    ContextManager.clearCallers();
> }
> 

Our custom Spring authenticator contains calls to ContextManager.login and
setCallers.  If we need to call setCallers for every request, then that
would explain this bug.  We only call it once, and don't call clearCallers,
so the subject is staying around in the original thread but subsequent
threads never get initialized properly.

Sounds like the proper solution is just a simple filter that does the
setCallers and clearCallers.  Thanks for all the help.

-- 
View this message in context: http://www.nabble.com/EJB---Web-App-losing-Subject-tp24485373s134p24502831.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.