>
>
> We'd be very interested in your commenting on
> http://www.ja-sig.org/issues/browse/CAS-782 about your experience with
> the fix for that issue that should appear in 3.3.3. External
> verification is good even if it's after the fact.
>
I will try out trunk today although I don't have a good
Hal, thanks for taking the time to carefully review some of the fixes
slated for 3.3.3.
> I am also using the JPATicketRegistry with Oracle and getting lots of
> deadlock detected exceptions in the logs. We customized the webapp to handle
> the errors and there doesn't seem to be performance penal
Good catch. I added a destroy method to the HttpClient and made sure all
the beans were injected with a Spring managed instance of HttpClient so that
destroy would be guaranteed to be called (which calls the shutdown method).
I'll test it out tomorrow. The 3.3.3 release will either be Thursday or
I was looking at the changes in HttpClient slated for version 3.3.3 and I
like the idea of doing the single log out HTTP calls asynchronously because
there is a performance monitoring benchmark running against the site I
support that over-emphasizes logout performance. I haven't played with the
E
