Re: Unable to shutdown tomcat
Caldarale, Charles R wrote: From: Christopher Schultz [mailto:ch...@christopherschultz.net] Subject: Re: Unable to shutdown tomcat Thread-5 daemon prio=5 tid=7fe82c1f7000 nid=0x10c4bb000 waiting for monitor entry [] java.lang.Thread.State: BLOCKED (on object monitor) This thread might be a problem. Nope - it's a daemon, so it will go away quietly when the JVM shuts down. AWT-AppKit daemon prio=5 tid=7fe82f10d000 nid=0x7fff7a5b3960 runnable [] java.lang.Thread.State: RUNNABLE This thread might be a problem. Nope - it's a daemon, so it will go away quietly when the JVM shuts down. main prio=5 tid=7fe82c001800 nid=0x10448e000 runnable [10448b000] java.lang.Thread.State: RUNNABLE at sun.security.pkcs11.wrapper.PKCS11.C_GetSlotList(Native Method) at sun.security.pkcs11.SunPKCS11.init(SunPKCS11.java:314) at sun.security.pkcs11.SunPKCS11.init(SunPKCS11.java:86) at The main thread definitely looks like it's doing something a bit odd. Yes, this is the culprit. Since it's off in native code, it's much more difficult to figure out what it's stuck on. The C_GetSlotList() function would normally return immediately, so this one's very strange. If there are additional crypto libraries installed beyond the one that ships with the JVM, it might be hung up in one of those. The usual entropy suspect ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: GZIP support in Tomcat 7
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Akash, On 2/18/14, 7:45 PM, Akash Jain wrote: I have following configuration in my server.xml : Connector port=19380 protocol=HTTP/1.1 compression=on compressableMimeType=text/ html,text/xml,text/plain,application/javascript,application/json,text/javascript,text/json connectionTimeout=2 redirectPort=8443 / But still when I am checking for JS/CSS files in browser, the size returned is not less. Can anybody guide as to what I am missing here. How are you checking the size returned? Can you provide full request and response headers of an example request? Also this ? http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Standard_Implementation compressionMinSize If compression is set to on then this attribute may be used to specify the minimum amount of data before the output is compressed. If not specified, this attribute is defaults to 2048. .. and the note about using sendFile, just above ? There seems to be quite an amount of potential interaction between the various compression* and sendfile* attributes, also depending on the Connector being used, and whether it is APR or not. Maybe we're in one of those cases here ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Error redirection settings
Hi, I'm using tomcat apache-tomcat-6.0.37 I have a few web applications in webapps directory. portal sms crm I'm creating custom error pages. inside the webapplication portal under WEB-INF in web.xml I have given the following. error-page error-code400/error-code location/lp/404.html/location /error-page error-page error-code404/error-code location/lp/404.html/location /error-page error-page error-code500/error-code location/lp/oops.html/location /error-page error-page exception-typejava.lang.Throwable/exception-type location/lp/oops.html/location /error-page And is working fine for the errors like domain.com/portal/sdgggdhsh But for other web applications, obviously it wont work. because I haven't configured in their web.xml files. Is there any way I can give common error pages? I can see that there is a web.xml file under conf directory. And I have given the settings in it. As below. error-page error-code400/error-code location/404.html/location /error-page error-page error-code404/error-code location/404.html/location /error-page error-page error-code500/error-code location/oops.html/location /error-page error-page exception-typejava.lang.Throwable/exception-type location/oops.html/location /error-page Path I changed. starting from / and put the files in webapps directory. But it is not working. How can I do this? -- Randeep Mob: +919447831699[kerala] Mob: +919880050349[B'lore] I blog here: http://www.randeeppr.me/ Follow me Here: http://twitter.com/Randeeppr Poke me here! http://www.facebook.com/Randeeppr A little Linux Help http://www.linuxhelp.in/ Work profile: http://in.linkedin.com/in/randeeppr
[ANN] Apache Tomcat 7.0.52 released
The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.52. Apache Tomcat is an open source software implementation of the Java Servlet, JavaServer Pages and Java Expression Language technologies. This release contains a number of bug fixes and improvements compared to version 7.0.50. Please refer to the change log for the complete list of changes: http://tomcat.apache.org/tomcat-7.0-doc/changelog.html Note: This version has 4 zip binaries: a generic one and three bundled with Tomcat native binaries for Windows operating systems running on different CPU architectures. Note: Use of the JSR-356 Java WebSocket 1.0 implementation requires Java 7. Note: If you use the APR/native AJP or HTTP connector you *must* upgrade to version 1.1.29 or later of the APR/native library. Downloads: http://tomcat.apache.org/download-70.cgi Migration guides from Apache Tomcat 5.5.x and 6.0.x: http://tomcat.apache.org/migration.html
RE: Unable to shutdown tomcat
From: André Warnier [mailto:a...@ice-sa.com] Subject: Re: Unable to shutdown tomcat The C_GetSlotList() function would normally return immediately, so this one's very strange. If there are additional crypto libraries installed beyond the one that ships with the JVM, it might be hung up in one of those. The usual entropy suspect ? Possibly, but I wouldn't expect that for this particular API. However, there's no telling how a 3rd-party crypto library might be implemented. - 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: Error redirection settings
Randeep wrote: Hi, I'm using tomcat apache-tomcat-6.0.37 I have a few web applications in webapps directory. portal sms crm I'm creating custom error pages. inside the webapplication portal under WEB-INF in web.xml I have given the following. error-page error-code400/error-code location/lp/404.html/location /error-page error-page error-code404/error-code location/lp/404.html/location /error-page error-page error-code500/error-code location/lp/oops.html/location /error-page error-page exception-typejava.lang.Throwable/exception-type location/lp/oops.html/location /error-page And is working fine for the errors like domain.com/portal/sdgggdhsh But for other web applications, obviously it wont work. because I haven't configured in their web.xml files. Is there any way I can give common error pages? I can see that there is a web.xml file under conf directory. And I have given the settings in it. As below. error-page error-code400/error-code location/404.html/location /error-page error-page error-code404/error-code location/404.html/location /error-page error-page error-code500/error-code location/oops.html/location /error-page error-page exception-typejava.lang.Throwable/exception-type location/oops.html/location /error-page Path I changed. starting from / and put the files in webapps directory. But it is not working. How can I do this? After a search in Google for tomcat error-page location, I found this : http://stackoverflow.com/questions/3856145/empty-page-instead-of-custom-tomcat-error-page which seems to say that Tomcat will always prefix the given location with the context path of the application where the error happens. (For example, if you have location/oops.html/location, and if the error happens in your app /MyApp, then Tomcat will be looking for the file ...webapps/MyApp/oops.html). So you cannot have one generic location for these error pages, and share them for all applications. You have to add the error page to each deployed application, separately. More precisely : you can *define* the error pages, as you have done, in the generic conf/web.xml. But you still have to put a copy of the pages themselves in each application separately. I suppose that this obeys the general principle according to which each application should be self-contained. Maybe in later Tomcat versions, there would be a way around this via aliases or the likes, but it is probably still not recommended. Note also, separately : the URL path / resolves to .../webapps/ROOT/, not to .../webapps/. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Error redirection settings
On Wed, Feb 19, 2014 at 7:37 PM, André Warnier a...@ice-sa.com wrote: Randeep wrote: Hi, I'm using tomcat apache-tomcat-6.0.37 I have a few web applications in webapps directory. portal sms crm I'm creating custom error pages. inside the webapplication portal under WEB-INF in web.xml I have given the following. error-page error-code400/error-code location/lp/404.html/location /error-page error-page error-code404/error-code location/lp/404.html/location /error-page error-page error-code500/error-code location/lp/oops.html/location /error-page error-page exception-typejava.lang.Throwable/exception-type location/lp/oops.html/location /error-page And is working fine for the errors like domain.com/portal/sdgggdhsh But for other web applications, obviously it wont work. because I haven't configured in their web.xml files. Is there any way I can give common error pages? I can see that there is a web.xml file under conf directory. And I have given the settings in it. As below. error-page error-code400/error-code location/404.html/location /error-page error-page error-code404/error-code location/404.html/location /error-page error-page error-code500/error-code location/oops.html/location /error-page error-page exception-typejava.lang.Throwable/exception-type location/oops.html/location /error-page Path I changed. starting from / and put the files in webapps directory. But it is not working. How can I do this? After a search in Google for tomcat error-page location, I found this : http://stackoverflow.com/questions/3856145/empty-page- instead-of-custom-tomcat-error-page which seems to say that Tomcat will always prefix the given location with the context path of the application where the error happens. (For example, if you have location/oops.html/location, and if the error happens in your app /MyApp, then Tomcat will be looking for the file ...webapps/MyApp/oops.html). So you cannot have one generic location for these error pages, and share them for all applications. You have to add the error page to each deployed application, separately. More precisely : you can *define* the error pages, as you have done, in the generic conf/web.xml. But you still have to put a copy of the pages themselves in each application separately. I suppose that this obeys the general principle according to which each application should be self-contained. Maybe in later Tomcat versions, there would be a way around this via aliases or the likes, but it is probably still not recommended. Note also, separately : the URL path / resolves to .../webapps/ROOT/, not to .../webapps/. Thank you for the reply Andre. I'll add in all the webapps separately. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- Randeep Mob: +919447831699[kerala] Mob: +919880050349[B'lore] I blog here: http://www.randeeppr.me/ Follow me Here: http://twitter.com/Randeeppr Poke me here! http://www.facebook.com/Randeeppr A little Linux Help http://www.linuxhelp.in/ Work profile: http://in.linkedin.com/in/randeeppr
Can jasper2's validateXml be added back, at least for the lifetime of Tomcat 7?
Hi everyone, My project recently tried upgrading to Tomcat 7.0.52 and has become bit by the renaming of jasper2’s “validateXml” to “validateTld”, as described on the thread below. This change has made it more difficult pick up the latest Tomcat 7’s security fixes since the change breaks build scripts for quite a few projects maintained by different teams. Would it be possible to add back support for “validateXml” as part of the next minor release of Tomcat 7, as more or less described by Mark Thomas on that thread? http://mail-archives.apache.org/mod_mbox/tomcat-users/201401.mbox/%3ccd84922d-b159-49bd-9c11-6aaa5cb97...@email.android.com%3E This would save us a lot of effort, and we would then plan on switching to the new attribute name as part of adopting Tomcat 8. Thank you for any assistance on this! Sincerely, Mark DeSpain
