On Jul 14, 2009, at 1:50 PM, Kory Markevich wrote:

>
>
> djencks wrote:
>> What creates the new non-working thread?  In geronimo we generally
>> don't assume anything about the relationship between threads so if  
>> you
>> want the new thread to get a particular security context you'll have
>> to install it youself.
> Just to clarify, we aren't trying to create new threads.  I just  
> assumed
> that geronimo/tomcat was doing it to service multiple connections or
> something.  Looking at the bottom of the stack dump for the  
> exception, it
> looks like a tomcat worker thread:
>
> <snip>
> at
> org 
> .apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java: 
> 286)
> at
> org 
> .apache.coyote.http11.Http11Processor.process(Http11Processor.java: 
> 845)
> at
> org.apache.coyote.http11.Http11Protocol 
> $Http11ConnectionHandler.process(Http11Protocol.java:583)
> at org.apache.tomcat.util.net.JIoEndpoint 
> $Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:619)
>
> The snipped part is all the valve, filter, controller and openejb  
> stuff,
> pretty standard.
>
> Oh, and I forgot to mention in the original post that we're using  
> 2.1.4.

good choice :-)

OK, this is weird, I've never seen a bug in this area.  What kind of  
authentication does the web app use?  Can you show the entire stack  
trace to the ejb security exception?

thanks
david jencks

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