Hi Christopher,
I think I've fixed the problem. I did two things
1) I renamed the SessionCounter to MyCounter
2) Somehow I had commented out the
HttpSession session = request.getSession(true);
Once I had a session started everything worked (including the Tomcat Manager
sessions). I am still baffled as to why it continued to work on the
developer server after the session was commented out, but assume it was
cached somehow. I finally noticed it after rebooting the system and finding
the developer server having the same problem.
A little humbling, but a happy ending. Thanks for your help!
randy
-----Original Message-----
From: Christoph Kutzinski [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 26, 2005 2:01 AM
To: Tomcat Users List
Subject: Re: HttpSessionListener
Hi Randy,
Randy George wrote:
>Hi Will and Christopher,
>
> Good thought. I shut down Tomcat and started it again with a clean
>set of logs:
>localhost.2005-05-25.log
> .
> .
>May 25, 2005 11:22:17 AM org.apache.catalina.core.ApplicationContext log
>INFO: SessionListener: contextInitialized()
>May 25, 2005 11:27:45 AM org.apache.catalina.core.ApplicationContext log
>INFO: SessionListener: sessionCreated('BD963D7E6AACE0E2387F37919BB277FC')
>
> I interpret this to show that the listener element in web.xml is
>initialized and later a sessionCeated() method was actually called:
> .
> .
> public synchronized void sessionCreated (HttpSessionEvent se) {
> System.out.println("sessionCreated "+sessionCount);
> sessionCount++;
> }
>
>However, there is no entry in the stout log so whatever sessionCreated
>method is called it is not the one registered?
> <listener>
> <listener-class>com.test.SessionCounter</listener-class>
> </listener>
>
>
Yes that is my thought, too. There is a SessionListener initialized but
apparently not yours. You should put a log statement into the
constructor of your listener and make sure.
You didn't answer my question about deployment: do you deploy your
application on the development and the production box in the same way.
If not, you should try to do it in the same way on the devel box as you
do on the prod box and look if the problem appears on the prod box, too.
Another idea: the name (com.test.SessionCounter) of your listenere is
not very "unique". Maybe there is a conflcit with an existing class in
Tomcats shared or common folder on the production system. Are there any
other applications installed on the production tomcat?
>I also just noticed that the Tomcat WebApp Manager is showing only 0's for
>sessions regardless of how many sessions are started?
>
>
That is really strange. Are you sure that you are hitting the production
tomcat with your tests? Any other log entries which could confirm that?
greetings,
Christoph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
