Howdy,
> public void sessionCreated(HttpSessionEvent evt) {
>
> activeSessionCount++;
> HttpSession session = evt.getSession();
...
> public void sessionDestroyed(HttpSessionEvent evt) {
> activeSessionCount--;
> logger.debug("The number of active sessions: " +
>activeSessionCount);
...
What if the container was restarted with several active sessions,
causing their serialization to disk, then deserialization when the
context starts back up, and then they timeout normally? That will give
you a negative counter.
>If I could pin point the occasion, I might solve it by now. I don't
observe
>any logs from the container during the time when the error occurs, but
I
>would like to know how set up logging messages for the problem. I don't
>know whether it is related with the container configuration. The tag
pool
>is disable.
For starters, enable the AccessLogValve so that you can see both
requests (the one that fails and the one that succeeds) and their
response codes. You can also add logging to your JSP page.
If you can't pinpoint the error yourself, it's even harder for us, as
none of us know your system as well as you do ;)
Yoav Shapira
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged. This
e-mail is intended only for the individual(s) to whom it is addressed, and may not be
saved, copied, printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your computer system
and notify the sender. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
