Quintin,
I noticed my userBean was set to request type scope. I changed it to session
type scope. It could explain why it was possible that the user was flushed
out of memory while the user session was still active. I expect now, that
the user will stay there untill the session times out and if this happens,
then he should simply be redirected to the login page. I will post an update
when I find out :)
Regards,
Marek
--
View this message in context: http://www.nabble.com/JPA-error-tp25092854p25095616.html
Sent from the java.net - glassfish persistence mailing list archive at Nabble.com.