Re: Strange difference in behavior ELSupport in Tomcat 6.0.20 and Tomcat 6.0.26
On 27/09/2010 03:39, sbrejeon wrote: The spec says that If A or B is an enum, coerce both A and B to enum, apply operator. Does't it simply mean that both A and B must be coercible to enums. instead of if A is an enum then B must be an enum of type A, or vice versa. No. Both must be of the same type. There are several reasons for this: - There is no provision in the EL spec for enum to enum type conversion via a string value - If both A B are enums, should both values be coerced to enum A or enum B? One may work whilst the other fails. If the spec permitted this then the behaviour in this case would need to be defined. It isn't. - Section 1.17 is clear the String values must be used to trigger enum type conversion Like the original creator of this post, I have a series of enums of different types that implement a common interface. I need to be able to compare them and I don't want to have to translate them to Strings. The EL spec doesn't support what you are trying to do. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: BOE LDAP Configuration
Carter, Reginald wrote: log4j:event logger=com.crystaldecisions.sdk.plugin.authentication.ldap.internal.LDAPImpl timestamp=1284763084123 level=ERROR thread=http-44306-Processor25 log4j:message![CDATA[GetDirContext(): Failed to obtain InitialDirContext]]/log4j:message log4j:throwable![CDATA[javax.naming.CommunicationException: simple bind failed: prdsap01.prod-sap.grainger.com:636 [Root exception is javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty] Getting the above error any suggestion on documentation or things that have worked for others... A couple : - if this is related to Tomcat at all, you may want to specifiy which version, which platform, which JVM etc.. - if it isn't, then you may want to look for an appropriate forum or mailing list - and if you have no idea at all, you may want to search Google for how to ask questions the smart way - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
About ContainerBackgroundProcessor thread
Hi all,
I have developed an application which instanciates a singleton class in
the init method of a servlet. This servlet is defined in the web.xml with
the load-on-startup1/load-on-startup tag. This singleton class start a
Thread which notifies the singleton class when a configuration file has
changed. The thread checks if the file has changed periodically. If
changed, it notifies the singleton.
If I put this configuration file in a different directory than the one
where the application is deployed, the application work as expected.
If I put the configuration file in the WEB-INF/classes directory the
thread notifies the singleton that the file has changed, that's OK. But
what is my suprise that, the init method of the servlet is executed again
by a thread named [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
(viewing logs from log4j) because the instance is requested again. I
thought it could be a tomcat behaviour. But the most strange is that the
singleton class is built as if it was the first time the instance is
requested... and in this singleton I used classes with static{} blocks and
they are executed again.
Does ContainerBackgroundProcessor allow us a mechanism to read
configuration in class directory each time it is modified by reading it in
the init method of servlets? How it works? How can happen this behaviour
in which static blocks are newly executed and singleton classes newly
built, is it a new execution of the JVM?
Thanks,
Juan Moratilla Peón
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 6.0 and Windows 7
Hello, I wrote a web application, that works great with a server under Tomcat 6.0.13 and client with Windows XP OS, in which user has to upload (text) files that are read and exploited. I tried this application (on a client machine) under Windows 7 and it works with uploaded files around 5-6 kb but if I try to upload a file around 60 kb, it doesn't work anymore and the localhost. .log trace file indicates the following error : org.apache.commons.fileupload.FileUploadException: Processing of multipart/form-data request failed. Read timed out at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:384) at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:268) at org.apache.struts.upload.CommonsMultipartRequestHandler.handleRequest(Common sMultipartRequestHandler.java:193) at org.apache.struts.util.RequestUtils.populate(RequestUtils.java:443) at org.apache.struts.action.RequestProcessor.processPopulate(RequestProcessor.j ava:796) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:203) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1192) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:430) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128 ) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104 ) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http 11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) Could you please help me to make my application work with client under Windows 7 ? Thanks in advance. Julie Gautier
Re: About ContainerBackgroundProcessor thread
I answer me:
I'm using reloadable=true in my context. Is that the reason a found this
behaviour??? Am I right??? If I use reloadable=false init method of
servlets will not be executed, am I right???
Here is the explanation I found:
http://tomcat.apache.org/tomcat-3.2-doc/uguide/tomcat_ug.html
Context- reloadable: A reloadable flag. When developing a servlet it is
very convenient to have Tomcat reload it upon change, this lets you fix
bugs and have Tomcat test the new code without the need to shutdown and
restart. To turn on servlet reloading set the reloadable flag to true.
Detecting changes however is time consuming; moreover, since the new
servlets are getting loaded in a new class-loader object there are cases
where this class-reloading trigger casts errors. To avoid these problems
you can set the reloadable flag to false; this will disable the autoreload
feature.
Thanks
Hi all,
I have developed an application which instanciates a singleton class in
the init method of a servlet. This servlet is defined in the web.xml with
the load-on-startup1/load-on-startup tag. This singleton class start a
Thread which notifies the singleton class when a configuration file has
changed. The thread checks if the file has changed periodically. If
changed, it notifies the singleton.
If I put this configuration file in a different directory than the one
where the application is deployed, the application work as expected.
If I put the configuration file in the WEB-INF/classes directory the
thread notifies the singleton that the file has changed, that's OK. But
what is my suprise that, the init method of the servlet is executed again
by a thread named [ContainerBackgroundProcessor[StandardEngine[Catalina]]]
(viewing logs from log4j) because the instance is requested again. I
thought it could be a tomcat behaviour. But the most strange is that the
singleton class is built as if it was the first time the instance is
requested... and in this singleton I used classes with static{} blocks and
they are executed again.
Does ContainerBackgroundProcessor allow us a mechanism to read
configuration in class directory each time it is modified by reading it in
the init method of servlets? How it works? How can happen this behaviour
in which static blocks are newly executed and singleton classes newly
built, is it a new execution of the JVM?
Thanks,
Juan Moratilla Peón
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.0 and Windows 7
Julie Gautier wrote: Hello, I wrote a web application, that works great with a server under Tomcat 6.0.13 and client with Windows XP OS, in which user has to upload (text) files that are read and exploited. I tried this application (on a client machine) under Windows 7 and it works with uploaded files around 5-6 kb but if I try to upload a file around 60 kb, it doesn't work anymore and the localhost. .log trace file indicates the following error : org.apache.commons.fileupload.FileUploadException: Processing of multipart/form-data request failed. Read timed out at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:384) at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:268) at org.apache.struts.upload.CommonsMultipartRequestHandler.handleRequest(Common sMultipartRequestHandler.java:193) ... Just to make sure that we understand this correctly : The only thing which changes is the client (XP or Windows 7), right ? Is it the same browser (or other client program) in both cases, and if yes which one ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 6.0 and Windows 7
Thanks for your quick reply ! It's correct : the only thing that changes is the client. For the browser question, the behavior is the same with IE 8 or FF. Thanks for your help. Julie Gautier -Message d'origine- De : André Warnier [mailto:a...@ice-sa.com] Envoyé : lundi 27 septembre 2010 15:00 À : Tomcat Users List Objet : Re: Tomcat 6.0 and Windows 7 Julie Gautier wrote: Hello, I wrote a web application, that works great with a server under Tomcat 6.0.13 and client with Windows XP OS, in which user has to upload (text) files that are read and exploited. I tried this application (on a client machine) under Windows 7 and it works with uploaded files around 5-6 kb but if I try to upload a file around 60 kb, it doesn't work anymore and the localhost. .log trace file indicates the following error : org.apache.commons.fileupload.FileUploadException: Processing of multipart/form-data request failed. Read timed out at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:384) at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:268) at org.apache.struts.upload.CommonsMultipartRequestHandler.handleRequest(Common sMultipartRequestHandler.java:193) ... Just to make sure that we understand this correctly : The only thing which changes is the client (XP or Windows 7), right ? Is it the same browser (or other client program) in both cases, and if yes which one ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 6.0 and Windows 7
Sorry but no. This statement does not match the localhost part you also mentioned. So really what is changing is that both the client and the server are changing to Windows 7. Start by looking at your firewall settings. -Original Message- From: Julie Gautier [mailto:j.gaut...@actes-sud.fr] Sent: Monday, September 27, 2010 9:05 AM To: 'Tomcat Users List'; 'Tomcat Users List' Subject: RE: Tomcat 6.0 and Windows 7 Thanks for your quick reply ! It's correct : the only thing that changes is the client. For the browser question, the behavior is the same with IE 8 or FF. Thanks for your help. Julie Gautier -Message d'origine- De : André Warnier [mailto:a...@ice-sa.com] Envoyé : lundi 27 septembre 2010 15:00 À : Tomcat Users List Objet : Re: Tomcat 6.0 and Windows 7 Julie Gautier wrote: Hello, I wrote a web application, that works great with a server under Tomcat 6.0.13 and client with Windows XP OS, in which user has to upload (text) files that are read and exploited. I tried this application (on a client machine) under Windows 7 and it works with uploaded files around 5-6 kb but if I try to upload a file around 60 kb, it doesn't work anymore and the localhost. .log trace file indicates the following error : org.apache.commons.fileupload.FileUploadException: Processing of multipart/form-data request failed. Read timed out at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:384) at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:268) at org.apache.struts.upload.CommonsMultipartRequestHandler.handleRequest(Common sMultipartRequestHandler.java:193) ... Just to make sure that we understand this correctly : The only thing which changes is the client (XP or Windows 7), right ? Is it the same browser (or other client program) in both cases, and if yes which one ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: About ContainerBackgroundProcessor thread
From: jmorati...@dit.upm.es [mailto:jmorati...@dit.upm.es] Subject: Re: About ContainerBackgroundProcessor thread Here is the explanation I found: http://tomcat.apache.org/tomcat-3.2-doc/uguide/tomcat_ug.html You can't seriously be using Tomcat 3.2, are you? That hasn't been supported for eons. In regards to your original question, if the reloadable attribute of the Context element is set to true, Tomcat will monitor /classes/ to see if the webapp has been updated. To quote from current documentation: Set to true if you want Catalina to monitor classes in /WEB-INF/classes/ and /WEB-INF/lib for changes, and automatically reload the web application if a change is detected. This feature is very useful during application development, but it requires significant runtime overhead and is not recommended for use on deployed production applications. You can also use a nested WatchedResource element to trigger reloads for other files; the default is just WEB-INF/web.xml. If you don't set reloadable and don't specify the file as a WatchedResource, Tomcat should not attempt to do anything with the webapp once it's started. But if you really are using Tomcat 3.2, I have no idea what it's behavior should be; move up to a supported level. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 6.0 and Windows 7
Hi, No, I manage the server where the application is stored and it didn't change ! The server OS didn't change ! Only the client : if I try with a machine under XP it works (IE or FF), if I try under W7, it doesn't (IE nor FF) ! And the log file on the server is really called localhost.2010-09-25.log ! Thanks for your help. -Message d'origine- De : Maximilian Stocker [mailto:m...@talentoyster.com] Envoyé : lundi 27 septembre 2010 15:09 À : 'Tomcat Users List' Objet : RE: Tomcat 6.0 and Windows 7 Sorry but no. This statement does not match the localhost part you also mentioned. So really what is changing is that both the client and the server are changing to Windows 7. Start by looking at your firewall settings. -Original Message- From: Julie Gautier [mailto:j.gaut...@actes-sud.fr] Sent: Monday, September 27, 2010 9:05 AM To: 'Tomcat Users List'; 'Tomcat Users List' Subject: RE: Tomcat 6.0 and Windows 7 Thanks for your quick reply ! It's correct : the only thing that changes is the client. For the browser question, the behavior is the same with IE 8 or FF. Thanks for your help. Julie Gautier -Message d'origine- De : André Warnier [mailto:a...@ice-sa.com] Envoyé : lundi 27 septembre 2010 15:00 À : Tomcat Users List Objet : Re: Tomcat 6.0 and Windows 7 Julie Gautier wrote: Hello, I wrote a web application, that works great with a server under Tomcat 6.0.13 and client with Windows XP OS, in which user has to upload (text) files that are read and exploited. I tried this application (on a client machine) under Windows 7 and it works with uploaded files around 5-6 kb but if I try to upload a file around 60 kb, it doesn't work anymore and the localhost. .log trace file indicates the following error : org.apache.commons.fileupload.FileUploadException: Processing of multipart/form-data request failed. Read timed out at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:384) at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:268) at org.apache.struts.upload.CommonsMultipartRequestHandler.handleRequest(Common sMultipartRequestHandler.java:193) ... Just to make sure that we understand this correctly : The only thing which changes is the client (XP or Windows 7), right ? Is it the same browser (or other client program) in both cases, and if yes which one ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 6.0 and Windows 7
From: Maximilian Stocker [mailto:m...@talentoyster.com] Subject: RE: Tomcat 6.0 and Windows 7 Sorry but no. This statement does not match the localhost part you also mentioned. I'll bite. Why do you say that? The localhost part of the log file name refers to the Host name attribute, not any particular access from 127.0.0.1. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.0 and Windows 7
Maximilian Stocker wrote: Sorry but no. This statement does not match the localhost part you also mentioned. Maximilian, For a minute, you had me doubt there. So sorry but no, your mistake, not mine. The server will always create this localhost.log file. It is the server that is localhost, not the client. Why would this not match what Julie claimed ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.0 and Windows 7
Caldarale, Charles R wrote: From: Maximilian Stocker [mailto:m...@talentoyster.com] Subject: RE: Tomcat 6.0 and Windows 7 Sorry but no. This statement does not match the localhost part you also mentioned. I'll bite. Why do you say that? The localhost part of the log file name refers to the Host name attribute, not any particular access from 127.0.0.1. So now that 3 of us agree that the server does not change, what can be the cause that a Windows XP client can upload a file, but a Windows 7 client cannot. And this with both IE and Firefox. I'll admit I'm stumped. Julie, is the bigger file which you are trying to upload the same in both cases (from XP and from Windows 7) ? Are both PC's in the same network section ? Is there a firewall or gateway between the clients and the server ? Are the clients accessing Tomcat directly, or through a front-end like Apache or IIS ? Fishing for straws.. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: About ContainerBackgroundProcessor thread
Many thanks Caldarale. I'm working with tomcat 6, but a I was looking so quickly for an answer that I didn't realise that it was the tomcat 3.2 user manual, but that explained me what happened. I think that WatchedResource will help me for this kind of tasks From: jmorati...@dit.upm.es [mailto:jmorati...@dit.upm.es] Subject: Re: About ContainerBackgroundProcessor thread Here is the explanation I found: http://tomcat.apache.org/tomcat-3.2-doc/uguide/tomcat_ug.html You can't seriously be using Tomcat 3.2, are you? That hasn't been supported for eons. In regards to your original question, if the reloadable attribute of the Context element is set to true, Tomcat will monitor /classes/ to see if the webapp has been updated. To quote from current documentation: Set to true if you want Catalina to monitor classes in /WEB-INF/classes/ and /WEB-INF/lib for changes, and automatically reload the web application if a change is detected. This feature is very useful during application development, but it requires significant runtime overhead and is not recommended for use on deployed production applications. You can also use a nested WatchedResource element to trigger reloads for other files; the default is just WEB-INF/web.xml. If you don't set reloadable and don't specify the file as a WatchedResource, Tomcat should not attempt to do anything with the webapp once it's started. But if you really are using Tomcat 3.2, I have no idea what it's behavior should be; move up to a supported level. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 6.0 and Windows 7
1. Yes, it's exactly the same file 2. What do you mean by network section ? 3. I'm not sure for the last questions (I'm not a server specialist, I'm more a java developer), I'll try to explain the environment : I installed the web application on a server : I installed Apache Tomcat (as a service) on the server machine and put my web application under Apache Software Foundation\Tomcat 6.0\webapps\ROOT. The first client machine is mine (running XP), the second one is another user's one, on which he just installed W7. Maybe an important fact : to access the web application, from a client machine, we have to connect to a VPN, to authentify... But once again, we do exactly the same operations (apparently in the same context, except the OS) and it works for me (XP) but not for the other user (W7). I could look further for the configuration if needed. Just tell me. I appreciate your help ! Many thanks ! Julie Gautier -Message d'origine- De : André Warnier [mailto:a...@ice-sa.com] Envoyé : lundi 27 septembre 2010 15:29 À : Tomcat Users List Objet : Re: Tomcat 6.0 and Windows 7 Caldarale, Charles R wrote: From: Maximilian Stocker [mailto:m...@talentoyster.com] Subject: RE: Tomcat 6.0 and Windows 7 Sorry but no. This statement does not match the localhost part you also mentioned. I'll bite. Why do you say that? The localhost part of the log file name refers to the Host name attribute, not any particular access from 127.0.0.1. So now that 3 of us agree that the server does not change, what can be the cause that a Windows XP client can upload a file, but a Windows 7 client cannot. And this with both IE and Firefox. I'll admit I'm stumped. Julie, is the bigger file which you are trying to upload the same in both cases (from XP and from Windows 7) ? Are both PC's in the same network section ? Is there a firewall or gateway between the clients and the server ? Are the clients accessing Tomcat directly, or through a front-end like Apache or IIS ? Fishing for straws.. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: About ContainerBackgroundProcessor thread
On 27.09.2010 15:42, jmorati...@dit.upm.es wrote: Many thanks Caldarale. I'm working with tomcat 6, but a I was looking so quickly for an answer that I didn't realise that it was the tomcat 3.2 user manual, but that explained me what happened. I think thatWatchedResource will help me for this kind of tasks Note that the watched resources means Tomcat will reload the webapp. I had the impression, you wanted to use a self-made mechanism that watches a resource and does some internal reconfiguration when the resource changes - but not a complete reload of the webapp. Regards, Rainer From: jmorati...@dit.upm.es [mailto:jmorati...@dit.upm.es] Subject: Re: About ContainerBackgroundProcessor thread Here is the explanation I found: http://tomcat.apache.org/tomcat-3.2-doc/uguide/tomcat_ug.html You can't seriously be using Tomcat 3.2, are you? That hasn't been supported for eons. In regards to your original question, if the reloadable attribute of the Context element is set to true, Tomcat will monitor /classes/ to see if the webapp has been updated. To quote from current documentation: Set to true if you want Catalina to monitor classes in /WEB-INF/classes/ and /WEB-INF/lib for changes, and automatically reload the web application if a change is detected. This feature is very useful during application development, but it requires significant runtime overhead and is not recommended for use on deployed production applications. You can also use a nestedWatchedResource element to trigger reloads for other files; the default is just WEB-INF/web.xml. If you don't set reloadable and don't specify the file as aWatchedResource, Tomcat should not attempt to do anything with the webapp once it's started. But if you really are using Tomcat 3.2, I have no idea what it's behavior should be; move up to a supported level. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.0 and Windows 7
On 27.9.2010 15:45, Julie Gautier wrote: I installed the web application on a server : I installed Apache Tomcat (as a service) on the server machine and put my web application under Apache Software Foundation\Tomcat 6.0\webapps\ROOT. The first client machine is mine (running XP), the second one is another user's one, on which he just installed W7. Maybe an important fact : to access the web application, from a client machine, we have to connect to a VPN, to authentify... For starters, I recommend upgrading to up-to-date version of Tomcat (say, 6.0.29). At least one bug [1] related to timeout issue is fixed in new version. -Ognjen [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=4 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 6.0 and Windows 7
Ok, I'll try. Thanks. Julie Gautier ACTES SUD 04 90 49 33 71 -Message d'origine- De : Ognjen Blagojevic [mailto:ognjen.d.blagoje...@gmail.com] Envoyé : lundi 27 septembre 2010 16:20 À : Tomcat Users List Objet : Re: Tomcat 6.0 and Windows 7 On 27.9.2010 15:45, Julie Gautier wrote: I installed the web application on a server : I installed Apache Tomcat (as a service) on the server machine and put my web application under Apache Software Foundation\Tomcat 6.0\webapps\ROOT. The first client machine is mine (running XP), the second one is another user's one, on which he just installed W7. Maybe an important fact : to access the web application, from a client machine, we have to connect to a VPN, to authentify... For starters, I recommend upgrading to up-to-date version of Tomcat (say, 6.0.29). At least one bug [1] related to timeout issue is fixed in new version. -Ognjen [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=4 - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Errors not logging to catalina.out after redeploy
On 9/23/10 8:15 PM, Roy McMorran wrote: We are observing an odd behavior after upgrading to 6.0.29. Ordinarily if an exception occurs this will be logged to catalina.out. When Tomcat is first started (we use jsvc) this is the case as expected. However if the webapp is redeployed (without a restart of Tomcat) errors are no longer logged to catalina.out. Restarting will return it to the normal behavior (until the next redeploy). Prior to upgrading we were using 6.0.20 and did not have this issue. Running under Solaris 10 with JDK 1.6.0_21. I'd be happy to provide any other information that might be useful. Any suggestions? Thanks! Well, we never did find out why this behavior changed, but we've implemented a workaround by configuring Tomcat to use log4j as described at http://tomcat.apache.org/tomcat-6.0-doc/logging.html#log4j and setting swallowOutput in the Context element. Now everything is logging to tomcat.log (instead of catalina.out) and it behaves the same way before and after any redeploy. Cheers, -- Roy McMorran Systems Administrator MDI Biological Laboratory mcmor...@mdibl.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Error in documentation, Tomcat 6
At the end of this page : http://tomcat.apache.org/tomcat-6.0-doc/logging.html#log4j there is this paragraph : If you have multiple instances of Tomcat, each with a separate $CATALINA_HOME but a shared $CATALINA_BASE, then you can configure log4j on a per instance basis by replacing references to $CATALINA_HOME in the above instructions with $CATALINA_BASE. Note that you may need to create a $CATALINA_BASE/lib directory. Is there not an inadvertent inversion in that paragraph ? Should it not be If you have multiple instances of Tomcat, each with a separate $CATALINA_BASE but a shared $CATALINA_HOME, then you can configure log4j on a per instance basis by replacing references to $CATALINA_HOME in the above instructions with $CATALINA_BASE. Note that you may need to create a $CATALINA_BASE/lib directory. Note that this has been fixed in the equivalent Tomcat 7 page at http://tomcat.apache.org/tomcat-7.0-doc/logging.html#log4j At first sight, it also looks as if the 6.0 version of the whole page could be fixed by overwriting it (apart from the header part) with the 7.0 version, which also corrects another couple of mistakes. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat ldap authentication with 403 Forbidden error
Hi, i'm working with Tomcat and i've configured a Realm for user authentication against Oracle OID. Sniffing the communication between the client and the OID server everything seems to be fine, but when the user authenticates the application then displays the 403 forbidden error page. This is the security section in the app web.xml, the role to validate is authenticated_users. It only works when I put the role as * but it doesn't when i put authenticated_users. Why could this be happening? security-constraint web-resource-collection web-resource-nameprotected/web-resource-name url-pattern/*/url-pattern /web-resource-collection auth-constraint role-nameauthenticated_users/role-name /auth-constraint /security-constraint security-role role-nameauthenticated_users/role-name /security-role login-config auth-methodFORM/auth-method form-login-config form-login-page/login.jsp/form-login-page form-error-page/error.jsp/form-error-page /form-login-config /login-config
Re: Error in documentation, Tomcat 6
On 27/09/2010 17:58, André Warnier wrote: At the end of this page : http://tomcat.apache.org/tomcat-6.0-doc/logging.html#log4j When looking at doc bugs I'd recommend working with the CI output which will reflect and changes since the last release. The link above will always be from the latest stable Tomcat 6 release so may not be 100% up to date. http://ci.apache.org/projects/tomcat/tomcat6/docs/logging.html In this case the bug is still present. there is this paragraph : If you have multiple instances of Tomcat, each with a separate $CATALINA_HOME but a shared $CATALINA_BASE, then you can configure log4j on a per instance basis by replacing references to $CATALINA_HOME in the above instructions with $CATALINA_BASE. Note that you may need to create a $CATALINA_BASE/lib directory. Is there not an inadvertent inversion in that paragraph ? Yep. Note that this has been fixed in the equivalent Tomcat 7 page at http://tomcat.apache.org/tomcat-7.0-doc/logging.html#log4j At first sight, it also looks as if the 6.0 version of the whole page could be fixed by overwriting it (apart from the header part) with the 7.0 version, which also corrects another couple of mistakes. Care to provide a patch? Offer of help with building etc. still stands if required. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
WAR Deployment before starting the cluster
Hello, We have 2 tomcat servers in cluster with session sharing and notifyListenersOnReplication=true. The application deployed uses a HttpSessionBindingListener to be aware of the number of licenses used by a user on the 2 servers. This configuration works great when the 2 servers are started at the same moment. The problem is: if one server restart, all the sessions will be replicated before the war is deployed so the listener, which is at an application level, will not be notified. Is it possible to deploy a war before starting the cluster service? Thanks, Romain
RE: Tomcat ldap authentication with 403 Forbidden error
From: Julio César Chaves Fernández [mailto:hent...@gmail.com] Subject: Tomcat ldap authentication with 403 Forbidden error i'm working with Tomcat What *exact* version? This is the security section in the app web.xml I don't see any security-role element in the above, which is required. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat ldap authentication with 403 Forbidden error
Hi, i'm working with Tomcat 5.5.31 ... but i've also tested this configuration on 6.0.29 and it displays the same error. The security-role is right below the security-constraint closing tag and above the login-config opening tag. Thanks. On Mon, Sep 27, 2010 at 12:37 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Julio César Chaves Fernández [mailto:hent...@gmail.com] Subject: Tomcat ldap authentication with 403 Forbidden error i'm working with Tomcat What *exact* version? This is the security section in the app web.xml I don't see any security-role element in the above, which is required. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
session won't timeout
Hi, I have a web app running on JBoss. I have made sure the following: 1. /jbossweb-tomcat55.sar/conf/web.xml to set the session timeout as 30 minutes: session-config session-timeout30/session-timeout /session-config 2. I am using sessionCreated/sessionDestroyed and valueBound/valueUnbound to monitor the active sessions in the system 3. there is no session-time setting in web.xml for the application since it has been configured in the tomcat. For some reason, some user's session just won't timeout and showing active in the system for days. The user has already closed the browser. What could be possible reasons for sessions being active for so long? Thanks in advance!
RE: Tomcat ldap authentication with 403 Forbidden error
From: Julio César Chaves Fernández [mailto:hent...@gmail.com] Subject: Re: Tomcat ldap authentication with 403 Forbidden error The security-role is right below the security-constraint closing tag and above the login-config opening tag. Sorry, I missed it. However, the security-role element normally comes /after/ login-config; not sure if that's required by the DTD, by your ordering is unusual. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: session won't timeout
On 27.09.2010 20:16, Jing Chen wrote: Hi, I have a web app running on JBoss. I have made sure the following: 1. /jbossweb-tomcat55.sar/conf/web.xml to set the session timeout as 30 minutes: session-config session-timeout30/session-timeout /session-config 2. I am using sessionCreated/sessionDestroyed and valueBound/valueUnbound to monitor the active sessions in the system 3. there is no session-time setting in web.xml for the application since it has been configured in the tomcat. For some reason, some user's session just won't timeout and showing active in the system for days. The user has already closed the browser. What could be possible reasons for sessions being active for so long? Exceptions in your session listener, preventing the cleanup? Add logging to your listener and activate an access log in Tomcat, adding %S to the log format, so that for each request the session id gets logged. Then try to find out, which sessions (IDs) do not get invalidated and check the log whether you can find something special about them. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: session won't timeout
From: Jing Chen [mailto:jin...@yahoo.com] Subject: session won't timeout For some reason, some user's session just won't timeout and showing active in the system for days. The user has already closed the browser. What could be possible reasons for sessions being active for so long? Use Tomcat's manager webapp or LambdaProbe or JMX and look at the expiration time for the session. It's possible that your webapp is programmatically resetting the session timeout value. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.0 and Windows 7
Hi is that all thats in the log. It appears read timeout should be caused by an upstream IO Exception. Wes On Mon, Sep 27, 2010 at 2:51 PM, Julie Gautier j.gaut...@actes-sud.fr wrote: Hello, I wrote a web application, that works great with a server under Tomcat 6.0.13 and client with Windows XP OS, in which user has to upload (text) files that are read and exploited. I tried this application (on a client machine) under Windows 7 and it works with uploaded files around 5-6 kb but if I try to upload a file around 60 kb, it doesn't work anymore and the localhost. .log trace file indicates the following error : org.apache.commons.fileupload.FileUploadException: Processing of multipart/form-data request failed. Read timed out at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:384) at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:268) at org.apache.struts.upload.CommonsMultipartRequestHandler.handleRequest(Common sMultipartRequestHandler.java:193) at org.apache.struts.util.RequestUtils.populate(RequestUtils.java:443) at org.apache.struts.action.RequestProcessor.processPopulate(RequestProcessor.j ava:796) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:203) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1192) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:430) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128 ) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104 ) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http 11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) Could you please help me to make my application work with client under Windows 7 ? Thanks in advance. Julie Gautier - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Unit testing a CometProcessor Servlet
Does anyone have tips for unit testing a servlet that implements CometProcessor? I have a servlet similar in structure to the the Chat Servlet example here: http://tomcat.apache.org/tomcat-6.0-doc/aio.html So, examples for testing that servlet code would be beneficial. Thanks in advance.
Re: Tomcat 6.0 and Windows 7
Wesley Acheson wrote: Hi is that all thats in the log. It appears read timeout should be caused by an upstream IO Exception. That is obviously what the server is saying. It seems that the server is trying to read what the browser should be sending, but that the browser closes the connection before everything is sent. So the server tries to read from a closed connection, and that triggers an exception. The question is : why is the server only saying that for the Windows-7 station, and with 2 different browsers ? Apart from possibly the bug which Ongjen mentioned, I would recommend to Julie the following : 1) On both the Windows XP and the Windows-7 machine, install the HttpFox plugin/extension into the Firefox browser (find it on the www). (This is a very useful plugin, which can show you everything that goes from the workstation 's Firefox to the server, and vice-versa. It is an essential tool to diagnose this kind of issue.) Then activate the plugin (in a separate window) on both workstations, and do the upload again. Then compare what you see in the HttpFox windows. 2) get another, 3rd PC, preferably also Windows-7, to do the same test. This is just to find out if the issue is particular to that one specific Windows-7 PC, or to Windows-7 PCs in general. Wes On Mon, Sep 27, 2010 at 2:51 PM, Julie Gautier j.gaut...@actes-sud.fr wrote: Hello, I wrote a web application, that works great with a server under Tomcat 6.0.13 and client with Windows XP OS, in which user has to upload (text) files that are read and exploited. I tried this application (on a client machine) under Windows 7 and it works with uploaded files around 5-6 kb but if I try to upload a file around 60 kb, it doesn't work anymore and the localhost. .log trace file indicates the following error : org.apache.commons.fileupload.FileUploadException: Processing of multipart/form-data request failed. Read timed out at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:384) at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.jav a:268) at org.apache.struts.upload.CommonsMultipartRequestHandler.handleRequest(Common sMultipartRequestHandler.java:193) at org.apache.struts.util.RequestUtils.populate(RequestUtils.java:443) at org.apache.struts.action.RequestProcessor.processPopulate(RequestProcessor.j ava:796) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:203) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1192) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:430) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128 ) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104 ) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http 11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) Could you please help me to make my application work with client under Windows 7 ? Thanks in advance. Julie Gautier - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat ldap authentication with 403 Forbidden error [solved]
It's solved. The problem is that the ldap group name is in uppercase while the security-role as well as the auth-constraint have the name in lowercase. Thanks. Le 27/09/2010 à 13:24, Caldarale, Charles R chuck.caldar...@unisys.com a écrit : From: Julio César Chaves Fernández [mailto:hent...@gmail.com] Subject: Re: Tomcat ldap authentication with 403 Forbidden error The security-role is right below the security-constraint closing tag and above the login-config opening tag. Sorry, I missed it. However, the security-role element normally comes /after/ login-config; not sure if that's required by the DTD, by your ordering is unusual. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6.0 and Windows 7
On 27/09/2010 14:45, Julie Gautier wrote: authentify... Like it. p 0x62590808.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
RE: Tomcat ldap authentication with 403 Forbidden error
Julio, --- On Mon, 9/27/10 at 11:24 AM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: The security-role is right below the security-constraint closing tag and above the login-config opening tag. Sorry, I missed it. However, the security-role element normally comes /after/ login-config; not sure if that's required by the DTD, by your ordering is unusual. In case you are still encountering a problem you could try listing the role(s) that have been assigned after authentication and comparing with authenticated-user; note that the comparison is case sensitive. - Bob - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat ldap authentication with 403 Forbidden error
Oops, just saw the [solved] msg... --- On Mon, 9/27/10 at 7:55 PM, Bob Hall rfha...@yahoo.com wrote: --- On Mon, 9/27/10 at 11:24 AM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: The security-role is right below the security-constraint closing tag and above the login-config opening tag. Sorry, I missed it. However, the security-role element normally comes /after/ login-config; not sure if that's required by the DTD, by your ordering is unusual. In case you are still encountering a problem you could try listing the role(s) that have been assigned after authentication and comparing with authenticated-user; note that the comparison is case sensitive. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat ldap authentication with 403 Forbidden error
Hehehe thanks anyway, i appreciate it. But yes, it was the comparison and the case of both words. Le 27/09/2010 à 21:57, Bob Hall rfha...@yahoo.com a écrit : Oops, just saw the [solved] msg... --- On Mon, 9/27/10 at 7:55 PM, Bob Hall rfha...@yahoo.com wrote: --- On Mon, 9/27/10 at 11:24 AM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: The security-role is right below the security-constraint closing tag and above the login-config opening tag. Sorry, I missed it. However, the security-role element normally comes /after/ login-config; not sure if that's required by the DTD, by your ordering is unusual. In case you are still encountering a problem you could try listing the role(s) that have been assigned after authentication and comparing with authenticated-user; note that the comparison is case sensitive. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
