Re: Tomcat 5.5 failure to deploy javac 1.6 servlet

2007-03-14 Thread Reinhard Moosauer
Hi, does your tomcat instance really use JRE 1.6 ? You can easily check in the manager app. Anyway I would suggest to always use -source 1.4 -target 1.4 for older Classes, because you avoid all possible syntax problems. Other combinations of source/target could be tested if you suspect a javac

Re: Chrooting Tomcat // Linux threading issue

2007-03-14 Thread Reinhard Moosauer
Hi, If security is your main concern, you should really consider 2.6: Technologies like AppArmor are are giving a lot of confidence. And you have intrusion detection included. And IMHO you have no long term alternative to using current and maintained software. R. Am Dienstag, 13. März 2007

Re: Is there a way to get access to request object without servlet?

2007-01-19 Thread Reinhard Moosauer
- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Reinhard Moosauer IT Beratung - To start a new

Re: Tomcat 5.5 and x64 Windows

2007-01-19 Thread Reinhard Moosauer
PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Reinhard Moosauer IT Beratung - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail

Re: Tomcat 5.5.17 protected pages JSP examples with valid user and invalid role results in msg 403.

2006-06-13 Thread Reinhard Moosauer
Hi, please consider the following: - Error 403 seems completely suitable from your words - Browsers always store Login Info until the browser windows is closed (No session here, this applies only to basic-auth!) With form auth: you can alyways provide a logout-button - If Standard-errorpage

Re: Tomcat 5.0.28 - jsp:useBean causing a jsp error

2006-06-08 Thread Reinhard Moosauer
Or even better: change class=.. to type=.. class means: this class can be instantiated type means: This attribute has been set before and should not be instantiated (List cannot anyway because its an interface) Since Tomcat 5 the JSP compiler checks this to reduce runtime errors. Am

Re: JK Sticky Session Handling with Load Balancing

2006-04-18 Thread Reinhard Moosauer
Hi, please do not mix up the tomcat cluster and apache load balancing. Sticky session means that tomcat2 is not used at all in your configuration. Only tomcat1, which created the cookie. When tomcat2 creates no session, the browser gets none and the lb-worker cannot work also. Maybe your

Re: Looking for simple file servlet with etag, range and if-range support

2006-04-13 Thread Reinhard Moosauer
Hi again, this sounds like you should use apache for that. Are you using a specific download manager on the client side? Note you can always configure tomcat to serve content outside of webapps. Just use context.xml-Configuration: http://tomcat.apache.org/tomcat-5.5-doc/deployer-howto.html --A

Re: gc tuning

2006-03-30 Thread Reinhard Moosauer
Hi, Sun's JDK contains am small Java-App called 'jconsole'. You can run it remotely after configuring your tomcat like this: http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html (Enabling JMX Remote) Consider reading the JDK-docs also. Real memory usage can be understood much better with this

Re: Classloader question

2006-03-24 Thread Reinhard Moosauer
Hi, this sounds like repackage would be a huge job. If yes, I would suggest: learn ant If not: You have to reload the apps anyway. So what do you achieve? just my 2 cents. R. Am Freitag, 24. März 2006 16:19 schrieb Fran Varin: Yes, that is the exact situation we are attempting to avoid in

Re: manager-remove/undeploy without losing sessions

2006-03-15 Thread Reinhard Moosauer
) in the manager or in the admin ? Or it is a value that need to be changed manually in server.xml or any props file ? Thanks Rodrigo Asensio -Original Message- From: Reinhard Moosauer [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 14, 2006 9:04 AM To: Tomcat Users List Subject: Re

Re: manager-remove/undeploy without losing sessions

2006-03-15 Thread Reinhard Moosauer
change the binary. Feel free to open an enhancement bug report, and feel free to add a patch. The current behaviour is correct for production sites. Peter Am 14.03.2006 um 15:03 schrieb Reinhard Moosauer: Hi List, I found something, that looked promising, but did not work

manager-remove/undeploy without losing sessions

2006-03-14 Thread Reinhard Moosauer
Hello List, recently I upgraded from tomcat 5.5.9 to 5.5.15 Since then, all my sessions are lost after a remove/install via the manager. The problem is the following: I installed a war-file, which is copied to the webapps-folder during manager-install. When I want to replace the war with a new

Re: manager-remove/undeploy without losing sessions

2006-03-14 Thread Reinhard Moosauer
) Formerly, the persisted session data survived the remove, so I could re-install the app. Please help! Reinhard Am Dienstag, 14. März 2006 13:53 schrieb Reinhard Moosauer: Hello List, recently I upgraded from tomcat 5.5.9 to 5.5.15 Since then, all my sessions are lost after a remove/install via

Re: manager-remove/undeploy without losing sessions

2006-03-14 Thread Reinhard Moosauer
a patch. The current behaviour is correct for production sites. Peter Am 14.03.2006 um 15:03 schrieb Reinhard Moosauer: Hi List, I found something, that looked promising, but did not work. Developers, please look, this could be a bug: The deploy-task has an attribute update, removes

Re: reg. custom security

2006-02-21 Thread Reinhard Moosauer
Hi Poorna, you must have access to the manager-application. Otherwise you could not deploy/restart your webapp. Don't you? If you have access to the manager-webapp, you can deploy a context.xml-file along with your realm. Please see http://yourserver:8080/manager/html/ -Install-XML config URL

c:forEach not working as expected

2006-02-13 Thread Reinhard Moosauer
Hi List, it seemed clear to me, that this construct: c:forEach items=${t.records} var=x ... (some inner logic) /c:forEach should be equivalent to this one: % for (Iterator it=t.getRecords(); it.hasNext(); ) { String x = (String)it.next(); % ... (some inner logic) %