RE: [POLL] Logging
Log4J. Haven't tried anything else, since Log4J works and is very adaptable by just altering configuration (no code changes). - Tatu V. > -Original Message- > From: news [mailto:[EMAIL PROTECTED] Behalf Of Bill Barker > Sent: 21. marraskuuta 2003 8:36 > To: [EMAIL PROTECTED] > Subject: Re: [POLL] Logging > > > Aside from a couple of throw-away apps (that I can't be bothered to config > :), it's Log4J all the way ;-). > > "Pitre, Russell" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > I need to use a robbust logging api for my webapp that I'm building, so > I decided I would cast a poll to get census of what everyone prefers > > > Logging, Which do you prefer? > > 1. Log4j > 2. Java.util.Logging > 3. Other > > > > Russ > > > > > - > 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]
RE: SessionListener
> > You might be able to use HttpSessionAttributeListener ...or HttpSessionBindingListener. The container calls the valueUnbound(HttpSessionBindingEvent event) when the object is removed from the session (e.g. when session is destroyed). I am using this one =) - Tatu V. > Peter Maas wrote: > > > What I actually want to do is call some destruct methods in objects > > bound to the session... > > > > P > > > > Christopher Schultz wrote: > > > >> Peter, > >> > >>> I wondered if there is a way detect somehting like a > >>> 'sessionWillBeDestroyed' event. > >>> since the sessionDestroyed method in a sessionListener seems to be > >>> called after the session was destroyed. > >> > >> > >> > >> I don't think you can 'veto' the destruction of a session, if that's > >> what you mean. All the container will do is notify you that the > >> session is in the process of being destroyed. > >> > >> -chris > >> > >> > >> - > >> 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] > > > > > > > - > 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]
RE: JSessionID problem
> > If I test this code from the Linux Tomcat Server (just typing > > http://myserver/session.jsp ) jsessionid doesn´t change each > time a refresh > > the page... > Isn't it the way it should work ? Keeping a single session > between requests ? I agree. > >And the link doesnt show jsessionid either, as should (notice the > > "encodeURL") If your browser does not block cookies, then the jsessionid is not put to the link, but to a cookie, right? Try to disable cookies and see if the sessioid appears to the link. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat + jk2 connector configuration
Hello, We have a development environment where each developer has a separate Tomcat instance to play with. Each Tomcat should listen in it's port for requests coming from the Apache front-end. The mappings for each user's Tomcat should be based on the request uri, i.e. http://www.somehost.com/user1/ means that Apache should forward the requests having 'user1' to user1's running Tomcat instance. We have this working with the "ancient" Warp- connector but we should move to jk2 because of some issues with warp. Could someone please include some example of workers2.properties/jk2.properties that would give us some hint of how to make things work. Yes, we have tried to configure things but apparently something has been missing and we are still stuck with warp :( Below is our workers2.properties (with user names replaced with more "publishable" names). Is there something missing there? Thanks a lot! workers2.properties: [logger.apache2] level=DEBUG [shm] file=/www/logs/shm.file size=1048576 # First Tomcat serving a product under tests [channel.socket:localhost:9025] port=9025 maxPort=9025 host=127.0.0.1 [ajp13:localhost:9025] channel=channel.socket:localhost:9025 [uri:/product1/*] worker1=ajp13:localhost:9025 # user1 [channel.socket:localhost:9031] port=9031 maxPort=9031 host=127.0.0.1 [ajp13:localhost:9031] channel=channel.socket:localhost:9031 [uri:/user1/*] worker1=ajp13:localhost:9031 # user2 [channel.socket:localhost:9029] port=9029 maxPort=9029 host=127.0.0.1 [ajp13:localhost:9029] channel=channel.socket:localhost:9029 [uri:/user2/*] worker1=ajp13:localhost:9029 # user3 [channel.socket:localhost:9027] port=9027 maxPort=9027 host=127.0.0.1 [ajp13:localhost:9027] channel=channel.socket:localhost:9027 [uri:/user3/*] worker1=ajp13:localhost:9027 # user4 [channel.socket:localhost:9021] port=9021 maxPort=9021 host=127.0.0.1 [ajp13:localhost:9021] channel=channel.socket:localhost:9021 [uri:/user4/*] worker1=ajp13:localhost:9021 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat + Connector issues
Hello I have two questions about Tomcat and connnectors. The front-end web server is Apache. 1.) When using Tomcat 4.1.24 and the Warp- connector, the creation of the servlet and the call to init() happens two times (even the class loading). Normally this would not be a great problem, but in my case I am starting a background scheduler thread when the servlet starts. So the result is that there are two background threads running. This is a bad thing. The first servlet loading happens when starting Tomcat and another when there is the first request to the servlet. I have checked all configurations and the webapp context is defined in one place only. When using the built-in http connector it seems to work ok, and also with JK (don't remember if jk or jk2) connector (the servlet and other classes are loaded once and the init is called once). Can anyone confirm that this really is an issue with the Warp connector? 2.) We are developing a web aplication with Apache + Tomcat and client side ssl authentication. Problems arise when we try to use the JK2 connector, because the client certificate is not found from the request. Using JK or Warp connector we have made it work but the JK2 would be the best choice for connector for other reasons. In JK connector there were some config values that enabled the propagation of SSL values (incl the client cert) to Tomcat and the web application, but those config values don't work in JK2. Does anyone know how to use and configure JK2 so that SSL information such as the client certificate is available to the web application under Tomcat? I would really appreciate any help, thanks in advance, Tatu V. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat + Connector issues
Hello I have two questions about Tomcat and connnectors. The front-end web server is Apache. 1.) When using Tomcat 4.1.24 and the Warp- connector, the creation of the servlet and the call to init() happens two times (even the class loading). Normally this would not be a great problem, but in my case I am starting a background scheduler thread when the servlet starts. So the result is that there are two background threads running. This is a bad thing. The first servlet loading happens when starting Tomcat and another when there is the first request to the servlet. I have checked all configurations and the webapp context is defined in one place only. When using the built-in http connector it seems to work ok, and also with JK (don't remember if jk or jk2) connector (the servlet and other classes are loaded once and the init is called once). Can anyone confirm that this really is an issue with the Warp connector? 2.) We are developing a web aplication with Apache + Tomcat and client side ssl authentication. Problems arise when we try to use the JK2 connector, because the client certificate is not found from the request. Using JK or Warp connector we have made it work but the JK2 would be the best choice for connector for other reasons. In JK connector there were some config values that enabled the propagation of SSL values (incl the client cert) to Tomcat and the web application, but those config values don't work in JK2. Does anyone know how to use and configure JK2 so that SSL information such as the client certificate is available to the web application under Tomcat? I would really appreciate any help, thanks in advance, Tatu V. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
