RE: X509 certificates and https
Hi, I think I have seen this Exception. I had certificate with both human readable and encoded parts. I deleted human readable part (I left only encoded part between -BEGIN CERTIFICATE- and -END CERTIFICATE- including these tags). After this, I was able to import this certificate. Lipi -Original Message- From: Julie McCabe [mailto:[EMAIL PROTECTED] Sent: Thursday, May 27, 2004 4:21 PM To: Tomcat Users List Subject: Re: X509 certificates and https Hi, I tried the following command keytool -import -alias tomcat -keystore server.ks -trustcacerts -file server.crt with my certificate and key which are in pem format and it returned keytool error: java.lang.Exception: Input not an X.509 certificate I have the CA certifcate stored in my browser but cant see how I can export it? Thanks Julie. On Thursday 27 May 2004 15:24, [EMAIL PROTECTED] wrote: The only thing you have to do is running the java keytool utily with following command: keytool -import -alias tomcat -keystore server.ks -trustcacerts -file server.crt This inserts thet server.crt certificate into the keystore that tomcat uses. Your CA scertificate needs to be in the trusted keystore of your JRE under which Tomcat runs. If this is not the case put it in there as follows: keytool -import -keystore %JAVA_HOME%/lib/security/cacerts -file ca.pem -alias my_alias This inserts the root certificate ca.pem into the trusted keystore of the JRE being used. This should work. Ron Blom - 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: Can I change Tomcat's default character encoding?
Thank you for the answer. I know about this possibility using filters (and I have done something). But the original question (and my question) is about simpler way: Is it possible to globally set (somewhere in JVM or Tomcat configuration) default character encoding for all created Writers? Lipi -Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 7:45 PM To: 'Tomcat Users List' Subject: RE: Can I change Tomcat's default character encoding? Hi, quick response, you can use your own customized OutputStreamWriter. You need to extend the abstract class ServletOutputStream. And you integrate your customized writer with tomcat by implementing a filter. For more info on how to use filters, you can do a search on google. This will only work for Tomcat 4 and up, or any other container that implement Servlet 2.3 and up. -Yan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Can I change Tomcat's default character encoding?
-Original Message- From: Yansheng Lin [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 11:57 PM To: 'Tomcat Users List' Subject: RE: Can I change Tomcat's default character encoding? Also you may have to change your OS default locale since JVM and Java Runtime uses system default language environment. Is there any way to set default encoding for created writers? For instance - class OutputStreamWriter has constructors with or without charset parameter. If no charset is specified, the default one will be used. And it depends on the system. It makes problems when same (web) application should run on different platforms (Windows, Linux, etc.). I have not system under my control but I have Tomcat web servers under control. So, question is - can I configure JAVA VM (or Tomcat itself) to create OutputStreamWriter(s) with my default character encoding? Thank you, Lipi. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: API for authenticating user
Hi Matt, application under your link is not running. Lipi -Original Message- From: Matt Raible [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 4:26 AM To: Tomcat Users List Subject: Re: API for authenticating user Unfortunately, there is not an API for this in J2EE or container-managed authentication. I accomplish this in an example app that I wrote - using cookies and a redirect to j_security_check. For a demo, see http://demo.raibledesigns.com/appfuse. Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: All threads (150) are currently busy....
Hi, it means that all threads are currently performing some request. It can have two reasons: 1) High load of the server - requests come quicker than they are finished. You can increase maxThreads or you can look into your app why it takes so long time. 2) Some requests are not finished due to some bug in your app. On Linux you can send kill -QUIT to your Tomcat process. You will receive stack traces of all VM threads and you can see where the threads currently are. Lipi -Original Message- From: Pavle [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 8:21 AM To: [EMAIL PROTECTED] Subject: All threads (150) are currently busy After several days of good woking my Tomcat 5.0.16 on RedHat 9.0 box stops accepting connection on SSL connector. In catalina.out I am recieving this message: SEVERE: All threads (150) are currently busy My server.xml file for SSL connector is the following: Connector port=8443 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true connectionTimeout=2 acceptCount=100 debug=0 scheme=https secure=true Factory clientAuth=false protocol=TLS keystoreFile=*** keystorePass=***/ /Connector I tried to put smaller connectionTimeout but it does not work too. I am not able to find anything on Google. Thanks Pavle - 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: RE: All threads (150) are currently busy....
I had a bit similar problem - see How to limit time for Connector threads? tread in this mailing list. In the end I found that my thread is in java.net.SocketOutputStream.socketWrite0(Native Method) method. Probably reason was that server waited for timeout because client had broken connection. Stack trace of running threads was very useful. Lipi -Original Message- From: Pavle [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 9:00 AM To: [EMAIL PROTECTED] Subject: RE: RE: All threads (150) are currently busy The main problem is that there is no load on the serever when this occurs. Everything works perfectly during the normal working week. The message and the hunging occurs during weekends, when there is low traffic. Pavle -Original Message- From: rlipi [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 8:46 AM To: 'Tomcat Users List'; [EMAIL PROTECTED] Subject: RE: All threads (150) are currently busy Hi, it means that all threads are currently performing some request. It can have two reasons: 1) High load of the server - requests come quicker than they are finished. You can increase maxThreads or you can look into your app why it takes so long time. 2) Some requests are not finished due to some bug in your app. On Linux you can send kill -QUIT to your Tomcat process. You will receive stack traces of all VM threads and you can see where the threads currently are. Lipi -Original Message- From: Pavle [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 8:21 AM To: [EMAIL PROTECTED] Subject: All threads (150) are currently busy After several days of good woking my Tomcat 5.0.16 on RedHat 9.0 box stops accepting connection on SSL connector. In catalina.out I am recieving this message: SEVERE: All threads (150) are currently busy My server.xml file for SSL connector is the following: Connector port=8443 maxThreads=150 minSpareThreads=25 maxSpareThreads=75 enableLookups=false disableUploadTimeout=true connectionTimeout=2 acceptCount=100 debug=0 scheme=https secure=true Factory clientAuth=false protocol=TLS keystoreFile=*** keystorePass=***/ /Connector I tried to put smaller connectionTimeout but it does not work too. I am not able to find anything on Google. Thanks Pavle - 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: How to limit time for Connector threads?
Hi all, I would like to finish this mailing thread and public results. In the end I found that some thread waits in java.net.SocketOutputStream.socketWrite0(Native Method) method. Probably reason was that server waited for timeout because client had broken connection. Because I have main entry app method synchronized all other treads waited for an end of this one thread. Hence, server didn't answer. Workaround solution for my particular problem: I have made CacheFilter. I let the treads write into my memory buffer instead of the original output stream. When the synchronized section is done I write buffered date to the original stream. You can download my tree simple classes from: http://info.vsb.cz/test/cacheFilter.zip. It is not general solution but it solves my particular problem in my particular environment. Inspiration for Filters I take from: http://www.javaworld.com/javaworld/jw-06-2001/jw-0622-filters.html Regards, Lipi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RE: RE: All threads (150) are currently busy....
I have made tests of my solution. It runs more then week without problems. So, I have posted it now to the original mailing thread. But it solves only my particular situation. I am not sure if the solution can help you. I think that more usefull for you is the way I found the problem. I used kill -QUIT signal and from stack traces I recognized the reason (many thanks to Antonio Fiol). Lipi -Original Message- From: Pavle [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 10:10 AM To: [EMAIL PROTECTED] Subject: RE: RE: RE: All threads (150) are currently busy Really sorry for the previous mail. I have sent it by mistake. How did you resolve the problem. I have visited the thread you have suggested, but however I was unable to find the solution. Pavle - 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: Persistent workspace
Hi, see this: Host name=localhost debug=0 appBase=webapps unpackWARs=true autoDeploy=true xmlValidation=false xmlNamespaceAware=false There is unpackWARs attribute in the Host element in the server.xml. But I'm not sure that you have asked about this. Lipi -Original Message- From: Simon Brooke [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 18, 2004 3:17 PM To: Tomcat Users List Subject: Persistent workspace -BEGIN PGP SIGNED MESSAGE- I've been deploying webapps with Tomcat since 1997, so you'd think I should know what I'm doing by now... But I find I don't. I'm increasingly trying to package my webapps so that they can be 'just dropped in' without any skill or knowledge being needed by the site administrator to get them set up and deployed, and this has raised two problems with relation to persistent workspace. If a preconfigured war file is installed into Tomcat using the manager webapp, it doesn't get unpacked, and in many ways that's a good thing. But I have up till now used sub-directories of the webapp root directory to store persistent data, for example cached pages and uploaded files. More particularly, I've been using the presence of a file 'WEB-INF/hymen.txt' as a marker that this webapp has never been accessed before and needs final initialisation, and had any servlet redirect to a special servlet which handled final setup if that file exists. Obviously, the final setup servlet then removed the marker file. Clearly neither of these things work if the webapp is delivered as a war file. Generally my webapps talk to databases (usually SQL databases, but could be LDAP, or other things) so it should be possible to replace the 'hymen.txt' mechanism with a simple database call which will succeed if the database has been initialised but fail if it hasn't. However this doesn't solve the problem of where to put caches and upload directories, and I can't find anything in the Servlet API which helps with this. I really don't want to be storing large lumps of arbitrary data into the database. Is there any mechanism in the Servlet spec which allows me either (i) to request that my war file should be unpacked when it is deployed, or else (ii) to get hold of some persistent filespace that my webapp can write to? Cheers Simon - -- [EMAIL PROTECTED] (Simon Brooke) http://www.jasmine.org.uk/~simon/ ;; Our modern industrial economy takes a mountain covered with trees, ;; lakes, running streams and transforms it into a mountain of junk, ;; garbage, slime pits, and debris. -- Edward Abbey -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBQKoM4nr1UrYJMbiJAQHbngP/SGMuawDkFhjStVUZUka8wjhPy+0yM+k/ Fm6v8niMFNyxGLvRhBkQEt7Wd8ZLrfIMKmssIiivuHZkf0ErYyc/hfRBmizG8xCG j3fc2KtvoRp1L2+sH+UyfJwW8lWQHDNFF+kc9MXTXKfs3nTFMBUtvjmVx6tI6fYe fOc3H1eikjE= =lAMw -END PGP SIGNATURE- - 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: How to limit time for Connector threads?
) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:151) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 67) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:83 3) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC onnection(Http11Protocol.java:732) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:61 9) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:688) at java.lang.Thread.run(Thread.java:534) - Maybe it is important - yet another thread is always runnable: http8080-Processor44 daemon prio=1 tid=0x62bc9b88 nid=0x2a06 runnable [b73ff000..b73ff908] at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353) - locked 0x467ea0f0 (a java.net.PlainSocketImpl) at java.net.ServerSocket.implAccept(ServerSocket.java:448) at java.net.ServerSocket.accept(ServerSocket.java:419) at org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(Defau ltServerSocketFactory.java:107) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint. java:410) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:59 1) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:688) at java.lang.Thread.run(Thread.java:534) Thank you for any suggestions, Lipi -Original Message- From: Antonio Fiol Bonnín [mailto:[EMAIL PROTECTED] Sent: Thursday, May 06, 2004 8:42 PM To: Tomcat Users List Subject: Re: How to limit time for Connector threads? Hi Yoav, What the original poster meant is not that there is a race condition in Tomcat, but in his own web application. Maybe we should try to point him into the direction of fixing the problem. So there I go: - When it hangs, if on Unix/Linux, kill -QUIT your Tomcat process, and you will get some stack traces. - Maybe they will tell you something. If they do, you're lucky. Otherwise, post them: maybe they will tell us something. At least, you will see how many threads there are, and their state (e.g. waiting for a lock). Good luck! Antonio Fiol Shapira, Yoav wrote: Hi, I highly doubt you've stumbled on a race condition in the tomcat connector implementation. Nonetheless, if you can supply a small WAR that leads to the problem you've described, we'll be glad to test it, and if your problem is reproducible rest assured it will be fixed immediately, as that would be more important than the other stuff currently open in bugzilla. Yoav Shapira Millennium Research Informatics -Original Message- From: rlipi [mailto:[EMAIL PROTECTED] Sent: Thursday, May 06, 2004 3:26 AM To: 'Tomcat Users List' Subject: RE: How to limit time for Connector threads? Yes, I did it. But it is not solution. Server doesn't answer slowly or for only some requests. It doesn't answer at all. It means that treads are not terminated and resources are not released. Sometimes, server doesn't answer without All threads are currently busy exception. That is why I think that the problem is some death lock. Lipi -Original Message- From: STOCKHOLM, Raymond [mailto:[EMAIL PROTECTED] Sent: Thursday, May 06, 2004 8:56 AM To: Tomcat Users List Subject: RE: How to limit time for Connector threads? Maybe you should increase the number of threads in your connector. check attribut maxProcessors in your server.xml In this example, I set it to 500 instead of 75 (default value) Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=80 minProcessors=30 maxProcessors=500 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false disableUploadTimeout=true / -Message d'origine- De : rlipi [mailto:[EMAIL PROTECTED] Envoyé : jeudi 6 mai 2004 08:40 À : 'Tomcat Users List' Objet : How to limit time for Connector threads? Hallo, is it possible in any way to limit time for threads that realize user requests? Sometimes (once a day in average), the Tomcat 5.0.19 server doesn't answers. The reason is in error message All threads are currently busy. Probably there is a bug in the web application. Some kind of synchronization death lock, I think. But localization of this bug is very hard. So, termination (and release of all resources) of long time
full URL
Hi, is it possible to (in servlet or JSP) gain full URL string? It means protocol, server, directory, parameters, user identification. There are methods in the servlet that return parts of the URL. But I didn't find method that returns full URL string. Than you, Lipi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to limit time for Connector threads?
Hi Yoav and Antonio, I am not absolutely sure, but I think (with high probability) that the bug is in our application. I am not original author of this application but I have to take care about it. Now I know that there are some strangenesses in source code of this app. Yet one reason why I think that it is in our app. The server stops answer on http (but it still answers on https). It is still running. I have to stop it. During the standard stopping of server I can see message like Waiting for 175 instance(s) to be deallocated right after message about removing of this app. The problem began to occur when we started to use this app as the main web page. The app URL had been accessible for weeks before but only through the link from the old main web page. After that, the traffic has been multiplied (by 10 or 20). The problem occurs once a day (in average). But interesting is that it is not in time of the highest traffic. It occurs mainly in the morning or evening. I am going to try Antonio's proposal. Also I would like to try some profiling tool. But it will take a lot of time to find and repair something, I think. So, let's go back to my original question. I think that it is common situation that, due to the some mistake in source code, the execution of a request thread is very long or infinite. And the server should not to go down by this kind of mistakes. I send (in attachment) to you very simple example of it. Execution time of this example is about 100 seconds but imagine that it can be hours. I think that the server should stop this thread after some time period. Is this possible? How can I tell the server to do this? Thank you, Lipi -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, May 06, 2004 8:47 PM To: Tomcat Users List Subject: RE: How to limit time for Connector threads? Hi, What the original poster meant is not that there is a race condition in Tomcat, but in his own web application. I don't think so, but either one of us could be misinterpreting the original post. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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: How to limit time for Connector threads?
I see that there is no source code in the mail attachment.
So, here is the source code of loop.jsp:
--
Start...
%
int limit = 100;
for(int i = 0; i limit; i++) {
System.out.println(Attempt number: + i);
out.print(br);
out.print(Attempt number: + i);
out.flush();
try {
Thread.sleep(1000);
}
catch(InterruptedException exc) {exc.printStackTrace();}
}
%
...End
---
Regards,
Lipi
-Original Message-
From: rlipi [mailto:[EMAIL PROTECTED]
Sent: Friday, May 07, 2004 9:17 AM
To: 'Tomcat Users List'
Subject: RE: How to limit time for Connector threads?
Hi Yoav and Antonio,
I am not absolutely sure, but I think (with high probability) that the
bug is in our application. I am not original author of this
application
but I have to take care about it. Now I know that there are some
strangenesses in source code of this app.
Yet one reason why I think that it is in our app. The server stops
answer on http (but it still answers on https). It is still running. I
have to stop it. During the standard stopping of server I can see
message like Waiting for 175 instance(s) to be deallocated right
after
message about removing of this app.
The problem began to occur when we started to use this app as the main
web page. The app URL had been accessible for weeks before but only
through the link from the old main web page. After that, the traffic
has
been multiplied (by 10 or 20). The problem occurs once a day (in
average). But interesting is that it is not in time of the highest
traffic. It occurs mainly in the morning or evening.
I am going to try Antonio's proposal. Also I would like to try some
profiling tool. But it will take a lot of time to find and repair
something, I think.
So, let's go back to my original question. I think that it is common
situation that, due to the some mistake in source code, the execution
of
a request thread is very long or infinite. And the server should not
to
go down by this kind of mistakes. I send (in attachment) to you very
simple example of it. Execution time of this example is about 100
seconds but imagine that it can be hours. I think that the server
should
stop this thread after some time period. Is this possible? How can I
tell the server to do this?
Thank you,
Lipi
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 06, 2004 8:47 PM
To: Tomcat Users List
Subject: RE: How to limit time for Connector threads?
Hi,
What the original poster meant is not that there is a race
condition
in
Tomcat, but in his own web application.
I don't think so, but either one of us could be misinterpreting the
original post.
Yoav Shapira
This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential,
proprietary and/or privileged. This e-mail is intended only for the
individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your
computer system and notify the sender. Thank you.
-
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: How to limit time for Connector threads?
Maybe I have wrong idea about possibilities of debugging tools but I think that it will not help. We have above 100 000 hits a day and the problem occurs only once a day. It can be a result of one special request or (with greater probability) it is result of some combination of requests. In both cases I don't know these requests nor the particular place where the problem is. Therefore, I need some statistical information about server behavior before problem and/or all possible information about server status in the time of problem. Can debugger help me with this? Lipi -Original Message- From: Rodrigo Ruiz [mailto:[EMAIL PROTECTED] Sent: Friday, May 07, 2004 12:27 PM To: Tomcat Users List Subject: Re: How to limit time for Connector threads? rlipi wrote: I am going to try Antonio's proposal. Also I would like to try some profiling tool. But it will take a lot of time to find and repair something, I think. If you are dealing with a programming error like an infinite loop or a deadlock, you may have better luck using a debugger, rather than a profiling tool :-) Most of the popular IDEs (JBuilder, Eclipse, Idea, etc) can do remote debugging, so you just need to start your server (or a copy of it) in debug mode and connect to it from the IDE. In case you do not have any IDE, my recommendation is Eclipse, as it is free and needs no complicated installation. In case you do not know how to use remote debugging, I am pretty sure you can search through the archives in this list, or do some googling ;-) Hope it helps you, Rodrigo Ruiz -- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.678 / Virus Database: 440 - Release Date: 06/05/2004 - 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: Question about memory
Hi, it's very interesting feature. I am trying it. But I have problem with authorization. The manager web pages are password protected. I see that there are two Config Elements that maybe can help: Login Config Element HTTP Authorization Manager But I don't know which one to use and how to configure it (what to write into Base URL of the HTTP Authorization Manager. I have tried o lot of possibilities but I am still receiving only: sampleResult timeStamp=1083937698899 dataType=text threadName=server monitoring1-1 label=Server status time=20 responseMessage=Unauthorized responseCode=401 success=false/ Thank you for any suggestions, Lipi -Original Message- From: Peter Lin [mailto:[EMAIL PROTECTED] Sent: Thursday, May 06, 2004 8:13 PM To: Tomcat Users List Subject: RE: Question about memory by the way, you can view the performance of Tomcat using JMeter. it will make a request to the status page and then graph the results. peter Shapira, Yoav [EMAIL PROTECTED] wrote: Hi, Here is a blurp i found searching through google for memory top and tomcat: It wouldn't hurt to quote or link to your sources ;) Supposedly tomcat 5 has a status page that displays memory usage. That might be more accurate. It's http://host:port/manager/status. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to limit time for Connector threads?
Hallo, is it possible in any way to limit time for threads that realize user requests? Sometimes (once a day in average), the Tomcat 5.0.19 server doesn't answers. The reason is in error message All threads are currently busy. Probably there is a bug in the web application. Some kind of synchronization death lock, I think. But localization of this bug is very hard. So, termination (and release of all resources) of long time threads can be a work around. Thank you for any suggestions, Lipi. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to limit time for Connector threads?
Yes, I did it. But it is not solution. Server doesn't answer slowly or for only some requests. It doesn't answer at all. It means that treads are not terminated and resources are not released. Sometimes, server doesn't answer without All threads are currently busy exception. That is why I think that the problem is some death lock. Lipi -Original Message- From: STOCKHOLM, Raymond [mailto:[EMAIL PROTECTED] Sent: Thursday, May 06, 2004 8:56 AM To: Tomcat Users List Subject: RE: How to limit time for Connector threads? Maybe you should increase the number of threads in your connector. check attribut maxProcessors in your server.xml In this example, I set it to 500 instead of 75 (default value) Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=80 minProcessors=30 maxProcessors=500 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false disableUploadTimeout=true / -Message d'origine- De : rlipi [mailto:[EMAIL PROTECTED] Envoyé : jeudi 6 mai 2004 08:40 À : 'Tomcat Users List' Objet : How to limit time for Connector threads? Hallo, is it possible in any way to limit time for threads that realize user requests? Sometimes (once a day in average), the Tomcat 5.0.19 server doesn't answers. The reason is in error message All threads are currently busy. Probably there is a bug in the web application. Some kind of synchronization death lock, I think. But localization of this bug is very hard. So, termination (and release of all resources) of long time threads can be a work around. Thank you for any suggestions, Lipi. - 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: Vedr.: RE: How to limit time for Connector threads?
Hi Thomas, the Tomcat isn't integrated to any web server. It runs alone. The problem occurs on both ports. In better words - the Tomcat is listening on the port 8080 but there is transparent redirect from 80 to 8080 in iptables. Radek -Original Message- From: Thomas Nybro Bolding [mailto:[EMAIL PROTECTED] Sent: Thursday, May 06, 2004 9:51 AM To: Tomcat Users List Subject: Vedr.: RE: How to limit time for Connector threads? Hi Lipi, are you by any chance integrating Tomcat with IIS using JK2? And does the death lock occur whether you use port 80 or 8080? /Thomas rlipi [EMAIL PROTECTED] 06-05-2004 09:25 Besvar venligst til Tomcat Users List Til:'Tomcat Users List' [EMAIL PROTECTED] cc: Vedr.: RE: How to limit time for Connector threads? Yes, I did it. But it is not solution. Server doesn't answer slowly or for only some requests. It doesn't answer at all. It means that treads are not terminated and resources are not released. Sometimes, server doesn't answer without All threads are currently busy exception. That is why I think that the problem is some death lock. Lipi -Original Message- From: STOCKHOLM, Raymond [mailto:[EMAIL PROTECTED] Sent: Thursday, May 06, 2004 8:56 AM To: Tomcat Users List Subject: RE: How to limit time for Connector threads? Maybe you should increase the number of threads in your connector. check attribut maxProcessors in your server.xml In this example, I set it to 500 instead of 75 (default value) Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=80 minProcessors=30 maxProcessors=500 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false disableUploadTimeout=true / -Message d'origine- De : rlipi [mailto:[EMAIL PROTECTED] Envoyé : jeudi 6 mai 2004 08:40 À : 'Tomcat Users List' Objet : How to limit time for Connector threads? Hallo, is it possible in any way to limit time for threads that realize user requests? Sometimes (once a day in average), the Tomcat 5.0.19 server doesn't answers. The reason is in error message All threads are currently busy. Probably there is a bug in the web application. Some kind of synchronization death lock, I think. But localization of this bug is very hard. So, termination (and release of all resources) of long time threads can be a work around. Thank you for any suggestions, Lipi. - 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] FONT SIZE=1 FACE=Arial___ Vi gør opmærksom på, at denne e-mail kan indeholde fortrolig information. Hvis du ved en fejltagelse modtager e-mailen, beder vi dig venligst informere afsender om fejlen ved at bruge svar-funktionen. Samtidig beder vi dig slette e-mailen i dit system uden at videresende eller kopiere den. Selv om e-mailen og ethvert vedhæftet bilag efter vores overbevisning er fri for virus og andre fejl, som kan påvirke computeren eller it-systemet, hvori den modtages og læses, åbnes den på modtagerens eget ansvar. Vi påtager os ikke noget ansvar for tab og skade, som er opstået i forbindelse med at modtage og bruge e-mailen. ___ Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake by sending a reply, then delete the message from your system without making, distributing or retaining any copies of it. Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message. /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Automatic login after registration on the Tomcat
Hello, I have interesting problem with an authentication. I use a JDBCRealm. I have a protected area. When a user comes to the protected area, server redirects the user to the login page. If the user knows his user name and password, he writes it and submits login form. If the user does not know user name and password, he clicks link on the login page to the register page. On the register page, he creates new user account - he types login name, password (twice) and e-mail. After submition of the HTML form, my JSP does some checks - similarity of passwords, individuality of user name, etc... If everything is OK, registration is successful - JSP writes user name, password and e-mail into the users table in DB. If not, registration fails and user comes back to the registration page. Problem is, that in the case of successful registration, user must go back to the login page and log into the application. He must type username and password again. But I have all information to login user into protected area on the server (user types it during the registration). Can I write any server side code, that log in the user, if I have his login name and password from the registration form and I'm sure, that user name and password are correct and registration is successful? There is idea create login form on the server and fill login name and password on the server. Bud I think that writing of password into HTML source and sending it to a WWW browser is not secure. Thank you. Lipi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: POST method not working
Hi, maybe we have a similar problem. Try to put slash to the end of the action attribute of the form. For example: form action=servlet_name/ method=post Radek -Original Message- From: Kumar Abhay-CAK203C [mailto:[EMAIL PROTECTED] Sent: Thursday, February 05, 2004 7:05 PM To: [EMAIL PROTECTED] Subject: POST method not working Importance: High Hi, I am suing post method of sending data to servlet from a JSP page. I am unable to get the data by request.getParameter(). If I am sing get method I am able to retrieve data from JSP page Please let me know how to achieve this ? And what is the bug ? Abhay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat.conf missing
Hi. Solve it in other way. Run Tomcat on some port up to 1024 under any user you like and redirect (in iptables) requests from port 80 (443) to your own port(s). Radek -Original Message- From: hostmaster [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 9:23 AM To: [EMAIL PROTECTED] Subject: Re: tomcat.conf missing Okay, but it should be possible to set the user like TOMCAT_USER=tomcat4 startup.sh and catalina.sh are offering no such possibility. chown -R tomcat4.tomcat4 jakarta was not able to fix the root problem. hostmaster wrote: I just installed Tomcat 4.1.29 The problem I got is: Tomcat is running under root. I'd like to change this to tomcat4 But there is no longer a tomcat.conf file available where I can change this setting. tomcat.conf is not a part of jakarta-tomcat-4.1.x package. It is a part of a RPM for version 2.1.24. It is nice, but it has nothing to do with the original package. Nix. - 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: How to restrict all webapps with http authentication in Tomcat?
Will help this: http://www.ingrid.org/jajakarta/tomcat/tomcat-4.0b5/src/catalina/docs/si nglesignon.html#Security ? Radek -Original Message- From: Salvador Santander Gutierrez [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 10:16 AM To: Tomcat List Subject: How to restrict all webapps with http authentication in Tomcat? I need to restrict all web applications in Tomcat with the same users? I know how to restrict a specific web application with its web.xml but... how to restrict /* in tomcat, included html pages? Thanks. - 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.conf missing
Hi. Probably because you are logged in as the root. Try to log in as the tomcat4 user. Or change user by the su tomcat4 command. Next run the Tomcat. Maybe you will need to enable rwx rights to tomcat4 user on the Tomcat directories and files. Radek -Original Message- From: hostmaster [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 10:39 AM To: [EMAIL PROTECTED] Subject: RE: tomcat.conf missing Hi, I'm running Tomcat on the standard port 8080 (mod_jk on 8009) As soon as I'm starting Tomcat it is running under user root No idea how I can change this to user tomcat4 Thanks, Markus Hi. Solve it in other way. Run Tomcat on some port up to 1024 under any user you like and redirect (in iptables) requests from port 80 (443) to your own port(s). Radek -Original Message- From: hostmaster [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 9:23 AM To: [EMAIL PROTECTED] Subject: Re: tomcat.conf missing Okay, but it should be possible to set the user like TOMCAT_USER=tomcat4 startup.sh and catalina.sh are offering no such possibility. chown -R tomcat4.tomcat4 jakarta was not able to fix the root problem. hostmaster wrote: I just installed Tomcat 4.1.29 The problem I got is: Tomcat is running under root. I'd like to change this to tomcat4 But there is no longer a tomcat.conf file available where I can change this setting. tomcat.conf is not a part of jakarta-tomcat-4.1.x package. It is a part of a RPM for version 2.1.24. It is nice, but it has nothing to do with the original package. Nix. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to restrict all webapps with http authentication in Tomcat?
Try again this (it works from my computer): http://www.ingrid.org/jajakarta/tomcat/tomcat-4.0b5/src/catalina/docs/si nglesignon.html I'm sorry if the url is divided into two lines in your incoming mail. Simply concatenate them. Radek -Original Message- From: Salvador Santander Gutierrez [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 12:07 PM To: Tomcat Users List Subject: Re: How to restrict all webapps with http authentication in Tomcat? Thanks for your help but the url passed doesn´t work. - Original Message - From: rlipi [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Friday, February 06, 2004 10:21 AM Subject: RE: How to restrict all webapps with http authentication in Tomcat? Will help this: http://www.ingrid.org/jajakarta/tomcat/tomcat-4.0b5/src/catalina/docs/si nglesignon.html#Security ? Radek -Original Message- From: Salvador Santander Gutierrez [mailto:[EMAIL PROTECTED] Sent: Friday, February 06, 2004 10:16 AM To: Tomcat List Subject: How to restrict all webapps with http authentication in Tomcat? I need to restrict all web applications in Tomcat with the same users? I know how to restrict a specific web application with its web.xml but... how to restrict /* in tomcat, included html pages? Thanks. - 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]
SSO
Hi, I found that it is possible to set Single Sign On for all web aplications running in some Host. I do that according to this topic: http://www.ingrid.org/jajakarta/tomcat/tomcat-4.0b5/src/catalina/docs/si nglesignon.html#Security. And it also works on Tomcat 5. I welcome this feature. Nevertheless, by this way, it authenticates user to the ALL web applications. But I have a few of them where I need special authentication (for example manager or admin web application). Is it possible to configure Tomcat server: 1) to use SSO authentication for nearly all web aplication 2) to use specific authentication (Realm) for a few particular web aplications? Thank You, Radek. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
