no session cookie found

skip11

ts 5.5.2 sp3 sol 7

in servletd.log we're seeingthe following java stack trace. We also
saw it in 5.5.1.

com.interwoven.framework.auth.InvalidAuthenticationException: no session cookie found
at com.interwoven.teamsite.auth.Ticket.newOpenApi(Ticket.java:181)
at com.interwoven.teamsite.auth.Ticket.<init>(Ticket.java:47)
at com.interwoven.teamsite.auth.TicketAuthenticator.find(TicketAuthenticator.java:155)
at com.interwoven.framework.auth.AuthServlet.service(AuthServlet.java:84)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
at org.apache.tomcat.core.Handler.service(Handler.java:287)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:423)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
at java.lang.Thread.run(Thread.java:484)

this stacktrace is raised every time a user logs into TS. I opened
and issue with support months ago, but they just explained it away calling it not a problem, but not handled very well.

Has anyone else seen this ? I've tested with a variety of browsers
IE 6.0, NS, Moz, Firebird, and all exhibit thesame behavior.

BTW, the login in fine, I just want an explaination, but then I always want explainations when I see stacktraces on my
production work/staging.

Skip Barger
Credit Suisse Group
Zurich, CH

abackenr

support was right. this really is not a problem. the webdesk logs tend to be overly verbose, and this message is probably the biggest offender. this is happening when you log in to the system for the first time, or after cleaning out cookies. all this is saying is that the UI is unable to authenticate using the IWAUTH cookie, since it was not found. i believe there is a similar stack trace whenever there is an invalid or expired cookie.

so basically, the only problem here is that webdesk is really greedy with logging, but this isn't an actual authentication problem, or an indication that the system isn't functioning correctly. look forward to cleaner logs in 6.0!

ariel