AW: Long Startup Time
Hi, is your application using some listeners / load-on-startup? Fohrer -Ursprüngliche Nachricht- Von: Mike Cherichetti (Renegade Internet) [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 30. März 2005 22:56 An: Tomcat Users Betreff: Long Startup Time Hi, I'm running Tomcat 5.0.28 with JDK 1.5.0_01 on Fedora Core 3. The problem that I'm having is pretty odd. It's taking Tomcat about 30 minutes to fully start up and start accepting connections. Here's where it's getting hung up at from the startup logs: Mar 30, 2005 10:52:10 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Mar 30, 2005 11:21:03 AM org.apache.catalina.core.StandardHost getDeployer You can see that it's about 29 minutes between those two log entries. So, my question is, what is happening there that could take so long? There are no errors in the logs and once Tomcat does complete its startup stuff our application works just fine. Thanks, Mike - 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]
AW: jsvc alternatives?
Try wrapper.sourceforge.net -Ursprüngliche Nachricht- Von: Michael Kastner [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 30. Dezember 2004 08:21 An: Tomcat Users List Betreff: jsvc alternatives? Hello, it seems like jsvc runs very unstable on my linux system. Does anybody know any alternatives to jsvc? Greetings Michael Kastner - 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]
AW: AW: jsvc alternatives?
Hi, As example use wrapper to control/check your tomcat instance and set up a apache/proxy or apache/mod_jk in front of it, to serve static resources, or use mod_rewrite/mod_cache (as example). Mod_proxy provides only connection from apache to tomcat, like mod_jk too. apache 2.1 mod_proxy provides some very interesting additional features: - load balancing - http 1.1 connection pooling ( apache to backendserver ). - additional ajp connector (2.0: http, ftp only ). Scared from mod_jk, use mod_proxy, and with 2.1 you get performace of mod_jk, simply configuration of mod_proxy ( i hope ). See mailing list for more info. -Ursprüngliche Nachricht- Von: Michael Kastner [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 30. Dezember 2004 12:57 An: Tomcat Users List Betreff: Re: AW: jsvc alternatives? Hello Torsten, yep, thanks for the hint. I think I'll give it a shot. By the way, would mod_proxy be an alternative too? Greetings Michael Kastner Torsten Fohrer schrieb: Try wrapper.sourceforge.net -Ursprüngliche Nachricht- Von: Michael Kastner [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 30. Dezember 2004 08:21 An: Tomcat Users List Betreff: jsvc alternatives? Hello, it seems like jsvc runs very unstable on my linux system. Does anybody know any alternatives to jsvc? Greetings Michael Kastner - 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]
Add
subscribe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: I know this is a stupid question
Simply look at the ROOT/WEB-INF/web.xml All webapps are precompiled. ;-) Cu Fohrer -Ursprüngliche Nachricht- Von: Donald Lee [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 28. März 2004 04:59 An: [EMAIL PROTECTED] Betreff: Re: I know this is a stupid question Yes I turned off caching I even deleted the index.jsp and stopped and started tomcat. I still get the Congratulations! I can do this without specifying the index.jsp and if I specify it. I know I am looking in the right folder because like I said, I can run a test.jsp just fine and even update it without cycling tomcat. This is version 5.0.19 windows installation. It runs as a service. I installed the jk2 connector but right now IIS is turned off and I am not using it. Thanks Don From: Bryan K. Cantwell Reply-To: Tomcat Users List To: Tomcat Users List Subject: Re: I know this is a stupid question Date: Sat, 27 Mar 2004 19:34:55 -0600 Is your browser chacheing? turn it off. clear the work directory of already compiled versions too... - Original Message - From: Donald Lee To: Sent: Saturday, March 27, 2004 7:31 PM Subject: I know this is a stupid question Ok, I know this has got to be a stupid newbie question but I have searched the archives without success. What is special about the default tomcat webapps/ROOT/index.jsp? I cannot make changes to it. I tried making minor changes to it and expecting the changes to happen on a refresh; no joy. I also shutdown and restarted tomcat to get the changes to take effect; no joy. I eventually created a small test.jsp and copied the contents to it and sure enough my changes were there. made some minor changes to my test.jsp and sure enough the changes were in effect without cycling tomcat. I really would like to use index.jsp as my default page. What has this locked down? Thanks Don _ Check out MSN PC Safety Security to help ensure your PC is protected and safe. http://specials.msn.com/msn/security.asp - 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] _ Get reliable access on MSN 9 Dial-up. 3 months for the price of 1! (Limited-time offer) http://join.msn.com/?page=dept/dialuppgmarket=en-usST=1/go/o nm00200361ave/direct/01/ - 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: I know this is a stupid question
Look at ROOT/WEB-INF/web.xml. all web-apps in tomcat 4/5 distributions, are precompiled. cu Fohrer On Sunday 28 March 2004 03:31, Donald Lee wrote: Ok, I know this has got to be a stupid newbie question but I have searched the archives without success. What is special about the default tomcat webapps/ROOT/index.jsp? I cannot make changes to it. I tried making minor changes to it and expecting the changes to happen on a refresh; no joy. I also shutdown and restarted tomcat to get the changes to take effect; no joy. I eventually created a small test.jsp and copied the contents to it and sure enough my changes were there. made some minor changes to my test.jsp and sure enough the changes were in effect without cycling tomcat. I really would like to use index.jsp as my default page. What has this locked down? Thanks Don _ Check out MSN PC Safety Security to help ensure your PC is protected and safe. http://specials.msn.com/msn/security.asp - 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: Tomcat - Automatically writes a session?
tomcat sents automatically a cookie named jsessionid for session maintain to a browser. with cookies=false as a context attrribute you disable this behaviour Context path= docBase=ROOT cookies=false/ from tomcat documentation: -- cookies Set to true if you want cookies to be used for session identifier communication if supported by the client (this is the default). Set to false if you want to disable the use of cookies for session identifier communication, and rely only on URL rewriting by the application. or http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/context.html cu Torsten Fohrer On Tuesday 20 January 2004 20:58, you wrote: Verify in your JSP's .java file that sessions are really being turned off. Look to see if there is a session=pageContext.getSession() Also, I think the call to pageContext = _jspxFactory.getPageContext(. Needs to have false as the 3rd to last argument. [EMAIL PROTECTED] 1/20/04 12:39:54 PM Neal wrote: I used the tag [EMAIL PROTECTED] session=false% which does appear correct, but I'm still seeing that header: Set-Cookie: JSESSIONID=97C8777F16379B8EC2CD17273CE35C3C; Path=/ There are two reasons why I want to get rid of this: 1. I assume I'm waiting server resources holding open a session for every user, unnecessarily. 2. I've been told this may prevent Google from properly spidering the site. Can you please shed any more light on how to fix this potential issue? Probably not, but I will try... Did you clear the cookies on your browser? If the browser is saying Hi! XXX is my session ID, then, (iif that session exists), tomcat is free of saying Hi! keep your session ID, which is XXX Other than that, no idea. I have never struggled to avoid cookies. Sorry. I was only echoing something I have read in the past. Antonio Fiol Jeff Tulley ([EMAIL PROTECTED]) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com - 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]
AW: How to configure Tomcat to suppress adding port to URL??????
simply patch the URL classes from catalina/tomcat-util to remove/replace the port. cu Fohrer -Ursprüngliche Nachricht- Von: Rademacher Tobias [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 12. Februar 2003 10:26 An: '[EMAIL PROTECTED]' Betreff: How to configure Tomcat to suppress adding port to URL?? Hi Folks, is it possible to configure Tomcat 4.0 to suppress the port into the url adress (URL rewriting etc)? If yes who and in which config file? I need this due to Tomcat should run into a specical security zone and the firewall maps a specific port to my tomcat server. Therefore I would like to force Tomat not returing the Port into the URL's. Bye lot's of Thx Toby - 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]
Problem with SecurityManager
How do i configure the Security Manager to use different policies for each
host/webapp/webapp(libs/classes)?
Example:
1. Install a clean Tomcat 4.1.xx
2. Creating a simple jsp page in examples/securityTest.jsp
securityTest.jsp
---
% secure.secureClass.readPasswd() %
---
3. Create a class secure.secureClass in examples/web-inf/classes
---
package secure;
import java.io.*;
public class secureClass {
public static void readPasswd() throws Exception {
File x = new File(/etc/passwd);
x.canRead();
}
}
---
4. Adding to catalina.policy
grant file:${catalina.home}/webapps/examples/WEB-INF/classes/- {
java.io.FilePermission /etc/passwd, read;
};
5. starting tomcat with security manager
6. request securityTest.jsp = Security Exception?
what i do wrong?
Torsten Fohrer
**
* DCSI AG* Tel.: +49 7131 155 88-0 *
* Lessingstrasse 17-19 * Fax.: +49 7131 155 88-99 *
* D-74076 Heilbronn * [EMAIL PROTECTED]*
* GERMANY* http://www.dcsi.de*
**
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: New Version 4.1.18 Out of Memory Errors...continued...
have you increase the maximum memory for the jvm? with -Xmx256mb as a example. cu Torsten Fohrer On Monday 30 December 2002 17:51, you wrote: Oops, I almost forget to send out the catalina logHere it is: Dec 30, 2002 11:08:29 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Dec 30, 2002 11:08:34 AM org.apache.tomcat.util.log.CommonLogHandler log SEVERE: Caught exception executing org.apache.jk.common.SocketConnection@80f521, terminating thread java.lang.OutOfMemoryError Dec 30, 2002 11:11:59 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Dec 30, 2002 11:12:47 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Dec 30, 2002 11:13:51 AM org.apache.tomcat.util.log.CommonLogHandler log SEVERE: Caught exception executing org.apache.jk.common.SocketConnection@673ee6, terminating thread java.lang.OutOfMemoryError Dec 30, 2002 11:13:53 AM org.apache.tomcat.util.log.CommonLogHandler log SEVERE: Caught exception executing org.apache.jk.common.SocketConnection@2566c1, terminating thread java.lang.OutOfMemoryError java.lang.OutOfMemoryError java.lang.OutOfMemoryError Dec 30, 2002 11:18:51 AM org.apache.tomcat.util.log.CommonLogHandler log SEVERE: Caught exception executing org.apache.jk.common.SocketAcceptor@f63fa1, terminating thread java.lang.OutOfMemoryError Dec 30, 2002 11:21:08 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Dec 30, 2002 11:31:34 AM org.apache.tomcat.util.log.CommonLogHandler log SEVERE: Caught exception executing org.apache.jk.common.SocketConnection@71bffb, terminating thread java.lang.OutOfMemoryError Dec 30, 2002 11:32:42 AM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reducing tomcat jasper memory footprint
the a bad thing is that the jasper generated code creates for each request all string object new. So hundred unneeded String objects consuming a lot off memory. And so big pages with many poor texts without codeneeds a big amount of memory. Torsten Fohrer On Monday 30 December 2002 20:37, you wrote: Hi, I'm using Apache 1.3.26 and 3 tomcat 4.0.4 instances with AJP13 loadbalancing . Our application is a CMS where all the published articles are generated offline as JSP-Files, one jsp per article. We had hige problems with the memory footprint. Due to the fact that every jsp is generated as a class and there are about 200 new artices per day the permanent segment of the JVM heap gets filled with all the classes, and I get an OutOfMemoryError. My workaround for now is setting -XX:PermSize and --XX:MapPermSize to higher values, but this just delays application hang-up. With 64 megs of permSize our Server had an approx. uptime of 1 day now it's about 3-4 days. Is there any way to unload jsp-Files (unload the class) ? llap, julian -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat stability problem
a simply performance switche for tomcat/jsp pages is the development init-param of jasper. cu Torsten Fohrer On Friday 27 December 2002 18:59, you wrote: We're running Tomcat 4.1.12 on a dual-proc PIII with 512MB RAM. The application consists of 100,000+ HTML pages and approx. 100 jsp pages. We get approx. 60,000 page views per day. Performance is fine, but occasionally the system runs into the following problem: - when you request a jsp page in the browser, there is a delay of 5-10 seconds, then the page is loaded into the browser - even though the HTML code is complete and all images are visible, the browser still appears to be loading something (load bar is creeping) - then after approx. 30 seconds the loading stops (because of a page timeout?) - static HTML pages are not affected, they load as quickly as usual Although the problem seems to happen more frequently on busy days, it does not seem to be related to peak traffic: it has also happened at quiet times, and sometimes within an hour after a Tomcat restart (up to 4 days after a restart). Does anybody have any ideas on what is happening and how we can solve it? Some configuration details: - catalina.sh: CATALINA_OPTS=-Xmx128M (we've ordered more RAM, as soon as it has arrived we're planning to change this to -Xmx512M - server.xml: Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=80 minProcessors=10 maxProcessors=110 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=1 useURIValidationHack=false / - web.xml (on public site): session-config session-timeout10/session-timeout /session-config Thanks a lot for your help. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: 4.1.17 Problems - Possibly Coyote Connector?
This is bug in 4.1.17 which will fixed in Tomcat 4.1.18, i attach the compiled classes that fixe it. update the tomcat-coyote and it should work... On Thursday 19 December 2002 14:33, you wrote: * Luc Foisy [EMAIL PROTECTED] [1214 20:14]: The actual web application did not seem to have a problem on the front side. Everything went on as normal on 4.1.12 Pages failed to be served correctly on 4.1.17 ( they are blank ) though logging on with a new session will serve the first couple pages then start blanking. This looks like exactly what is happening to me. 4.1.12 works, 4.1.17 gives me the problem. One thing to note is that my application does not use JSP so must be a catalina or coyote issue. Are you using the stock Coyote/HTTP 1.1 connector or are you using one of the JK connectors? I am using whatever 4.1.x is set to use by default. Which I am pretty sure is the Coyote/HTTP 1.1 connectors. This might be a dumb question, but have you tried using the older http/1.1 connectors to see if the problem goes away? At least then you know it's Coyote's fault. tomcat-coyote.tgz Description: application/tgz -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: 4.1.17 Problems - Possibly Coyote Connector?
socket closed exception you will have possible for ever. that is problem of tcp/ip and not tomcatthe patch fixes that the writer the jsp pages used, isn't clean recylce for the next request. what are you getting from tomcat?. can you try it via telnet/ or with sniffer running in the background catching the http conversation.. OutOfMemory exception? On Thursday 19 December 2002 15:39, you wrote: Ack, whatever was fixed not to cause the blank pages being served seems to still have the underlying problem for me... It also occured int 4.1.12 see error at bottom I'd like to restate that this error continues to occur and the server will eventually run out of memory I am going to test the old HTTP1.1 connector now, to see if I still get the below exception... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 19, 2002 8:56 AM To: Tomcat Users List Subject: Re: 4.1.17 Problems - Possibly Coyote Connector? This is bug in 4.1.17 which will fixed in Tomcat 4.1.18, i attach the compiled classes that fixe it. update the tomcat-coyote and it should work... On Thursday 19 December 2002 14:33, you wrote: * Luc Foisy [EMAIL PROTECTED] [1214 20:14]: The actual web application did not seem to have a problem on the front side. Everything went on as normal on 4.1.12 Pages failed to be served correctly on 4.1.17 ( they are blank ) though logging on with a new session will serve the first couple pages then start blanking. This looks like exactly what is happening to me. 4.1.12 works, 4.1.17 gives me the problem. One thing to note is that my application does not use JSP so must be a catalina or coyote issue. Are you using the stock Coyote/HTTP 1.1 connector or are you using one of the JK connectors? I am using whatever 4.1.x is set to use by default. Which I am pretty sure is the Coyote/HTTP 1.1 connectors. This might be a dumb question, but have you tried using the older http/1.1 connectors to see if the problem goes away? At least then you know it's Coyote's fault. 2002-12-19 09:37:32 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Socket closed at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java: 248) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicatio nFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterC hain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.j ava:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.j ava:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:18 0) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invo keNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve .java:170) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invo keNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:17 2) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invo keNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.jav a:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invo keNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:432) at
Re: 4.1.17 Problems - Possibly Coyote Connector?
what does this servlet/page do? On Thursday 19 December 2002 18:05, you wrote: Luc Foisy wrote: It did eventually lead to an OutOfMemory exception ( at least months ago ) But as I continue to watch top I have pushed it up to tomcat using 108 megs of memory (and it doesnt go away). As this server only has 128 megs of memory, thats pushing it, and that was in the span of maybe 15 minutes. I didnt actually push it to the outofmemory state this time around, as it is quite obviously the same problem I was getting about 4 month ago when I first switched to the 4.x strain. I was hoping the newer version would have solved that issue ( and darned it, I was almost ready to deploy on production server AGAIN! I don't need the clients ripping me a new umm below orafice again! :) Having that exception printed out in the logs should not lead to any memory consumption. Useless flushing happens in Jasper, which will be removed (but not in 4.1.18, since there is no time to do a beta). You should check for other factors which could cause memory consumption (like having too many active sessions), and report if you find a part of Tomcat causing the problem. One active session. Wanna let me know other factors that I could look for??? I have no idea what goes on behind the scenes and really I am not caring much, I just want something that works. Whatever it might not be, the memory use jump happens everytime i get that exception, so whatever it is, is close by. Anyways, using the legacy HTTP1.1 connector I have not been able to reproduce the socketException after multiple people pounding on it for the last 10 minutes. That makes me happy... The legacy HTTP/1.1 connector is bad in many ways (I know, because I wrote it), and given the Jasper code, it is wrong in that particular case to swallow the exception. I don't recommend using it. Swallowed exception or not, I do not see any errors happening in my logs, nor do I see an extreme increase in memory usage. With a single session using the Coyote connector I was able to increase memory usage 100% in less that 15 minutes ( not good when I expect at least 300 sessions simultaneously ) So give yourself and your bad connector a little more credit, it doesn't blow up my server. And if its the same connector used in 3.2.x , I'll be way more than happy to use it since we have been using it for the last year and a half without any problems. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: javac Memory Leak: STATUS request
a simply way. don't set CATALINA_OPTS=-Dbuild.compiler.emacs=true restart tomcat and request a jsp page with a syntax error like following BEGIN --- % x = 10 % END jikes produce this error: org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Compiling 1 source file [javac] Found 1 syntax error in /home/tfohrer/develop/Tomcat/4.1.17/jakarta-tomcat-4.0/dist/work/Standalone/localhost/_/jikes_jsp.java: [javac] 43. x = 0 [javac] ^---^ [javac] *** Syntax: ; inserted to complete ExpressionStatement javac produce this error: Generated servlet error: [javac] Compiling 1 source file /home/tfohrer/develop/Tomcat/4.1.17/jakarta-tomcat-4.0/dist/work/Standalone/localhost/_/jikes_jsp.java:43: ';' expected x = 0 ^ /home/tfohrer/develop/Tomcat/4.1.17/jakarta-tomcat-4.0/dist/work/Standalone/localhost/_/jikes_jsp.java:43: cannot resolve symbol symbol : variable x location: class org.apache.jsp.jikes_jsp x = 0 ^ 2 errors On Thursday 19 December 2002 18:40, you wrote: Torsten, It looks like everything is working, I have set the logVerbosity level to debug, but I still can find out if it is actually using jikes or javac. Is there any way to check for sure? Here's all the log shows... JspEngine -- /index.jsp ServletPath: /index.jsp PathInfo: null RealPath: /pathtohost/httpdocs/index.jsp RequestURI: /index.jsp QueryString: null Request Params: Brandon -Original Message- From: Torsten Fohrer [mailto:[EMAIL PROTECTED]] Sent: Monday, December 16, 2002 6:13 PM To: Tomcat Users List Subject: Re: javac Memory Leak: STATUS request one question? your tomcat does run more than a day, so i assume that he is a production system. memory leak in javac is only affected, if you compile a jsp page. so? how many times, you change your jsp pages? if you don't change them, and memory usage increase. it is possible a memory leak in your application. here a simply howto to use jikes. 1. Install jikes 2. Changing conf/web.xml to following: !-- If you wish to use Jikes to compile JSP -- !-- Set the init parameter compiler to jikes. -- !-- the property -Dbuild.compiler.emacs=true when starting cat-- !-- by adding the above to your CATALINA_OPTS environment iable.-- !-- If you get an error reporting that jikes can't use UTF8 encoding, -- !-- try setting the init parameter javaEncoding to O-8859-1.-- servlet servlet-namejsp/servlet-name servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class init-param param-namecompiler/param-name param-valuejikes/param-value /init-param init-param param-namelogVerbosityLevel/param-name param-valueWARNING/param-value /init-param load-on-startup3/load-on-startup /servlet 3. Define build.compiler as above noted 4. Setting a env variable named BOOTCLASSPATH to jre/lib/rt.jar cu Torsten fohrer On Tuesday 17 December 2002 01:06, you wrote: Does anyone know how I can confirm that I am actually using jikes? I have entered all the configuration required, but sometimes when I get errors compiling, the output refers to javac still. It also seems like tomcat slowly takes more and more memory. Brandon -Original Message- From: Jeremy Joslin [mailto:[EMAIL PROTECTED]] Sent: Monday, December 16, 2002 4:56 PM To: 'Tomcat Users List' Subject: RE: javac Memory Leak: STATUS request I don't know where you can get more information about this but have you considered using jikes instead of javac? I don't know of any issues with jikes and its s much faster than javac :-) Jeremy -Original Message- From: Dan Payne [mailto:[EMAIL PROTECTED]] Sent: Monday, December 16, 2002 2:32 PM To: [EMAIL PROTECTED] Subject: javac Memory Leak: STATUS request According to the Tomcat 4.1.12 release notes there is a javac memory leak. I've searched the bug watch database at sun and have searched the web as well but am having trouble finding the latest info on this. Has it been fixed? If so, what version of the JDK? I'm using 1.4.0_01 and my productin server is crashing every 4 days with out of memory exceptions. Does anyone know where I can track this at/get more info at? Thanks a million. Ya'll have been great. -Dan -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED
Re: 4.1.17 Problems - Possibly Coyote Connector?
Please try this steps. 1. hang on catalina.out, access.log 2. request the page with the browser = something changes in logs? 3. add some System.out.println() at beginning and end of the servlet 4. request the page again with the browser = output of the System.out.println ok? On Thursday 19 December 2002 18:50, you wrote: Remy Maucherat wrote: Fabio Mengue wrote: Hello, Did not work for me. I still get the blank pages. Mine are servlet related, not JSP related. The bug can affect servlets which use a Writer. The same patch should fix it. I'm sorry... But it didn't. What can I do to help figure this out ? I'm not directly involved with the developers, so I don't know exactly what they are using. If the Writer class you said is related to HttpServletResponse, then they are using it. I don't get any output of it on the log files, I just know that request is processed, and the response is a blank page. And on the machine next to mine, connected to port 8083, everything is fine. Thanks a lot, Fabio. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [OT] RE: javac Memory Leak: STATUS request
call jikes manually on the command line and see which options he support. why do you set the encoding manually to utf-8? On Thursday 19 December 2002 20:21, you wrote: Torsten, do you know what this means? org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Compiling 1 source file [javac] use: jikes [options] [@files] file.java... [javac] For more help, try -help or -version. [javac] Error: The option -encoding is unsupported in this build. snip I've unzipped the file jikes-1.18-windows.zip to C:\jikes-1.18 I've created the environment variables: BOOTCLASSPATH=C:\j2sdk1.4.1_01\jre\lib\rt.jar JIKESPATH=C:\jikes-1.18 CATALINA_OPTS=-Dbuild.compiler.emacs=true I've added C:\jikes-1.18\bin to my PATH variable. I've edited conf/web.xml, adding the init-param compiler = jikes as shown below: servlet servlet-namejsp/servlet-name servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class init-param param-namecompiler/param-name param-valuejikes/param-value /init-param init-param param-namejavaEncoding/param-name param-valueUTF8/param-value /init-param init-param param-namelogVerbosityLevel/param-name param-valueWARNING/param-value /init-param load-on-startup3/load-on-startup /servlet Am I missing anything? I came across something about having to install IBM's ICU4J. Is this correct? Thanks -Dan -Original Message- From: Torsten Fohrer [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 19, 2002 12:02 PM To: Tomcat Users List Subject: Re: javac Memory Leak: STATUS request a simply way. don't set CATALINA_OPTS=-Dbuild.compiler.emacs=true restart tomcat and request a jsp page with a syntax error like following BEGIN --- % x = 10 % END jikes produce this error: org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: -1 in the jsp file: null Generated servlet error: [javac] Compiling 1 source file [javac] Found 1 syntax error in /home/tfohrer/develop/Tomcat/4.1.17/jakarta-tomcat-4.0/dist/work/Standalon e /localhost/_/jikes_jsp.java: [javac] 43. x = 0 [javac] ^---^ [javac] *** Syntax: ; inserted to complete ExpressionStatement javac produce this error: Generated servlet error: [javac] Compiling 1 source file /home/tfohrer/develop/Tomcat/4.1.17/jakarta-tomcat-4.0/dist/work/Standalone / localhost/_/jikes_jsp.java:43: ';' expected x = 0 ^ /home/tfohrer/develop/Tomcat/4.1.17/jakarta-tomcat-4.0/dist/work/Standalone / localhost/_/jikes_jsp.java:43: cannot resolve symbol symbol : variable x location: class org.apache.jsp.jikes_jsp x = 0 ^ 2 errors On Thursday 19 December 2002 18:40, you wrote: Torsten, It looks like everything is working, I have set the logVerbosity level to debug, but I still can find out if it is actually using jikes or javac. Is there any way to check for sure? Here's all the log shows... JspEngine -- /index.jsp ServletPath: /index.jsp PathInfo: null RealPath: /pathtohost/httpdocs/index.jsp RequestURI: /index.jsp QueryString: null Request Params: Brandon -Original Message- From: Torsten Fohrer [mailto:[EMAIL PROTECTED]] Sent: Monday, December 16, 2002 6:13 PM To: Tomcat Users List Subject: Re: javac Memory Leak: STATUS request one question? your tomcat does run more than a day, so i assume that he is a production system. memory leak in javac is only affected, if you compile a jsp page. so? how many times, you change your jsp pages? if you don't change them, and memory usage increase. it is possible a memory leak in your application. here a simply howto to use jikes. 1. Install jikes 2. Changing conf/web.xml to following: !-- If you wish to use Jikes to compile JSP -- !-- Set the init parameter compiler to jikes. -- !-- the property -Dbuild.compiler.emacs=true when starting cat-- !-- by adding the above to your CATALINA_OPTS environment iable.-- !-- If you get an error reporting that jikes can't use UTF8 encoding, -- !-- try setting the init parameter javaEncoding to O-8859-1.-- servlet servlet-namejsp/servlet-name servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class init-param param-namecompiler/param-name param-valuejikes/param-value /init-param init-param param-namelogVerbosityLevel/param-name param-valueWARNING/param-value
Re: javac Memory Leak: STATUS request
one question? your tomcat does run more than a day, so i assume that he is a production system. memory leak in javac is only affected, if you compile a jsp page. so? how many times, you change your jsp pages? if you don't change them, and memory usage increase. it is possible a memory leak in your application. here a simply howto to use jikes. 1. Install jikes 2. Changing conf/web.xml to following: !-- If you wish to use Jikes to compile JSP pages: -- !-- Set the init parameter compiler to jikes. Define -- !-- the property -Dbuild.compiler.emacs=true when starting Tomcat-- !-- by adding the above to your CATALINA_OPTS environment variable.-- !-- If you get an error reporting that jikes can't use UTF8 encoding, -- !-- try setting the init parameter javaEncoding to ISO-8859-1.-- servlet servlet-namejsp/servlet-name servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class init-param param-namecompiler/param-name param-valuejikes/param-value /init-param init-param param-namelogVerbosityLevel/param-name param-valueWARNING/param-value /init-param load-on-startup3/load-on-startup /servlet 3. Define build.compiler as above noted 4. Setting a env variable named BOOTCLASSPATH to jre/lib/rt.jar cu Torsten fohrer On Tuesday 17 December 2002 01:06, you wrote: Does anyone know how I can confirm that I am actually using jikes? I have entered all the configuration required, but sometimes when I get errors compiling, the output refers to javac still. It also seems like tomcat slowly takes more and more memory. Brandon -Original Message- From: Jeremy Joslin [mailto:[EMAIL PROTECTED]] Sent: Monday, December 16, 2002 4:56 PM To: 'Tomcat Users List' Subject: RE: javac Memory Leak: STATUS request I don't know where you can get more information about this but have you considered using jikes instead of javac? I don't know of any issues with jikes and its s much faster than javac :-) Jeremy -Original Message- From: Dan Payne [mailto:[EMAIL PROTECTED]] Sent: Monday, December 16, 2002 2:32 PM To: [EMAIL PROTECTED] Subject: javac Memory Leak: STATUS request According to the Tomcat 4.1.12 release notes there is a javac memory leak. I've searched the bug watch database at sun and have searched the web as well but am having trouble finding the latest info on this. Has it been fixed? If so, what version of the JDK? I'm using 1.4.0_01 and my productin server is crashing every 4 days with out of memory exceptions. Does anyone know where I can track this at/get more info at? Thanks a million. Ya'll have been great. -Dan -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat uptime and stability in production environments
I maintain and using three standalone tomcat servers. One of the three has a request count of 4-7 per day, and traffic 1-5.5 gb traffic per month. cu Torsten Fohrer On Friday 13 December 2002 04:23, you wrote: On Thu, 12 Dec 2002, Mike W-M wrote: Date: Thu, 12 Dec 2002 13:24:27 - From: Mike W-M [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Tomcat uptime and stability in production environments I remember someone telling me once, No wonder we're having problems - that NT box hasn't been rebooted for a week. I haven't seen any mention of it here, but wondered if anyone has any similar(ly pithy) advice to offer on matters of Tomcat / Java stability and uptime. Is one sensible to plan to restart a production Tomcat every night, or foolish if you plan to do it every month? Do JVMs eat more and more memory unless they're restarted? I'm planning to deploy on Linux, but it'd be interesting to see how opinion varies by platform. Although I regularly reloaded my Tomcat-based app (mostly to add new features), I had the luxury of managing one Linux-based server that stayed up for over 400 days (i.e. well over a year) without a reboot -- and we only had to then because the machine was being moved to a new power plug at the ISP's co-lo site :-). More seriously, the precise behavior is pretty dependent on exactly which versions of JDK and Tomcat you're using, as well as any possible memory leaks in your app, or the libraries it uses (JDBC drivers can be notorious). I'd probably start with a weekly cycle on a heavily used app, but monitor things to see if more often or less often would be appropriate. Ta. Mike. Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PATCH] Fixes TagHandlerPool Size patch
Adding Integer to String
Index: Generator.java
===
RCS file:
/home/cvspublic/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Generator.java,v
retrieving revision 1.127
diff -u -w -b -r1.127 Generator.java
--- Generator.java 16 Nov 2002 04:20:10 - 1.127
+++ Generator.java 18 Nov 2002 19:38:47 -
@@ -660,7 +660,7 @@
for (int i=0; itagHandlerPoolNames.size(); i++) {
out.printin((String) tagHandlerPoolNames.elementAt(i));
out.print( = new org.apache.jasper.runtime.TagHandlerPool();
-out.print(ctxt.getOptions().getTagPoolSize());
+out.print(Integer.toString(ctxt.getOptions().getTagPoolSize()));
out.println(););
}
out.popIndent();
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: FW: Problem using Https connection on tomcat 4 jdk 1.4
how do you connecting to the other servlet? Torsten On Monday 18 November 2002 21:16, Ritu Kumar wrote: Hi, I am using tomcat 4.1.12 jdk 1.4. I am having problem using HTTPS as a protocol to connect to another servlet. ( No problem if I use HTTP protocol) I do not get any errors, but the code seems to hang. If I use tomcat 4.1.12 jdk 1.3 , the same code works fine. Any idea why this could be happining ? Ritu Kumar 703-464-5379 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: eth0 ip, not lo ip
if you use jdk 1.4 and above, look at java.net.NetworkInterface: NetworkInterface.getByName( eth0 ); should do it, if i read the docu rights, that's it. Torsten Fohrer On Saturday 16 November 2002 10:54, RXZ JLo wrote: Hi InetAddress.getLocalHost().getHostAddress() this is returning the lo interface's ip(127...), i want the eth0 interface's ip. Where and what configuration should I change for this? Thanks, Rf. __ Do you Yahoo!? Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: A long classpath list
if i remember right, tomcat 4 ignores the classpath. place classes simply in the (common or shared)/classes read more under: http://jakarta.apache.org/tomcat/tomcat-4.0-doc/class-loader-howto.html On Saturday 16 November 2002 21:12, chasee wrote: Hello all, the class loader of my tomcat stand-alone server (jakarta4.0.4) has problems finding classes. it gives a java.lang.NoClassDefFoundError. I checked the classpath environment variable using echo %classpath%. It is properly set. The only thing I have doubt about is my classpath is way too long with 20 lines also. (in the command window of a width of 80 chars). Would that affect the behavior of the server in any way? thanks, Chasee - Do you Yahoo!? Yahoo! Web Hosting - Let the expert host your site -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
AW: JDBC Policy connection problem
-Ursprüngliche Nachricht-
Von: Jacob Kjome [mailto:hoju;visi.com]
Gesendet: Freitag, 15. November 2002 15:16
An: Tomcat Users List
Betreff: Re: JDBC Policy connection problem
Can you connect to your MySQL server via a basic application
started with
the java command rather than trying to do it within the
container? You
should do this to make sure it works first.
Jake
At 12:21 AM 11/15/2002 -0800, you wrote:
I am having some issues with trying to use my JDBC driver to
connect to a
mySQL server. I get the following error in my catalina.out file:
java.sql.SQLException: Cannot connect to MySQL server on
dbox.dnsalias.net:3306. Is there a MySQL server running on the
machine/port you are trying to connect to?
(java.security.AccessControlException)
Yet, there most certainly is a server running at that
location. In fact, I
dont get this error when I start tomcat without the
-security option. This
obviously narrows the problem down to a policy setting. So I
added the
following grant (based on a sample that was commented out in
catalina.policy:
grant codeBase
file:/usr/share/tomcat4/webapps/bookstore/WEB-INF/lib/mysql-
connector-java-2.0.14-bin.jar!/-
{
permission java.net.SocketPermission dbox.dnsalias.net:3306,
connect;
};
I've restarted the server with this added but it still gives me the error
message shown earlier when I try to establish the connection. Any idea's
what I should change this grant to? Or if there is another one I need to
add?
--
Trevor MacPhail
--
To unsubscribe, e-mail:
mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail:
mailto:tomcat-user-help;jakarta.apache.org
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: can write to / not /var frpm jsp/servlet
how do you mount the other partition? On Friday 15 November 2002 18:13, Brendon Mosher wrote: I have run accross an unusual problem. I am running Linux and am able to write to any directory in the same partition as / from a servlet or jsp. However, if i try and write from a servlet or jsp to a location in any other partition on the machine (/var, /usr, /home) it fails. I have checked, and it is not a file permission problem as i have set the dirs to full rwx access when testing. I am not running with the optional -security option, so I'm ruling out catalina.policy issues as well. Does anyone have any idea what could be causing this, it's been driving me craxy for the last day. Thanks in advance for any help, Brendon -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: Cahrset problem
some tips from me
1. mask non standart characters with html entitys like nbsp; that you display
in html pages, if there exist some one.
2. setting response contentType, with % page contentType=
3. adding to the head of your html page
meta http-equiv=Content-Type content=text/html; charset=iso-8859-15
4. test different browsers
5. does the browser have fonts with the characters?
which browser you use?
On Sunday 15 December 2002 09:23, Galbayar Dorjgotov wrote:
hi all.
i have one problem. My JSP's enconding is windows-1251 and have a form.
i'm wrote cyrillic characters and submit
when i reading textfield value use getParameter() method it returns
what's the matter?
MY JSP is
% page contentType=text/html; charset=windows-1251 language=java
import=java.io.* errorPage= %
html
head
titleUntitled Document/title
/head
body
%
String a1=request.getParameter(textfield);
out.println(a1);
if (a1!=null){
InputStreamReader a=new InputStreamReader(new
ByteArrayInputStream(a1.getBytes()),windows-1251);
int gg=0;
gg=a.read();
out.println((char)gg);
a.close();
}
%
form name=form1 method=post action=
input type=text name=textfield
input type=submit name=Submit value=Submit
/form
/body
/html
--
To unsubscribe, e-mail:
mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional
commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: remove the need for :8443 in URLs needing https:
how do you run tomcat on port 8443 or 443, with the official tomcat distribtion you root rights for serving content on port 443 under linux. cu Torsten Fohrer On Wednesday 13 November 2002 01:24, Pae Choi wrote: That is wha the connector is for. Pae - Original Message - From: Qmail List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 1:21 PM Subject: remove the need for :8443 in URLs needing https: Hello, It is more difficult to re-write urls as: https://www.domain.com:8443/index.jsp as opposted to https://www.domain.com/index.jsp How can I configure Tomcat (and/or underlying Unix box) to not need the :8443 explicit port reference in the url? I tried changing the https /etc/services entry to port 8443 instead of 443, but no luck. Regards -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Re: Port redirection on Tomcat standalone
which redirectPort have you stay in your normal 8080 tomcat connector config? On Wednesday 13 November 2002 23:57, Michal Kreglewski wrote: Hi, I've got a problem with port redirection on Tomcat 4.1.12 standalone. I've enabled SSL in server.xml and it works fine. But then I put the following in web.xml: security-constraint web-resource-collection web-resource-nameMy Servlet/web-resource-name url-pattern/myServlet/url-pattern /web-resource-collection auth-constraint role-namemyRole/role-name /auth-constraint user-data-constraint transport-guaranteeCONFIDENTIAL/transport-guarantee /user-data-constraint /security-constraint login-config auth-methodFORM/auth-method realm-nameDyplom application/realm-name form-login-config form-login-page/login.jsp/form-login-page form-error-page/error.jsp/form-error-page /form-login-config /login-config security-role role-namemyRole/role-name /security-role And now I expect that invoking http://localhost:8080/myApp/myServlet will redirect me to login.jsp page over HTTPS. And that works ok, but only if Tomcat works on 80 and 443 ports. Otherwise my browser (IE 6.0) only asks me to accept the server certificate and then it can't connect to the server. Is there a way to make it work on other ports (for example on default 8080 and 8443)? Mind, that when I ommit auth-constraint tag it works as it should - MyServlet is invoked over HTTPS. Thanks for any help. Michal -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: remove the need for :8443 in URLs needing https:
i run tomcat on port '80' and '443' without root rights Torsten On Thursday 14 November 2002 22:51, Turner, John wrote: You can run Tomcat as root and have it listen on 443, as well as port 80. This is definitely possible, though some people try to avoid running web services as root for security reasons. John -Original Message- From: [EMAIL PROTECTED] [mailto:TFohrer;t-online.de] Sent: Wednesday, November 13, 2002 6:01 PM To: [EMAIL PROTECTED] Cc: Tomcat Users List Subject: Re: remove the need for :8443 in URLs needing https: how do you run tomcat on port 8443 or 443, with the official tomcat distribtion you root rights for serving content on port 443 under linux. cu Torsten Fohrer On Wednesday 13 November 2002 01:24, Pae Choi wrote: That is wha the connector is for. Pae - Original Message - From: Qmail List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Tuesday, November 12, 2002 1:21 PM Subject: remove the need for :8443 in URLs needing https: Hello, It is more difficult to re-write urls as: https://www.domain.com:8443/index.jsp as opposted to https://www.domain.com/index.jsp How can I configure Tomcat (and/or underlying Unix box) to not need the :8443 explicit port reference in the url? I tried changing the https /etc/services entry to port 8443 instead of 443, but no luck. Regards -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
AW: tomcat 4.1 does not resolve links
here is a patch for FileDirContext.java -Ursprüngliche Nachricht- Von: Alexander Piavka [mailto:piavka;cs.bgu.ac.il] Gesendet: Donnerstag, 17. Oktober 2002 11:17 An: Tomcat Users List Betreff: Re: tomcat 4.1 does not resolve links Does anyone know then the 4.1.13 version will be released, or maybe this bug has been already solved and i can download the current cvs(or a patch)? Since i really need it urgently. I tried to make minor changes in the FileDirContext.java file, so that allowLinking is always enabled but it did now work. Thanks. On Sun, 6 Oct 2002, Remy Maucherat wrote: Alexander Piavka wrote: The RELEASE-NOTES it is said that to enable symbloic linking i need to add the allowLinking option to FileDirContext. But i did not find anything about FileDirContext in the documentation. Does anyone know where sould the FileDirContext configuration be put and where is the documentation about it. It turns out there is a bug in the feature in 4.1.12. It will be fixed in 4.1.13, and properly documented. -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org FileDirContext.patch Description: Binary data -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
AW: AW: tomcat 4.1 does not resolve links
Hi, this case is true, but i use some symbolic links with different names that lies outside the root/webapp with same/different names, if i set allowLinking/case sensitive to true the checks fails too. -Ursprüngliche Nachricht- Von: Luise Massimo [mailto:mluise;computercenter.it] Gesendet: Freitag, 18. Oktober 2002 09:00 An: Tomcat Users List Betreff: Re: AW: tomcat 4.1 does not resolve links Hi, i think there is another problem in FileDirContext.java.the problem reside in the following code: if (!canPath.equals(absPath)) return null; if you allow linking and the file linked is INSIDE webapp directory (so isLink = !canPath.startsWith(absoluteBase) is false, tomcat execute the code showed before and return null because absPath and canPath differ ! In this case the linking are allowed by allowLinking attribute, but are not allowed by the test inside FileDirContext Torsten Fohrer wrote: here is a patch for FileDirContext.java -Ursprüngliche Nachricht- Von: Alexander Piavka [mailto:piavka;cs.bgu.ac.il] Gesendet: Donnerstag, 17. Oktober 2002 11:17 An: Tomcat Users List Betreff: Re: tomcat 4.1 does not resolve links Does anyone know then the 4.1.13 version will be released, or maybe this bug has been already solved and i can download the current cvs(or a patch)? Since i really need it urgently. I tried to make minor changes in the FileDirContext.java file, so that allowLinking is always enabled but it did now work. Thanks. On Sun, 6 Oct 2002, Remy Maucherat wrote: Alexander Piavka wrote: The RELEASE-NOTES it is said that to enable symbloic linking i need to add the allowLinking option to FileDirContext. But i did not find anything about FileDirContext in the documentation. Does anyone know where sould the FileDirContext configuration be put and where is the documentation about it. It turns out there is a bug in the feature in 4.1.12. It will be fixed in 4.1.13, and properly documented. -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org - --- -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Multiple SSL and TOMCAT ?????
How do i get Multiple SSL Hosts working on 1 Tomcat ? regards Torsten Fohrer -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
AW: iso-8859-2
hi, try %@ page contentType=text/html; charset=iso-8859-2% at top of your jsp pages. -Ursprngliche Nachricht- Von: Skorupski Pawel ,(PZUZ) [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 19. Juni 2002 10:11 An: 'Tomcat Users List' Betreff: iso-8859-2 Hi, the problem I am facing is that even if I set the charset to iso-8859-2 my browser shows always jsp pages in iso-8859-1. It has started with Tomcat 4.0 , Tomcas 3.2 works fine. I changed charset in browser options and it doesn't work. Any help will be appreciated :) Pawel -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
AW: charset fail to set browser encoding
try, %@ page contentType=text/html; charset=gb2312 % at the first line in your jsp page. -Ursprüngliche Nachricht- Von: Kenneth Tang [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 14. Juni 2002 09:26 An: [EMAIL PROTECTED] Betreff: charset fail to set browser encoding Hi, I am new in using Tomcat. I got a problem in displaying i18n char in jsp page. I got a simple jsp page as below: html head META http-equiv=Content-Type content=text/html; charset=gb2312 /head font face=Verdana, Arial, Helvetica, sans-serifbfont size=3×¢²á/font/b/font The charset have been set to gb2312. However, one have to change the encoding manually inside the brower in order to view the encoding correctly. I have also tried to change the file extension from xx.jsp to xx.html. It works in xx.html extension, but fail to display correct encoding in xx.jsp. Am I miss something? Could any one give me a hand on it? Thanks in advanced! Regards, --kenneth -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
AW: libawt.so - No such file or directory - What's wrong?
Hi, 1.if you use awt objects you need a running X-Server, because most awt controls needed a native peer control, that's needed the X-Server.. 2. if you will run tomcat, or other jsp/servlet engines you need the jdk not the jre... (for version before 1.3 known, 1.4 not tested...) ok...? -Ursprüngliche Nachricht- Von: Rasmus Wiman [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 12. April 2002 14:22 An: [EMAIL PROTECTED] Betreff: libawt.so - No such file or directory - What's wrong? Hi all. We have a little problem with a site we've moved from servletrunner, Sun jre 1.3 and NT to a Slackware 8.0 box running tomcat 4.02. We started out with IBM:s jre 1.3, but have also tried Sun jre 1.3 (We of course did the mandatory ulimit -s 6144 to avoid java segfaulting). Each time we try to create a java.awt.Color object we get an exception, the system can't find $JAVA_HOME/lib/i386/libawt.so. Of course we have double checked it, the .so file is certainly there. What could be wrong? I inlcuded the complete exception output below. Any Ideas? DEBUG [Report Servlet Thread] ReportServlet- ExportableImageContainer= ERROR [Report Servlet Thread] ReportServlet- Unexpected exception when creating a report. java.lang.UnsatisfiedLinkError: /usr/local/jre1.3.1_03/lib/i386/libawt.so: cannot open shared object file: cannot load shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1414) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1330)at java.lang.Runtime.loadLibrary0(Runtime.java:744)at java.lang.System.loadLibrary(System.java:815) at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:48)at java.security.AccessController.doPrivileged(Native Method) at java.awt.Toolkit.loadLibraries(Toolkit.java:1065) at java.awt.Toolkit.clinit(Toolkit.java:1086)at java.awt.Color.clinit(Color.java:183) at se.tidax.webq.report.ReportServlet.BarChart(ReportServlet.java:800) at se.tidax.webq.report.ReportServlet.getTotalWorkloadForMonthDiagramMonth(R eportServlet.java:472) at se.tidax.webq.report.ReportServlet.doPost(ReportServlet.java:190) at se.tidax.webq.report.ReportServlet.doGet(ReportServlet.java:699)at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat ionFilterChain.java:247)at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilte rChain.java:193)at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve .java:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.jav a:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:47 2) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve .java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.jav a:566) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorB ase.java:475) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.jav a:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:47 2) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java: 180)at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.jav a:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVal ve.java:170)at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.jav a:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java: 170)at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.jav a:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.jav a:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:47 2) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.j ava:174)at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.jav a:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:47 2) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:429) at org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:495) at java.lang.Thread.run(Thread.java:479) Unexpected exception when
Apache 2.0 and Tomcat 4.0, index.jsp
I get Tomcat 4.03 with the Connectors 4.0.4b and Apache working, but even if i put DirectoryIndex index.jsp index.htm in httpd.conf. Tomcat ignores them could somebody..have a answer thanks -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
AW: Apache 2.0 and Tomcat 4.0, index.jsp
thanks, for help but it doesn't work, the only thing that is working is this Command in httpd.conf JkMount /* ajp13.but then can I use tomcat purethats faster .. i have found it that's helpbut now static index files are delivered by tomcat too... JkMount / ajp13 but better than non index.jsp thanks all -Ursprüngliche Nachricht- Von: Julien OIX [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 10. April 2002 12:20 An: Tomcat Users List Betreff: Re: Apache 2.0 and Tomcat 4.0, index.jsp Torsten Fohrer a écrit : I get Tomcat 4.03 with the Connectors 4.0.4b and Apache working, but even if i put DirectoryIndex index.jsp index.htm in httpd.conf. Tomcat ignores them could somebody..have a answer thanks edit $TOMCAT_HOME/conf/web.xml or your $TOMCAT_HOME/webapps/$YOURAPP/WEB-INF/web.xml; at the end of this file, you find the welcome-file-list section, which has the same effect that DirectoryIndex directive under Apache welcome-file-list welcome-fileindex.jsp/welcome-file welcome-fileframeset.html/welcome-file welcome-fileaccueil.htm/welcome-file welcome-filedefault.htm/welcome-file /welcome-file-list hopes this helps -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- Julien OIX Service Informatique de Gestion Tél: 02 40 99 83 65 mail: [EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
