> If anything it would be because of stale connections (which is why I asked > about testing).
I don't believe it has anything to do with physical database connections. It has to do with the Hibernate Session object, which we access via the EntityManager facade. You would see this exception if a lazily-fetched collection is attempted to be accessed on a closed Session. I suppose it would be possible for the Session to be dead because of an underlying database connection problem, but there should be other evidence in the logs for that situation. Without other supporting evidence for database connection problems, we should look elsewhere first. M -- 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
