Konstantin, I apologize for my lack of information, but for an inexperienced user this can be difficult, Tomcat version and OS are easy enough, but configuration bits can be difficult, especially since a configuration can exist that is causing your problem, that you dont even know it exists.
Anyways, I believe my stress tester is working fine. I think the real problem I faced was since multiple threads are sharing the same resource(System.out), they are not all getting to print to it and some essages are getting lost. Also, I am not using an authenticator, or even a web page, I wrote a java application to connect to the tomcat server. As for the original problem, sessions were not getting lost, it was a concurrency issue within my stress tester. Thank you all for your responses On Fri, Sep 12, 2014 at 10:15 AM, Konstantin Kolinko <knst.koli...@gmail.com > wrote: > 2014-09-11 17:07 GMT+04:00 Elias Kopsiaftis <yemi...@gmail.com>: > > ok Thanks, > > > > I am using Tomcat7. I dont know much about Tomcat application > development, > > so I will research these options you gave me before responding again. > > > > Thanks again > > > As written here: > http://tomcat.apache.org/lists.html#tomcat-users > > Important: > 1. When asking questions on the list, please state your exact Tomcat > version (which is three numbers, 7.0.x or 6.0.x), your operating > system, and essential bits of your configuration. > (...) > 6. When replying, please write your text below the quoted one. > > Sessionid is usually changed when authentication succeeds. For FORM > authentication and up-to-date Tomcat 7 the change happens twice (once > login form is displayed and once authentication succeeds). At that > time the old sessionid becomes invalid. > > The session may also expire or be explicitly invalidated (e.g. during > logout). > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
