Yes, it persists with synchronous replication. I made sure to add some thread sleep time to the web application code (5000ms) just to make sure the web application wasn't beating EhCache. With DEBUG logging on I can see the EhCache activity well before the web application attempts to retrieve a proxy ticket. So, I would expect the proxy granting ticket to be present in memory for use at this point.
On Wed, Aug 28, 2013 at 3:16 PM, Tom Poage <[email protected]> wrote: > On Aug 28, 2013, at 11:08 AM, Kenneth Erard <[email protected]> > wrote: > ... > > not fix our problems, so I reverted to 2.2.0. EhCache is running > asynchronously. Log4j 1.2.17 and SLF4J 1.6.6 are > > I've been looking over the proxy protocol myself. Does the problem persist > if you switch to synchronous replication? (thinking STs here.) > > Tom. > > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
