WebappClassLoader#getResources returns enumeration with null element
Hi, We just were informed about bug in Apache Struts [1] but it looks like a bug in Tomcat 8. The PackageBasedActionConfigBuilder class uses class loader to fetch all the URLs where application's classes are stored, but right now the resulting enumeration contains also null element. The same code works with no problems on Tomcat 7. If I add if(url != null) (see [2]) everything works as expected (but I must apply this ugly fix in few other places as well). [1] https://issues.apache.org/jira/browse/WW-4294 [2] https://github.com/apache/struts/blob/master/plugins/convention/src/main/java/org/apache/struts2/convention/PackageBasedActionConfigBuilder.java#L406 Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: WebappClassLoader#getResources returns enumeration with null element
On 03/03/2014 08:06, Lukasz Lenart wrote: Hi, We just were informed about bug in Apache Struts [1] but it looks like a bug in Tomcat 8. The PackageBasedActionConfigBuilder class uses class loader to fetch all the URLs where application's classes are stored, but right now the resulting enumeration contains also null element. The same code works with no problems on Tomcat 7. If I add if(url != null) (see [2]) everything works as expected (but I must apply this ugly fix in few other places as well). Including null in that enumeration doesn't look right but I do wonder (without having looked at the code) how it got there. I'll take a look. Mark [1] https://issues.apache.org/jira/browse/WW-4294 [2] https://github.com/apache/struts/blob/master/plugins/convention/src/main/java/org/apache/struts2/convention/PackageBasedActionConfigBuilder.java#L406 Regards - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
how to always return 200
webapp error-page error-code404/error-code location/index.jsp/location /error-page /webapp I need the above to return 200 not 404 how? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
Re: how to always return 200
2014-03-03 12:32 GMT+04:00 Aryeh Friedman aryeh.fried...@gmail.com: webapp error-page error-code404/error-code location/index.jsp/location /error-page /webapp I need the above to return 200 not 404 how? response.setStatus(..) ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Apache Tomcat Summit
All, The Apache Tomcat project will be holding a summit on Friday 11th April in Denver Colorado USA as part of ApacheCon NA 2014. The topics to be discussed will be finalized on the day by the attendees but the current list of topics is: - future development ideas prior to the next round of JavaEE specifications - AJP support for HTTP upgrade The list of topics is being maintained on the wiki [1]. If there is a topic you think needs to be discussed, please add it. If you'd like to attend, you can add it to your ApacheCon registration at no extra charge. For those of you that are not able to attend, the discussion will continue on the mailing lists after the event. We hope to see you there. Mark P.S. Don't forget that ApacheCon NA 2014 features an entire track dedicated to Apache Tomcat. See [2] for more details. [1] https://wiki.apache.org/tomcat/summit-na-2014 [2] http://events.linuxfoundation.org/events/apachecon-north-america/program/schedule - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: WebappClassLoader#getResources returns enumeration with null element
On 03/03/2014 08:23, Mark Thomas wrote: On 03/03/2014 08:06, Lukasz Lenart wrote: Hi, We just were informed about bug in Apache Struts [1] but it looks like a bug in Tomcat 8. The PackageBasedActionConfigBuilder class uses class loader to fetch all the URLs where application's classes are stored, but right now the resulting enumeration contains also null element. The same code works with no problems on Tomcat 7. If I add if(url != null) (see [2]) everything works as expected (but I must apply this ugly fix in few other places as well). Including null in that enumeration doesn't look right but I do wonder (without having looked at the code) how it got there. I'll take a look. When I looked at the stack trace, I thought it looked familiar: https://issues.apache.org/bugzilla/show_bug.cgi?id=56125 Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: WebappClassLoader#getResources returns enumeration with null element
2014-03-03 9:54 GMT+01:00 Mark Thomas ma...@apache.org: On 03/03/2014 08:23, Mark Thomas wrote: On 03/03/2014 08:06, Lukasz Lenart wrote: Hi, We just were informed about bug in Apache Struts [1] but it looks like a bug in Tomcat 8. The PackageBasedActionConfigBuilder class uses class loader to fetch all the URLs where application's classes are stored, but right now the resulting enumeration contains also null element. The same code works with no problems on Tomcat 7. If I add if(url != null) (see [2]) everything works as expected (but I must apply this ugly fix in few other places as well). Including null in that enumeration doesn't look right but I do wonder (without having looked at the code) how it got there. I'll take a look. When I looked at the stack trace, I thought it looked familiar: https://issues.apache.org/bugzilla/show_bug.cgi?id=56125 Yes, thanks Mark! Next time I will try spend more time on searching before asking :-) Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Add certificate without Tomcat restart
Hi. We have two-side authentification on our Tomcat: keystoreFile=/home/someuser/apache-tomcat-5.5.23/conf/.ssl/somealias.jks keyAlias=somealias keystorePass=somepass truststoreFile=/home/someuser/apache-tomcat-5.5.23/conf/.ssl/trustcacerts.jks truststorePass=somepass / Is there any way to add certificate to truststore and get Tomcat load it without restart it? I mean - after: $ keytool -import -v -trustcacerts -alias somealias -file some.cer -keystore ../trustcacerts.jks Thanks.
Re: Add certificate without Tomcat restart
2014-03-03 13:17 GMT+04:00 Арсений Зинченко setev...@gmail.com: Hi. We have two-side authentification on our Tomcat: keystoreFile=/home/someuser/apache-tomcat-5.5.23/conf/.ssl/somealias.jks keyAlias=somealias keystorePass=somepass truststoreFile=/home/someuser/apache-tomcat-5.5.23/conf/.ssl/trustcacerts.jks truststorePass=somepass / Is there any way to add certificate to truststore and get Tomcat load it without restart it? I mean - after: $ keytool -import -v -trustcacerts -alias somealias -file some.cer -keystore ../trustcacerts.jks AFAIK, you need to restart the Connector. This can be done via JMX. I am not sure whether start/stop is enough or you should go all way down to destroy/init. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Error while upgrading to Tomcat 7.0.52
Hi, I upgraded my application to 7.0.52 from 7.0.41. After upgrading while building and compiling whole application I am recieving error jasper2 doesn't support the validateXml attribute While looking in 1 of the blogs i found that the solution for this will be available only on 7.0.53 which is not yet available. Can you please let me know how i can proceed with this. If in case you need further details please let me know or feel free to reach to me in India IST. -Utkarsh Dave +919739903066 Technial Lead Infosys Limited at Cisco. e-city, Bangalore. India
Re: Error while upgrading to Tomcat 7.0.52
To be more specific, i upgraded Tomcat in my application from Tomcat 7.0.41 to 7.0.52. Quick response is appreciable as the build process is on hold critical services are shut down. -Thanks On Mon, Mar 3, 2014 at 3:39 PM, Utkarsh Dave utkarshkd...@gmail.com wrote: Hi, I upgraded my application to 7.0.52 from 7.0.41. After upgrading while building and compiling whole application I am recieving error jasper2 doesn't support the validateXml attribute While looking in 1 of the blogs i found that the solution for this will be available only on 7.0.53 which is not yet available. Can you please let me know how i can proceed with this. If in case you need further details please let me know or feel free to reach to me in India IST. -Utkarsh Dave +919739903066 Technial Lead Infosys Limited at Cisco. e-city, Bangalore. India
Re: Error while upgrading to Tomcat 7.0.52
2014-03-03 14:28 GMT+04:00 Utkarsh Dave utkarshkd...@gmail.com: To be more specific, i upgraded Tomcat in my application from Tomcat 7.0.41 to 7.0.52. Quick response is appreciable as the build process is on hold critical services are shut down. If you use the value of false, remove the attribute. false is the default value here. There is no reason to use it explicitly. If you use the value of true, remove the attribute now and restore it back when 7.0.53 is released. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Error while upgrading to Tomcat 7.0.52
On Mon, Mar 3, 2014 at 3:58 PM, Utkarsh Dave utkarshkd...@gmail.com wrote: To be more specific, i upgraded Tomcat in my application from Tomcat 7.0.41 to 7.0.52. Quick response is appreciable as the build process is on hold critical services are shut down. -Thanks On Mon, Mar 3, 2014 at 3:39 PM, Utkarsh Dave utkarshkd...@gmail.com wrote: Hi, I upgraded my application to 7.0.52 from 7.0.41. After upgrading while building and compiling whole application I am recieving error jasper2 doesn't support the validateXml attribute While looking in 1 of the blogs i found that the solution for this will be available only on 7.0.53 which is not yet available. Can you please let me know how i can proceed with this. If in case you need further details please let me know or feel free to reach to me in India IST. Hi Utkarsh Please use validateTld instead of validateXML. It would work . -Utkarsh Dave +919739903066 Technial Lead Infosys Limited at Cisco. e-city, Bangalore. India -- ~ Prashant Kadam
Re: Stream closed- IOException exception
please help ... I have removed whitespaces by adding jsp-config jsp-property-group url-pattern*.jsp/url-pattern trim-directive-whitespacestrue/trim-directive-whitespaces /jsp-property-group /jsp-config but still i am facing same error. I tried to increase the buffer size also as, %@ page buffer=800kb autoFlush=false % but still same error stuck on this issue for more than 2 weeks now and need to close it ASAP please help. Any help/ pointer would be highly appreciated. one more things, we are using struts version 1 and tiles 2.2. as struts1 doesn't work with tiles2, we have used struts-tiles2-1.4.0-SNAPSHOT.jar, can this create any problem, but this combination work with tomcat version below 7.0.37 and giving issues from version 7.0.39. Can anybody please tell me what are the changes in between these two versions which can produce this errror ?? Thanks Prashant Kadam On Mon, Mar 3, 2014 at 11:58 AM, Prashant Kadam prashantkada...@gmail.comwrote: On Sat, Mar 1, 2014 at 1:33 AM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Prashant, On 2/28/14, 7:54 AM, Prashant Kadam wrote: thanks Mark and Konstantin for your reply If you create the simplest possible JSP that demonstrates the issue (start with the one you have and remove as much as you can) and then post that JSP here, we can take a look. as you can see in stacktrace, there are many jsps forwarding request to another jsp, i am not sure how can I post jsp code. also one observation is, there is a struts action forward in between means jsp- struts action - jsp , If I remove this action call and include jsp directly in jsp then its working ... whether something wrong with tiles or struts or tomcat .. ? If you are doing a lot of JSP forwarding, you could be generating a lot of useless whitespace that is all being sent to the output buffer. Once that buffer fills up, the response headers will be sent to the client and and response is therefore committed. thanks for your reply seems logical ... and will try by removing white spaces .. still one question ... this is how it work it flows ... 1. jsp1 includes jsp2, 2. jsp2 forwards to jsp3 (using org.apache.struts.actions.ForwardAction) , 3. jsp3 forwards to strutsaction1, 4. strutsaction1 forwards to strutsaction2, 5. strutsaction2 forwards to jsp4, 6. and jsp4 includes jsp5 to render final view ... now if I remove 3,4,5 and directly include jsp4 into jsp3 it works. even I tried removing all business logic code in strutsaction1, strutsaction2, it is throwing same error .. so conclusion is whenever i am using struts action in between it is causing problem ... any thoughts ... ? If my analysis is correct, the difference between the Tomcat versions probably comes down to some small change in the way JSPs are compiled which may generate more whitespace if you haven't been careful. Take a look at all the JSPs that are participating in the request -- you should be able to inspect them to see why they might be generating whitespace. Remember, newlines are whitespace ;) I can see from your stack trace that you are using *includes*. Is there some other error that is occurring before this one? Does it happen on every request to this resource? yes this happen on every request for same resource ... this is exception that i can see when I put try catch in one of the jsp ,,, javax.servlet.jsp. JspException: javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: org.apache.jasper.JasperException: java.lang.IllegalStateException: Exception occurred when flushing data - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTEOt7AAoJEBzwKT+lPKRY6fYP+wWFNBtLRjUi1m6NPPpxajyp NBp0SZ5TIBs9c1fwAq3oKjodMDsgGMo59HApJpzHYyQhwuKHez3VLdGPss4aeq50 +Yc/UNhuMor31JWkPHzy05oSEFOQeKFn8Trw//OJ8m2giZSopt/05E8NRu9MIpUw +9eEsetJHs0502XCEFQ206/6MLxleGLA/sM5HTWJHg0NJczobTsHo40myy201Y1j Q7tO/gsyRzwljbHf0XByTTYUQNaNCaTzH0ydLiVeWCaPfxCpF4DXzrzdBu+BrL8U n5BlaizxMp9vd5DPucbRZidC0ihQpcaMjBAXnwg3OtbltX5EsMEYOfgD/TQXh5PC PFTPRm21OaybgNj13hNOOfmOCDw5AAA+znyVPFl4Ao+z67w0jIgSre49HMXfzYJQ a2pcDzCUuvbtXl22LJBVcnqlISLETiShulRzvAF5OiYwe2bJS4fOdWNSB8Nn7L7A +x//HxvTOem1dG5CaFRkCxvnkvK30e4LNCwY0AfErt3eKahHj0rJA+w/qiodTg2U bzh8kgRv+9v0fqV3RKVV/nO7WFRlyN6QIalCvLKPC+9CdajvBPUVC+gZgizs4pjT osHuIcGPmXMzycj1FfXzym5ucdy/WlJPUIBtliA4XnJ/RdBu1WfdB0c6rruiNflW vp1dKzQjPx5Zv58BU2l1 =pI9J -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- ~ Prashant Kadam -- ~ Prashant Kadam
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
Can you advice how we can find the problem in app/environment like this? What are possible ways to debug this? Regards, Dmitry Batiyevskiy Ardas Group Inc. www.ardas.dp.ua 2014-02-27 23:24 GMT+02:00 Christopher Schultz ch...@christopherschultz.net : -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dmitry, On 2/27/14, 3:27 PM, Dmitry Batiyevskiy wrote: This didn't helped, java process died with same error in about 5 hours Okay. The assert() call will in fact kill the process -- I had to check. It seems that for the time being, your only resource would be to switch to one of the pure-Java connectors until you are able to track-down the problem. We haven't been hearing a lot about this problem, so it looks like for now it's likely to be a problem with your application or environment. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTD60NAAoJEBzwKT+lPKRY8YEQAIFCUrgNaLwRgA1ktIyOwid/ bU/9CD93obj/vgsQbUkoDB4wneepGW5AFWVR0kk5tVWynjjg8JZNbiKtYoHX5FrJ Ig4hzzlUaETL/KNczeMwprmhARZSdMEl+QXXi9Evau/K7ngCUZUXGV8nTrCTGxtz XEmXp/UnSkRDKuD72TkYMFWNQhiZZjLBeqcba6B0SY80F0jj04r5yNW7dLDmNphx LUC+U6WtPyoo3IMj7V5KRTPcDTmjDsGIjp//lCf7kDZ9GyQTHasV85GBzxmuwvvj TeuD17cjOsOacEw4baxqI/ah1IboWkVHhdwEn/7Af6iUS+AI2J5lQmMej/DoZiJy y805A+xDTOap29vhZTx9d+PlTQnp0KCnHKfN8sRHBtQGdImarr8bQ9E5KI1GEiaP ezYRiM0Z0sA+sCq7dUMvFEjXXsNcoP1kInq3HjqRdaJd2LE6peRYDzJhPgXB3U22 NZSF6i4Ab8mSuueTQvX7UOhZG8s4chMdfcmw/W9e8lMG43MKkiuELHENzLarQwKe 6hOk6eUthYw1p1zSO53UxwgGAzC7yLAPQ/tvDZN1dbewUcOWNjQ9GzIDZ2WMTZRg TsGFz3CjmSo59q9VegmIA4DHMRXz0Zxrxzt2YjQEwXSYMoVAm8vcM3AssuorhAWi HCcozZP3IkQHc7eBZ2lW =xTw7 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Error while upgrading to Tomcat 7.0.52
Thanks Konstantin for the quick response. We are using false value, so i assume i can remove the attribute. As there are many level of developers involved, deleting and again adding it, will be difficult to track. I recieved another response, if i can replace validateTld instead of validateXML. Do you see any issue if we adopt this approach. -Thanks Utkarsh On Mon, Mar 3, 2014 at 4:16 PM, Konstantin Kolinko knst.koli...@gmail.comwrote: 2014-03-03 14:28 GMT+04:00 Utkarsh Dave utkarshkd...@gmail.com: To be more specific, i upgraded Tomcat in my application from Tomcat 7.0.41 to 7.0.52. Quick response is appreciable as the build process is on hold critical services are shut down. If you use the value of false, remove the attribute. false is the default value here. There is no reason to use it explicitly. If you use the value of true, remove the attribute now and restore it back when 7.0.53 is released. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Error while upgrading to Tomcat 7.0.52
Hi Prashant - I assume there will not be any consequence of replacing validateXML with validateTld? -Thanks for the quick response. -Utkarsh On Mon, Mar 3, 2014 at 4:19 PM, Prashant Kadam prashantkada...@gmail.comwrote: On Mon, Mar 3, 2014 at 3:58 PM, Utkarsh Dave utkarshkd...@gmail.com wrote: To be more specific, i upgraded Tomcat in my application from Tomcat 7.0.41 to 7.0.52. Quick response is appreciable as the build process is on hold critical services are shut down. -Thanks On Mon, Mar 3, 2014 at 3:39 PM, Utkarsh Dave utkarshkd...@gmail.com wrote: Hi, I upgraded my application to 7.0.52 from 7.0.41. After upgrading while building and compiling whole application I am recieving error jasper2 doesn't support the validateXml attribute While looking in 1 of the blogs i found that the solution for this will be available only on 7.0.53 which is not yet available. Can you please let me know how i can proceed with this. If in case you need further details please let me know or feel free to reach to me in India IST. Hi Utkarsh Please use validateTld instead of validateXML. It would work . -Utkarsh Dave +919739903066 Technial Lead Infosys Limited at Cisco. e-city, Bangalore. India -- ~ Prashant Kadam
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
On Thu, Feb 20, 2014 at 11:00 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: We have upgraded tomcat 7.0.42 to 7.0.50 We have an app which is built around atmosphere framework and uses websockets After upgrade tomcat instance which has only this app dies in few hours after deploy (the whole java process dies) How did you configure atmosphere? which version of atmosphere are you using? can you share your web.xml (atmosphere config)? which atmosphere-related dependencies? is atmosphere-related dependencies in tomcat/lib or in your WAR file?
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
On Mon, Mar 3, 2014 at 6:26 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: On Thu, Feb 20, 2014 at 11:00 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: We have upgraded tomcat 7.0.42 to 7.0.50 We have an app which is built around atmosphere framework and uses websockets After upgrade tomcat instance which has only this app dies in few hours after deploy (the whole java process dies) How did you configure atmosphere? which version of atmosphere are you using? can you share your web.xml (atmosphere config)? which atmosphere-related dependencies? is atmosphere-related dependencies in tomcat/lib or in your WAR file? also, are you specifying servlet 3.0 (or 2.5) in your web.xml? can you copy/paste that config as well?
Re: Error while upgrading to Tomcat 7.0.52
2014-03-03 15:09 GMT+04:00 Utkarsh Dave utkarshkd...@gmail.com: Thanks Konstantin for the quick response. We are using false value, so i assume i can remove the attribute. As there are many level of developers involved, deleting and again adding it, will be difficult to track. I recieved another response, if i can replace validateTld instead of validateXML. Do you see any issue if we adopt this approach. Beware that validateXml and validateTld are two different features in 7.0.53. Please do not top-post on this mailing list. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
Atmosphere dependencies from pom.xml: dependency groupIdorg.atmosphere.extensions/groupId artifactIdatmosphere-gwt20-server/artifactId version2.0.2/version /dependency dependency groupIdorg.atmosphere/groupId artifactIdatmosphere-runtime/artifactId version2.0.5/version /dependency Dependencies are in war file Atmosphere config from web.xml: servlet descriptionAtmosphereServlet/description servlet-nameAtmosphereServlet/servlet-name servlet-classorg.atmosphere.cpr.AtmosphereServlet/servlet-class load-on-startup1/load-on-startup async-supportedtrue/async-supported init-param param-nameorg.atmosphere.cpr.AtmosphereInterceptor/param-name param-valuecom.mycompany.communicationengine.interceptor.SecurityContextInterceptor/param-value /init-param init-param param-nameorg.atmosphere.cpr.packages/param-name param-valuecom.mycompany.atm/param-value /init-param init-param param-nameorg.atmosphere.useNative/param-name param-valuetrue/param-value /init-param init-param param-nameorg.atmosphere.cpr.broadcaster.maxProcessingThreads/param-name param-value30/param-value /init-param init-param param-nameorg.atmosphere.cpr.broadcaster.maxAsyncWriteThreads/param-name param-value30/param-value /init-param /servlet This is top of web.xml: web-app xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd; version=3.0 Regards, Dmitry Batiyevskiy Ardas Group Inc. www.ardas.dp.ua 2014-03-03 13:28 GMT+02:00 Howard W. Smith, Jr. smithh032...@gmail.com: On Mon, Mar 3, 2014 at 6:26 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: On Thu, Feb 20, 2014 at 11:00 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: We have upgraded tomcat 7.0.42 to 7.0.50 We have an app which is built around atmosphere framework and uses websockets After upgrade tomcat instance which has only this app dies in few hours after deploy (the whole java process dies) How did you configure atmosphere? which version of atmosphere are you using? can you share your web.xml (atmosphere config)? which atmosphere-related dependencies? is atmosphere-related dependencies in tomcat/lib or in your WAR file? also, are you specifying servlet 3.0 (or 2.5) in your web.xml? can you copy/paste that config as well?
Re: Stream closed- IOException exception
2014-03-03 15:04 GMT+04:00 Prashant Kadam prashantkada...@gmail.com: stuck on this issue for more than 2 weeks now and need to close it ASAP please help. Any help/ pointer would be highly appreciated. If nothing else helps, try running with a debugger to find when the said response is being committed. https://wiki.apache.org/tomcat/FAQ/Developing#Debugging A breakpoint can be set 1. On the place that throws IllegalStateException 2. On places that use ActionCode.COMMIT constant (org.apache.coyote.ActionCode). E.g. in org.apache.coyote.http11.AbstractHttp11Processor.action(...) Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Error while upgrading to Tomcat 7.0.52
On Mar 3, 2014, at 5:16 AM, Utkarsh Dave utkarshkd...@gmail.com wrote: Hi, I upgraded my application to 7.0.52 from 7.0.41. After upgrading while building and compiling whole application I am recieving error jasper2 doesn't support the validateXml attribute While looking in 1 of the blogs i found that the solution for this will be available only on 7.0.53 which is not yet available. Can you please let me know how i can proceed with this. If in case you need further details please let me know or feel free to reach to me in India IST. Try searching the archives. http://markmail.org/message/t5d54dkbhjk4prip Dan -Utkarsh Dave +919739903066 Technial Lead Infosys Limited at Cisco. e-city, Bangalore. India - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Error while upgrading to Tomcat 7.0.52
2014-03-03 15:52 GMT+04:00 Daniel Mikusa dmik...@gopivotal.com: On Mar 3, 2014, at 5:16 AM, Utkarsh Dave utkarshkd...@gmail.com wrote: Hi, I upgraded my application to 7.0.52 from 7.0.41. After upgrading while building and compiling whole application I am recieving error jasper2 doesn't support the validateXml attribute While looking in 1 of the blogs i found that the solution for this will be available only on 7.0.53 which is not yet available. Can you please let me know how i can proceed with this. If in case you need further details please let me know or feel free to reach to me in India IST. Try searching the archives. http://markmail.org/message/t5d54dkbhjk4prip That comment has already become obsolete, with http://svn.apache.org/viewvc?view=revisionrevision=1570163 Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Archiva fails to deploy on Tomcat with SEVERE: Unable to create initial connections of pool.
I'm trying to install Apache Archiva 2.0.0 on Tomcat 7 (installed from the Debian package). However when Tomcat 7 is started, I get this error in catalina.out: INFO: Deploying web application archive /var/lib/tomcat7/webapps/apache-archiva-2.0.0.war Feb 28, 2014 10:32:20 AM org.apache.tomcat.jdbc.pool.ConnectionPool init SEVERE: Unable to create initial connections of pool. java.sql.SQLException at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:254) at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182) at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701) at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635) at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:486) at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:144) at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:116) at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:103) at org.apache.tomcat.jdbc.pool.DataSourceFactory.createDataSource(DataSourceFactory.java:554) at org.apache.tomcat.jdbc.pool.DataSourceFactory.getObjectInstance(DataSourceFactory.java:242) at org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:141) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321) at org.apache.naming.NamingContext.lookup(NamingContext.java:842) at org.apache.naming.NamingContext.lookup(NamingContext.java:153) at org.apache.naming.NamingContext.lookup(NamingContext.java:830) at org.apache.naming.NamingContext.lookup(NamingContext.java:167) at org.apache.catalina.core.NamingContextListener.addResource(NamingContextListener.java:1091) at org.apache.catalina.core.NamingContextListener.createNamingContext(NamingContextListener.java:670) at org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:269) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5355) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.lang.NullPointerException at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:270) at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:246) ... 33 more My /etc/tomcat7/Catalina/localhost/archiva.xml looks like this: ?xml version=1.0 encoding=UTF-8? Context path=/apache-archiva-2.0.0 docBase=/var/lib/tomcat7/webapps/apache-archiva-2.0.0 Resource name=jdbc/users auth=Container type=javax.sql.DataSource username=sa password= driverClassName=org.apache.derby.jdbc.EmbeddedDriver url=jdbc:derby:/var/lib/archiva/users;create=true / Resource name=mail/Session auth=Container type=javax.mail.Session mail.smtp.host=localhost/ /Context I have derby.jar in /usr/share/tomcat7/libs and I see that the derby database in /var/lib/archiva/users/ is created correctly. I have placed my full catalina.out here: http://artipc10.vub.ac.be/~frederik/archiva/catalina.out and here is archiva.log: http://artipc10.vub.ac.be/~frederik/archiva/archiva.log Any idea what is going wrong? Regards Frederik - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Archiva fails to deploy on Tomcat with SEVERE: Unable to create initial connections of pool.
2014-03-03 16:37 GMT+04:00 Frederik Himpe fhi...@vub.ac.be: I'm trying to install Apache Archiva 2.0.0 on Tomcat 7 (installed from the Debian package). However when Tomcat 7 is started, I get this error in catalina.out: INFO: Deploying web application archive /var/lib/tomcat7/webapps/apache-archiva-2.0.0.war Feb 28, 2014 10:32:20 AM org.apache.tomcat.jdbc.pool.ConnectionPool init SEVERE: Unable to create initial connections of pool. java.sql.SQLException at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:254) at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182) at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701) at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635) at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:486) at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:144) at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:116) at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:103) at org.apache.tomcat.jdbc.pool.DataSourceFactory.createDataSource(DataSourceFactory.java:554) at org.apache.tomcat.jdbc.pool.DataSourceFactory.getObjectInstance(DataSourceFactory.java:242) at org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:141) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321) at org.apache.naming.NamingContext.lookup(NamingContext.java:842) at org.apache.naming.NamingContext.lookup(NamingContext.java:153) at org.apache.naming.NamingContext.lookup(NamingContext.java:830) at org.apache.naming.NamingContext.lookup(NamingContext.java:167) at org.apache.catalina.core.NamingContextListener.addResource(NamingContextListener.java:1091) at org.apache.catalina.core.NamingContextListener.createNamingContext(NamingContextListener.java:670) at org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:269) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5355) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.lang.NullPointerException at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:270) at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:246) ... 33 more My /etc/tomcat7/Catalina/localhost/archiva.xml looks like this: ?xml version=1.0 encoding=UTF-8? Context path=/apache-archiva-2.0.0 docBase=/var/lib/tomcat7/webapps/apache-archiva-2.0.0 Resource name=jdbc/users auth=Container type=javax.sql.DataSource username=sa password= driverClassName=org.apache.derby.jdbc.EmbeddedDriver url=jdbc:derby:/var/lib/archiva/users;create=true / Resource name=mail/Session auth=Container type=javax.mail.Session mail.smtp.host=localhost/ /Context I have derby.jar in /usr/share/tomcat7/libs and I see that the derby database in /var/lib/archiva/users/ is created correctly. I have placed my full catalina.out here: http://artipc10.vub.ac.be/~frederik/archiva/catalina.out From your catalina.out: [[[ Feb 28, 2014 10:32:05 AM org.apache.catalina.startup.HostConfig deployDescriptor WARNING: A docBase /var/lib/tomcat7/webapps/apache-archiva-2.0.0 inside the host appBase has been specified, and will be ignored ]]] You deployed your web application twice: 1. as archiva (thanks to archiva.xml), 2. as apache-archiva-2.0.0 (thanks to a subdirectory in
Re: Archiva fails to deploy on Tomcat with SEVERE: Unable to create initial connections of pool.
2014-03-03 17:31 GMT+04:00 Konstantin Kolinko knst.koli...@gmail.com: 2014-03-03 16:37 GMT+04:00 Frederik Himpe fhi...@vub.ac.be: I'm trying to install Apache Archiva 2.0.0 on Tomcat 7 (installed from the Debian package). However when Tomcat 7 is started, I get this error in catalina.out: INFO: Deploying web application archive /var/lib/tomcat7/webapps/apache-archiva-2.0.0.war Feb 28, 2014 10:32:20 AM org.apache.tomcat.jdbc.pool.ConnectionPool init SEVERE: Unable to create initial connections of pool. java.sql.SQLException at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:254) at org.apache.tomcat.jdbc.pool.PooledConnection.connect(PooledConnection.java:182) at org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(ConnectionPool.java:701) at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:635) at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:486) at org.apache.tomcat.jdbc.pool.ConnectionPool.init(ConnectionPool.java:144) at org.apache.tomcat.jdbc.pool.DataSourceProxy.pCreatePool(DataSourceProxy.java:116) at org.apache.tomcat.jdbc.pool.DataSourceProxy.createPool(DataSourceProxy.java:103) at org.apache.tomcat.jdbc.pool.DataSourceFactory.createDataSource(DataSourceFactory.java:554) at org.apache.tomcat.jdbc.pool.DataSourceFactory.getObjectInstance(DataSourceFactory.java:242) at org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceFactory.java:141) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321) at org.apache.naming.NamingContext.lookup(NamingContext.java:842) at org.apache.naming.NamingContext.lookup(NamingContext.java:153) at org.apache.naming.NamingContext.lookup(NamingContext.java:830) at org.apache.naming.NamingContext.lookup(NamingContext.java:167) at org.apache.catalina.core.NamingContextListener.addResource(NamingContextListener.java:1091) at org.apache.catalina.core.NamingContextListener.createNamingContext(NamingContextListener.java:670) at org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:269) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5355) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.lang.NullPointerException at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:270) at org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:246) ... 33 more My /etc/tomcat7/Catalina/localhost/archiva.xml looks like this: ?xml version=1.0 encoding=UTF-8? Context path=/apache-archiva-2.0.0 docBase=/var/lib/tomcat7/webapps/apache-archiva-2.0.0 Resource name=jdbc/users auth=Container type=javax.sql.DataSource username=sa password= driverClassName=org.apache.derby.jdbc.EmbeddedDriver url=jdbc:derby:/var/lib/archiva/users;create=true / Resource name=mail/Session auth=Container type=javax.mail.Session mail.smtp.host=localhost/ /Context I have derby.jar in /usr/share/tomcat7/libs and I see that the derby database in /var/lib/archiva/users/ is created correctly. I have placed my full catalina.out here: http://artipc10.vub.ac.be/~frederik/archiva/catalina.out From your catalina.out: [[[ Feb 28, 2014 10:32:05 AM org.apache.catalina.startup.HostConfig deployDescriptor WARNING: A docBase /var/lib/tomcat7/webapps/apache-archiva-2.0.0 inside the host appBase has been specified, and will be ignored ]]] You deployed your web application twice: 1. as archiva
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
On Mon, Mar 3, 2014 at 6:41 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: Atmosphere dependencies from pom.xml: dependency groupIdorg.atmosphere.extensions/groupId artifactIdatmosphere-gwt20-server/artifactId version2.0.2/version /dependency dependency groupIdorg.atmosphere/groupId artifactIdatmosphere-runtime/artifactId version2.0.5/version /dependency Looks good, but have you tried latest version (Atmosphere 2.1.0 runtime) ? I don't know the appropriate 'gwt' version to use with Atmosphere 2.1.0 runtime. I think you can search the atmosphere wiki or mail list, or post a mail there. I know that Atmosphere 2.0.3 had specific changes/fixes that were in-line with Tomcat 7.0.42, which supports your report that 7.0.42 is working (as expected). Dependencies are in war file okay. Atmosphere config from web.xml: servlet descriptionAtmosphereServlet/description servlet-nameAtmosphereServlet/servlet-name servlet-classorg.atmosphere.cpr.AtmosphereServlet/servlet-class load-on-startup1/load-on-startup async-supportedtrue/async-supported init-param okay, good, i was looking for the async-supported to be set, since you're using servlet 3.0. param-nameorg.atmosphere.cpr.AtmosphereInterceptor/param-name param-valuecom.mycompany.communicationengine.interceptor.SecurityContextInterceptor/param-value /init-param init-param param-nameorg.atmosphere.cpr.packages/param-name param-valuecom.mycompany.atm/param-value /init-param init-param param-nameorg.atmosphere.useNative/param-name param-valuetrue/param-value /init-param snip init-param param-nameorg.atmosphere.cpr.broadcaster.maxProcessingThreads/param-name param-value30/param-value /init-param init-param param-nameorg.atmosphere.cpr.broadcaster.maxAsyncWriteThreads/param-name param-value30/param-value /init-param /servlet /snip Jeanfrancois advised me to accept the default config/settings (for maxProcessingThreads and maxAsyncWriteThreads) instead of specifying low values like you have (30). what happens when you comment out these (atmosphere config) lines from your web.xml when using tomcat 7.0.50? maybe someone here on tomcat list can advise why your max threads settings is working with tomcat 7.0.42, but not with tomcat 7.0.50. This is top of web.xml: web-app xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd; version=3.0 okay, good. Regards, Dmitry Batiyevskiy Ardas Group Inc. www.ardas.dp.ua 2014-03-03 13:28 GMT+02:00 Howard W. Smith, Jr. smithh032...@gmail.com: On Mon, Mar 3, 2014 at 6:26 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: On Thu, Feb 20, 2014 at 11:00 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: We have upgraded tomcat 7.0.42 to 7.0.50 We have an app which is built around atmosphere framework and uses websockets After upgrade tomcat instance which has only this app dies in few hours after deploy (the whole java process dies) How did you configure atmosphere? which version of atmosphere are you using? can you share your web.xml (atmosphere config)? which atmosphere-related dependencies? is atmosphere-related dependencies in tomcat/lib or in your WAR file? also, are you specifying servlet 3.0 (or 2.5) in your web.xml? can you copy/paste that config as well?
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
Thanks, I will try updating atmosphere and/or changing maxProcessingThreads Regards, Dmitry Batiyevskiy Ardas Group Inc. www.ardas.dp.ua 2014-03-03 16:33 GMT+02:00 Howard W. Smith, Jr. smithh032...@gmail.com: On Mon, Mar 3, 2014 at 6:41 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: Atmosphere dependencies from pom.xml: dependency groupIdorg.atmosphere.extensions/groupId artifactIdatmosphere-gwt20-server/artifactId version2.0.2/version /dependency dependency groupIdorg.atmosphere/groupId artifactIdatmosphere-runtime/artifactId version2.0.5/version /dependency Looks good, but have you tried latest version (Atmosphere 2.1.0 runtime) ? I don't know the appropriate 'gwt' version to use with Atmosphere 2.1.0 runtime. I think you can search the atmosphere wiki or mail list, or post a mail there. I know that Atmosphere 2.0.3 had specific changes/fixes that were in-line with Tomcat 7.0.42, which supports your report that 7.0.42 is working (as expected). Dependencies are in war file okay. Atmosphere config from web.xml: servlet descriptionAtmosphereServlet/description servlet-nameAtmosphereServlet/servlet-name servlet-classorg.atmosphere.cpr.AtmosphereServlet/servlet-class load-on-startup1/load-on-startup async-supportedtrue/async-supported init-param okay, good, i was looking for the async-supported to be set, since you're using servlet 3.0. param-nameorg.atmosphere.cpr.AtmosphereInterceptor/param-name param-valuecom.mycompany.communicationengine.interceptor.SecurityContextInterceptor/param-value /init-param init-param param-nameorg.atmosphere.cpr.packages/param-name param-valuecom.mycompany.atm/param-value /init-param init-param param-nameorg.atmosphere.useNative/param-name param-valuetrue/param-value /init-param snip init-param param-nameorg.atmosphere.cpr.broadcaster.maxProcessingThreads/param-name param-value30/param-value /init-param init-param param-nameorg.atmosphere.cpr.broadcaster.maxAsyncWriteThreads/param-name param-value30/param-value /init-param /servlet /snip Jeanfrancois advised me to accept the default config/settings (for maxProcessingThreads and maxAsyncWriteThreads) instead of specifying low values like you have (30). what happens when you comment out these (atmosphere config) lines from your web.xml when using tomcat 7.0.50? maybe someone here on tomcat list can advise why your max threads settings is working with tomcat 7.0.42, but not with tomcat 7.0.50. This is top of web.xml: web-app xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd; version=3.0 okay, good. Regards, Dmitry Batiyevskiy Ardas Group Inc. www.ardas.dp.ua 2014-03-03 13:28 GMT+02:00 Howard W. Smith, Jr. smithh032...@gmail.com : On Mon, Mar 3, 2014 at 6:26 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: On Thu, Feb 20, 2014 at 11:00 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: We have upgraded tomcat 7.0.42 to 7.0.50 We have an app which is built around atmosphere framework and uses websockets After upgrade tomcat instance which has only this app dies in few hours after deploy (the whole java process dies) How did you configure atmosphere? which version of atmosphere are you using? can you share your web.xml (atmosphere config)? which atmosphere-related dependencies? is atmosphere-related dependencies in tomcat/lib or in your WAR file? also, are you specifying servlet 3.0 (or 2.5) in your web.xml? can you copy/paste that config as well?
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
On Mon, Mar 3, 2014 at 9:52 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: Thanks, I will try updating atmosphere and/or changing maxProcessingThreads may not be completely related, but what is your maxThreads value in your Connector .../ in server.xml ? mine is below (found in tomee/conf/server.xml) Connector port=8080 protocol=org.apache.coyote.http11.Http11NioProtocol maxThreads=150 connectionTimeout=2 acceptorThreadCount=2 redirectPort=8443 socket.directBuffer=false/ Regards, Dmitry Batiyevskiy Ardas Group Inc. www.ardas.dp.ua 2014-03-03 16:33 GMT+02:00 Howard W. Smith, Jr. smithh032...@gmail.com: On Mon, Mar 3, 2014 at 6:41 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: Atmosphere dependencies from pom.xml: dependency groupIdorg.atmosphere.extensions/groupId artifactIdatmosphere-gwt20-server/artifactId version2.0.2/version /dependency dependency groupIdorg.atmosphere/groupId artifactIdatmosphere-runtime/artifactId version2.0.5/version /dependency Looks good, but have you tried latest version (Atmosphere 2.1.0 runtime) ? I don't know the appropriate 'gwt' version to use with Atmosphere 2.1.0 runtime. I think you can search the atmosphere wiki or mail list, or post a mail there. I know that Atmosphere 2.0.3 had specific changes/fixes that were in-line with Tomcat 7.0.42, which supports your report that 7.0.42 is working (as expected). Dependencies are in war file okay. Atmosphere config from web.xml: servlet descriptionAtmosphereServlet/description servlet-nameAtmosphereServlet/servlet-name servlet-classorg.atmosphere.cpr.AtmosphereServlet/servlet-class load-on-startup1/load-on-startup async-supportedtrue/async-supported init-param okay, good, i was looking for the async-supported to be set, since you're using servlet 3.0. param-nameorg.atmosphere.cpr.AtmosphereInterceptor/param-name param-valuecom.mycompany.communicationengine.interceptor.SecurityContextInterceptor/param-value /init-param init-param param-nameorg.atmosphere.cpr.packages/param-name param-valuecom.mycompany.atm/param-value /init-param init-param param-nameorg.atmosphere.useNative/param-name param-valuetrue/param-value /init-param snip init-param param-nameorg.atmosphere.cpr.broadcaster.maxProcessingThreads/param-name param-value30/param-value /init-param init-param param-nameorg.atmosphere.cpr.broadcaster.maxAsyncWriteThreads/param-name param-value30/param-value /init-param /servlet /snip Jeanfrancois advised me to accept the default config/settings (for maxProcessingThreads and maxAsyncWriteThreads) instead of specifying low values like you have (30). what happens when you comment out these (atmosphere config) lines from your web.xml when using tomcat 7.0.50? maybe someone here on tomcat list can advise why your max threads settings is working with tomcat 7.0.42, but not with tomcat 7.0.50. This is top of web.xml: web-app xmlns=http://java.sun.com/xml/ns/javaee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd; version=3.0 okay, good. Regards, Dmitry Batiyevskiy Ardas Group Inc. www.ardas.dp.ua 2014-03-03 13:28 GMT+02:00 Howard W. Smith, Jr. smithh032...@gmail.com : On Mon, Mar 3, 2014 at 6:26 AM, Howard W. Smith, Jr. smithh032...@gmail.com wrote: On Thu, Feb 20, 2014 at 11:00 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: We have upgraded tomcat 7.0.42 to 7.0.50 We have an app which is built around atmosphere framework and uses websockets After upgrade tomcat instance which has only this app dies in few hours after deploy (the whole java process dies) How did you configure atmosphere? which version of atmosphere are you using? can you share your web.xml (atmosphere config)? which atmosphere-related dependencies? is atmosphere-related dependencies in tomcat/lib or in your WAR file? also, are you specifying servlet 3.0 (or 2.5) in your web.xml? can you copy/paste that config as well?
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
On Mon, Mar 3, 2014 at 6:41 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: init-param param-nameorg.atmosphere.useNative/param-name param-valuetrue/param-value /init-param also, i wonder what your test results will be if you comment out the lines above from your web.xml.
Re: tomcat 6 refuses mod_jk connections after server runs for a couple of days
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Issac, On 3/1/14, 12:41 AM, Isaac Gonzalez wrote: From: Christopher Schultz [ch...@christopherschultz.net] Sent: Friday, February 28, 2014 11:40 AM To: Tomcat Users List Subject: Re: tomcat 6 refuses mod_jk connections after server runs for a couple of days pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 1024 You might want to increase this number. How many processes is tomcat running outside of the JVM? This is likely to be the limit you are hitting. Tomcat is only running about 7 processes total, one for each JVM...but nothing else...unless I need to look beyond ps... Don't think this is it...but you never know Some *NIXs count individual threads as processes. You'll have to check in your own environment. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFKTgAAoJEBzwKT+lPKRYhK0P/0XBtTjcmIFE+tRIsR+SxTN2 T5wpkzqmjO7o1Q2+BRQXJyWIFB3EshlKjB4e3P6RkiqB9yWL5PV6N+7LqZGlJZSn AMWQDUIkszG7wP6E1lTMNm3IJRba0PGJlhsYb4BtTuxQyKJlqMNdzKw3OyETghbl ibOAPRHZZK9apQKSQKaO7CGOUv0+VAGTwwf1tcXv7UQVOqpryApuCWIrVNNMyrOD wiXioTj6qhbcl7i+x+qW2Nqk4ldkNGVKgS+3wfAjzUbFuXWfPMKRG7YCAltySP8W tZ+4SFAQ0GYTP0M2yoEC8+m8kXTOlDWHNeLPvhlU3NhFOCl25W9u1GHJyvFvjzKP IV+nglZ47qZryQYWYeiZOquM25hjuvCGT+r5o0enrca3VFxw7TCdYyDOq/CHLQjU +MaY9yXEuRYbXphdmWj0hEWyY+TirTEdumjFB1tVKrY87jr7biq2gyCtRC/mey8t xLLi3nYhHEqVDCPCv8pt+5nQg6AgQRqv3veBt8Z86p21JuuBcPoRYJy6aI0KpIms 11Xxe9M05M8W4b7wY+4U6vrxYVsEx6GVPEA8ZTsARTpwDjYeHRSQ5Tp9nRf9NrAf vCYtws9OkOfy7UOkEGQt4OLpuGHdld4rCEQfNwC+REuqW68r7+hE/bpqZwFFalP4 rf60cH024jR32N8gJvqn =ZKmN -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Could not publish server configuration for Tomcat v7.0 Server at localhost.
Hi Guys Just started using Tomcat v7..deployed my application and I am getting this error when I try to run; Could not publish server configuration for Tomcat v7.0 Server at localhost. Multiple Contexts have a path of /etm. Has anyone got this type of error before? Thanks, Frank Lugalla 314-212-27086 (office) 858-366-5733 (mobile) AMDOCS | EMBRACE CHALLENGE EXPERIENCE SUCCESS This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
Re: Newbie question: Installing Java EE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Bruce, On 3/1/14, 3:05 AM, Bruce Whealton wrote: Next question is with regard to the server. Is there any reason one would run both Tomcat and Glass-Fish server? I'm sure one could find a reason, but usually one would choose either a Java servlet container (like Tomcat) or a Java EE server (like Glassfish). If you like Tomcat and your EE needs are minimal, take a look at TomEE, which is a Tomcat core with a bunch of Java EE services available on top of it. TomEE would be more of a competitor to Glassfish than Tomcat would, because Tomcat has only the servlet, EL, and JSP specifications implemented from the Java EE collection. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFKskAAoJEBzwKT+lPKRYyFwP/RSGzzAXHZURAdqZ2eDnWVNO CgbhL/kVtSKc8wC54Eu8E0NlskiLHyLndzfTKYQjPh2K2zaNJAeaU+wPzNCHL6K7 jCdlOu72TAxiGsMtMajG4zWRWByygeWa6TWY60MQzsnj4uHPfPMs59ghiHHLwBlS XV8fmmQwxH/QcnJQmf8orsQD4oXqiVVVSn1nTkcMZ4l9Mw3y2jzcdau67jXlOARE mA7XEsA/FEH+AnI4oQ5U07Cy82aCWZCUvJSjtEi9O8/e6CCcSeOLGupefdTbVZl1 lG4dN6uRop/+rmTk8+pYhsRbqqiyX2x2/XqkUPAFYR8O+XYMA5taEhy3dHDU2J6Q h/imKD40qNFgaJp+YFXOmCYWKPANb2QC7tioxFX1UbgMaZiMUc495njGflFzK/Xw CT09lClFnGUc+lo7CiVjjTEIRCR3nnBg62hfszK1J+gDsjjAM1uV4XNRxychQDUg 7uM+zmuoA5eqFQNL+9+xGjfkObetPysCxBCP6tnqmgQ8VlQuNkZiayVOyF3yOp0i O7XvtEaRKxRebJvIhC04Uc4lNONrttlYI51WyxaIouPAvbWW/u/bm/2Urlg7bQJ3 2+apOIqpLGkBRGwNK2YASgAYXeDlYYt17EgNfLMRaJyRyod0PiS4ojUt6ZsOVFh2 y8rY7Rj7jot8krojxz71 =3J5x -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 8.0.3 hangs when ISAPI redirector sends an AJP request without request body
Hi,
I observed another strange problem when using Tomcat 8.0.3 with Java 1.7.0_51
(64-bit) on Windows Server 2012 R2, in conjunction with IIS 8.5 + ISAPI
Redirector 1.2.39 (the problem also happens with 1.2.37). I'm using the AJP NIO
and HTTP NIO connectors, but the problem also happens with AJP BIO and AJP APR.
The problem is: When I have a servlet that directly reads the request body, and
I send a HTTP request to IIS (GET or POST) with Content-Length: 0, Tomcat hangs
trying to read the request body. This does not happen when sending the same
request directly to Tomcat using the HTTP connector.
Consider this example servlet:
[[[
@WebServlet(/Servlet)
public class Servlet extends HttpServlet {
private static final long serialVersionUID = 1L;
protected void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
doRequest(request, response, false);
}
protected void doPost(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
doRequest(request, response, true);
}
private void doRequest(HttpServletRequest request, HttpServletResponse
response, boolean isPost) throws ServletException, IOException {
System.out.println(Method: + (isPost ? POST : GET) + . Reading
request body...);
long readCount = 0;
try (InputStream s = request.getInputStream()) {
byte[] buf = new byte[4096];
int read;
while ((read = s.read(buf)) 0)
readCount += read;
}
System.out.println(Reading request body finished, Byte Count: +
readCount);
response.setContentType(text/plain);
response.setCharacterEncoding(UTF-8);
try (PrintWriter w = response.getWriter()) {
w.println(Method: + (isPost ? POST : GET) + . Reading
request body...);
w.println(Request Body length in bytes: + readCount);
}
}
}
]]]
This servlet directly reads the request InputStream and counts the bytes that
it read.
When I now send the following HTTP requests directly to Tomcat (port 8080),
everything works as expected:
Request:
GET /TestWebapp/Servlet HTTP/1.1
Host: localhost
Connection: keep-alive
Content-Length: 10
0123456789
Response:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/plain;charset=UTF-8
Content-Length: 72
Date: Mon, 03 Mar 2014 15:39:35 GMT
Method: GET. Reading request body...
Request Body length in bytes: 10
Request:
GET /TestWebapp/Servlet HTTP/1.1
Host: localhost
Connection: keep-alive
Response:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/plain;charset=UTF-8
Content-Length: 71
Date: Mon, 03 Mar 2014 15:38:33 GMT
Method: GET. Reading request body...
Request Body length in bytes: 0
However, when I set the ISAPI Redirector for IIS 8.5 to forward every request
to Tomcat, using following worker.properties:
# Define 1 real worker using ajp13
worker.list=worker1
# Set properties for worker1 (ajp13)
worker.worker1.type=ajp13
worker.worker1.host=127.0.0.1
worker.worker1.port=8009
and uriworkermap.properties:
/*=worker1
Then, when I send the same requests to IIS, the one which has a body succeeds,
but the one which doesn't have a body does not finish:
Request:
GET /TestWebapp/Servlet HTTP/1.1
Host: localhost
Connection: keep-alive
Content-Length: 10
0123456789
Response:
HTTP/1.1 200 OK
Content-Length: 72
Content-Type: text/plain;charset=UTF-8
Server: Microsoft-IIS/8.5
X-Powered-By: ASP.NET
Date: Mon, 03 Mar 2014 15:41:49 GMT
Method: GET. Reading request body...
Request Body length in bytes: 10
Request:
GET /TestWebapp/Servlet HTTP/1.1
Host: localhost
Connection: keep-alive
Response:
(waits forever without sending a response...)
The same happens with this request:
POST /TestWebapp/Servlet HTTP/1.1
Host: localhost
Connection: keep-alive
Content-Length: 0
Response:
(waits forever without sending a response...)
In Tomcat's log you can see that Tomcat hangs at s.read(buf), so it seems it
somehow does not notice that the request body length is 0.
Any idea what's going on there?
Note: I do not yet have examined what AJP packets are sent between Tomcat and
ISAPI Redirector.
Regards,
Konstantin Preißer
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dmitry, On 3/3/14, 6:06 AM, Dmitry Batiyevskiy wrote: Can you advice how we can find the problem in app/environment like this? What are possible ways to debug this? Honestly, I'd try switching to the NIO connector and resume your testing. If all is well, it may point to a bug in the APR connector and/or tcnative itself. If you are having similar problems with the pure-Java connectors, then the problem is likely something you are doing in your application that is causing an invalid state. You'll probably get better information from the Java stack trace than from an assertion-failure. Give that a try and let us know how things go. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFKw/AAoJEBzwKT+lPKRY/hYP/RCK/AGsDHLUK6kiEON/m0jL C+32enJUz/p8xhWNGA9HpwjcwZmIW7fDNCQRiBBTs2bodtLW+//z5YTIvUPNM9Bq 9cCX25I+Z/2Dz4ZHfByeRXDNqhViPWhfjfKqAfxM0HSCKuRWF0w7ejUtN4w7bciM nTLG3rWG4HmhmSMfPIIzP0S48tzdXoriUPneMB6s1+h88uP1qvXB8XEsiXWCRaVN TLs5EaE6GksXj/LhpAkJh5HnD9yDxMklYl7soRHkogvenOOPQtMgD/5LnuxO2Ug9 FDQQuWLh6WYm5tPwSmPbcIaWsm/2xkEdCjtk1i9jrZxKKjGk+xWaaHp2ZNnxf/cr KPT94czieYlVc664NVM6OafnpUrVxZXQMuICCtaFqcnkFvOGja/TDr1FObEvkgNz JLUkDoB9NfPpQwQc5r3JF0L0IBAmM+WVOOv9GfmN8PdEIfvN2f4WPwQ5Ya9ExTJV Q70IkiKJBQ7OLpesIZOGqA4AHlGrhLMoMDAjfs9J6tVNSdMLpjGGIrOh60ka9oKb klYfsagEq0gqdgv9M2T4m91mbjwbWo+X+aBv0q7QtL+6vod449ybToXEzQ11CP3s +sU+6crBzUIUTIXu2JR3AGNKjUmIFYRwViiDa6l/MLu7fZGS9z9je6nduaZlJZ82 l6iV0qfUlrPKHyXm/b7v =8Q5O -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Howard, On 3/3/14, 10:09 AM, Howard W. Smith, Jr. wrote: On Mon, Mar 3, 2014 at 6:41 AM, Dmitry Batiyevskiy dmitry.batiyevs...@ardas.dp.ua wrote: init-param param-nameorg.atmosphere.useNative/param-name param-valuetrue/param-value /init-param also, i wonder what your test results will be if you comment out the lines above from your web.xml. Probably not... it's unlikely that Atmosphere knows anything about Tomcat's native capabilities. It's definitely tcnative that is throwing that assertion error. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFKyEAAoJEBzwKT+lPKRYFTYP/jWHZIEjSHHkmhIHvul/uAId O/6fQd44mfgjKgs6ykRPEt8HjZoiNWI8SKkjH86f13l0DGFE9/s9eLqPAj3m+MOt F3Q4uP32PDwMmZkd8tpq6CygunEtgOFNuUjwoj34dv0Fpuas1WoHJndIjpuzhGcb sksshvwtG9g56hxCG70bcy8CvoXbVc43CEb1ioOZ2s1fJi7R+C4Ft17s6EsYiICq 974bqDJziYbueDIjhL85tlr6+pHCXB/+7WZqOyFuhivqt42LPMC5HQajmLm/wwxo IfY4Fk+wYiQNKyQ9iffpvlbzoyxkDxrhyQq2Ly3ZO42bZM6JHLVU24KYt1aao0iR jdkS4YO4J5OEASnD8vpWKmVyTE+lB13Ef+cfDrd3VTQi8AbwyPqdEymiV1Ol8r9+ 9f+ZS4PzikjSDdF6A/ZMf8ul4r237Gu/a3wySbEnu0ygBAnJ3qEK4ll7D2UoLZdr wVOaorKLmXb8amEW0BFaFz1zsXpeaO45uClLQV8SJU5E9F+2nOWFPFx171vh8X5e WvCWqN+1ybbVLE/0sTj/ZxX5Uy32j05VnClKmuI9sBGeNEWVEWoLxlwpNmxSLY7G s0f+VkHik+7UjjCBiqi2CTI5kM3mjmvF+JgOEn1M51dJsLGaV8Mte/vWfg9IHabG oCwEyMv5s1WWr9rIj6ug =yqIe -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Could not publish server configuration for Tomcat v7.0 Server at localhost.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frank, On 3/3/14, 10:58 AM, Frank Lugalla wrote: Hi Guys Just started using Tomcat v7..deployed my application and I am getting this error when I try to run; Could not publish server configuration for Tomcat v7.0 Server at localhost. Multiple Contexts have a path of /etm. Has anyone got this type of error before? This sounds like a deployment-specific problem. How are you deploying to Tomcat? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFKz0AAoJEBzwKT+lPKRYHngP/Rn/lTFot17iCvxjTOvPFQNx 88iaydsU5MTuCIuv56ImCVsfZsnJeaFaCmVjzrBYPjB6WRYnpNtvkV8HzAywZZQD ZxSFscClikKsrfs2lUh8xpmdGMU/NcvbYKEGndZuB5oslFn6clqjNBlXifBUDzBi R9ae7eQxCUKh1cpvLNlkON0TtVdU5128VMbDByj70j2Eo1eQA+bxhgwjOht20eSx 02d0SQtf7L7IEXs4hqfOVJlydE/EY1v9fYPXlkVDjBwELeGARq4A0NSUYrPEZ60D KEVXu8bWKu7ArsolRSPgeYHOkY7/MRWBsainiNQ24pqWMcxPqTD5fnfrA/wasW+T h8oyAP3ebYYYViRSHnTOHJGaSVz1BEBfRbJEM5hkf0encBEb83Da6jHVa53XQOpQ dCuuRtF/X50mFw0qIUlK1JG5WB31OHrEwxaNiuUcECdid7Jh5OVfpojZ7gY/AGWt Iw+hvpBj8lQhMfCcCkw8PUfs1mrMCHlH+ZbmCEngGuNgiFFpeNzplUG8s16DYiHQ bj4x5c2kRj1DHq0KVPMlRAq3oiY7DJKjgmEckXc/2viff6iha62N+zjPLy4y+e1g chaS7rtmYISQ+fOUOHAGDgnjpHVzvbjZbzjYAjKDEMpzksXmaaudm/rc4QXD5Szl kMeJWbR1/2tPn7o+MAwe =nAMg -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 8.0.3 hangs when ISAPI redirector sends an AJP request without request body
-Original Message- From: Konstantin Preißer [mailto:kpreis...@apache.org] Sent: Monday, March 3, 2014 5:19 PM To: 'Tomcat Users List' Subject: Tomcat 8.0.3 hangs when ISAPI redirector sends an AJP request without request body snip Note: I do not yet have examined what AJP packets are sent between Tomcat and ISAPI Redirector. When sending the following request to IIS: POST /TestWebapp/Servlet HTTP/1.1 Host: localhost Connection: keep-alive Content-Length: 0 Then the ISAPI redirector sends the following AJP packet to Tomcat: [ID 3] Data - Offset: 0x0, Count: 0xB1. 12 34 00 AD 02 04 00 08 48 54 54 50 2F 31 2E 31 00 00 13 2F .4.HTTP/1.1.../ 54 65 73 74 57 65 62 61 70 70 2F 53 65 72 76 6C 65 74 00 00 TestWebapp/Servlet.. 09 31 32 37 2E 30 2E 30 2E 31 00 00 09 31 32 37 2E 30 2E 30 .127.0.0.1...127.0.0 2E 31 00 00 09 6C 6F 63 61 6C 68 6F 73 74 00 00 50 00 00 03 .1...localhost..P... A0 06 00 0A 6B 65 65 70 2D 61 6C 69 76 65 00 A0 08 00 01 30...keep-alive. ...0 00 A0 0B 00 09 6C 6F 63 61 6C 68 6F 73 74 00 03 00 00 00 04 . ...localhost.. 00 00 00 0A 00 0F 41 4A 50 5F 52 45 4D 4F 54 45 5F 50 4F 52 ..AJP_REMOTE_POR 54 00 00 05 34 39 34 38 32 00 0A 00 10 4A 4B 5F 4C 42 5F 41 T...49482JK_LB_A 43 54 49 56 41 54 49 4F 4E 00 00 03 41 43 54 00 FFCTIVATION...ACT.ÿ To me, this looks ok - as the request body is 0 (known in advance) AFAIK only the JK_AJP13_FORWARD_REQUEST packet should be sent to Tomcat. Note, that the Content-Length: 0 header is correctly included in the packet: A0 08 00 01 30 (0xA008 represents Content-Length). Regards, Konstantin Preißer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Stream closed- IOException exception
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Prashant, On 3/3/14, 6:04 AM, Prashant Kadam wrote: please help ... I have removed whitespaces by adding jsp-config jsp-property-group url-pattern*.jsp/url-pattern trim-directive-whitespacestrue/trim-directive-whitespaces /jsp-property-group /jsp-config but still i am facing same error. This may or may not do anything. I tried to increase the buffer size also as, %@ page buffer=800kb autoFlush=false % but still same error Hm. With a huge buffer, the only reason the response would have been committed is if a flush() was being called somewhere. You said you gutted the struts actions, but it's possible that somewhere, Struts is internally flushing the buffer. (That would surprise me, honestly). Are you sure there are no errors occurring anywhere? Often, an error will cause the response to be committed. BTW you probably never want to use autoFlush=false unless you are watching the buffer very carefully. For debugging, it's fine, but you certainly don't want to do that on a regular basis. stuck on this issue for more than 2 weeks now and need to close it ASAP please help. Remember that this is a community made up of volunteers. This problem / ticket is *yours* and not ours to be solved ASAP. Everybody's issues need to be solved ASAP, of course. If you want something done ASAP and you can't do it yourself, then you'll have to pay someone else to do it. Any help/ pointer would be highly appreciated. one more things, we are using struts version 1 and tiles 2.2. as struts1 doesn't work with tiles2, we have used struts-tiles2-1.4.0-SNAPSHOT.jar, can this create any problem, but this combination work with tomcat version below 7.0.37 and giving issues from version 7.0.39. Can anybody please tell me what are the changes in between these two versions which can produce this errror ?? You could take a look at the Changelog for version 7.0.39 (or .38) to see if anything looks probable. I recommend using a debugger as Konstantin suggests and trap the condition. You'll be able to unwind the stack to see what code is causing the response to be committed. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFLrqAAoJEBzwKT+lPKRYYx0P/jQ065OqO2xG+TiWv8Nkyht8 HMewLURHezpCkWM3Q2tCrV4mgTXLgvs1eOMBdi4LTjvzAdLjPNRBBQhR0bXjjIIS gAu92exfyuoBgN8mkgBTgZpmIFa/xPIbj+xDdImFHYcpHCrRw7ga4V9iyum27UQF JkXGz/qOegMattgF2k6Dgkz2UBN7QLwqnAqpaFo3m9XNqc6eQdTQWTzZ+MXX2tJ2 dndK+Bu+sdlWDeCtnegGO8ieh5GH0SB67ygSnBC/FPQOTDKojTpG7XbvrKonviUH 2u8S1gBuRClGGWXYv73LTCIYM5hpZA6S86nHD8UBciNTEx/rfLFtDGfpyb0lSVo8 4/kt/XIuqzmnrFkV2+Do2/xmorAs3QADlkmaK1e0cT1yVCBGUwU1FfalELj6JICj Wc73VB2SPDgwnY8qS1haa8V+LHZq4KVj9M1ZVf1buA7sFQTHeMsezP7KMmySJ6GU Ht70ubSvCIiEiSKT/gBeRcaTr1G6tyD4mObrKoz87BDMJbfe5yfkhguDKa3xvZLa +4oVvROVYklE1ZVAvY4IUH+LHTpWIL9HJFtWxi2C+KE0ihs8wq+iA+KMdkwB4W7H 9l231PiUE8ugya9K6qvDglPXhB5TvzIqpRoyb3lomESTwYuqDERYGRs3ouIVuJ3f vF1I9tIciTVKPwzRNESN =ukUm -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 7.0.52 stops after hours on our Sun Sparc with SunOS 5.10
Hello,
We newly installed Solaris 10 with all default settings on our Sun Sparc
machine (sun4u sparc SUNW,UltraAX-i2 64-bit sparcv9 kernel modules).
The OS Version: SunOS hostname 5.10 Generic_147147-26 sun4u sparc
SUNW,UltraAX-i2.
We downloaded and installed JDK packages as follows:
jdk-7u51-solaris-sparc.z
jdk-7u51-solaris-sparcv9.z
The Java in the environment:
java version 1.7.0_51
Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Client
VM (build 24.51-b03, mixed mode, sharing)
We downloaded the apache-tomcat-7.0.52.tar.gz and just unpacked it in
/export/home/tester.
Then we started the Tomcat server just using ./startup.sh without change of
any default settings.
The Tomcat is started ok listening at 8080 and we can see the Tomcat main
page on Web Browser at the port 8080.
But after several hours it stops itself without obvious reason (not manually
killed). and
It seems it was not a Shutdown command as there is no message of A valid
shutdown command was received via the shutdown port. in the log.
Is anyone aware about this issue?
Is it a configuration issue or environment issue?
Can you please provide any clues or check points?
Thanks,
Jay
PS. Here are the outputs from the logs:
#
# cat catalina.out
Feb 28, 2014 4:12:09 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path: /usr/jdk/packages/lib/sparc:/lib:/usr/lib
Feb 28, 2014 4:12:12 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-bio-8080]
Feb 28, 2014 4:12:12 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [ajp-bio-8009]
Feb 28, 2014 4:12:12 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 5782 ms
Feb 28, 2014 4:12:12 PM org.apache.catalina.core.StandardService
startInternal
INFO: Starting service Catalina
Feb 28, 2014 4:12:12 PM org.apache.catalina.core.StandardEngine
startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52
Feb 28, 2014 4:12:12 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/export/home/tester/apache-tomcat-7.0.52/webapps/manager
Feb 28, 2014 4:12:16 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/export/home/tester/apache-tomcat-7.0.52/webapps/docs
Feb 28, 2014 4:12:17 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/export/home/tester/apache-tomcat-7.0.52/webapps/examples
Feb 28, 2014 4:12:21 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/export/home/tester/apache-tomcat-7.0.52/webapps/ROOT
Feb 28, 2014 4:12:21 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/export/home/tester/apache-tomcat-7.0.52/webapps/host-manager
Feb 28, 2014 4:12:22 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [http-bio-8080]
Feb 28, 2014 4:12:22 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [ajp-bio-8009]
Feb 28, 2014 4:12:22 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 10031 ms
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [http-bio-8080]
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [ajp-bio-8009]
Mar 01, 2014 2:00:50 AM org.apache.catalina.core.StandardService
stopInternal
INFO: Stopping service Catalina
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler [http-bio-8080]
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler [ajp-bio-8009]
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler [http-bio-8080]
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler [ajp-bio-8009]
#
# cat localhost.2014-02-28.log
Feb 28, 2014 4:12:21 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Feb 28, 2014 4:12:21 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Feb 28, 2014 4:12:21 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener:
attributeAdded('org.apache.jasper.compiler.TldLocationsCache',
'org.apache.jasper.compiler.TldLocationsCache@19a2df9')
#
# cat localhost.2014-03-01.log
Mar 01, 2014 2:00:50 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextDestroyed()
Mar 01, 2014 2:00:50 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener:
Configuring mod_jk with multiple Apache HTTPD Virtual Hosts
Hello, I'm currently working on a project where we're migrating from Adobe Coldfusion 8 to CF 10. Adobe CF10 now uses tomcat as the underlying server and mod_jk is the standard connector used. On our test environment we have a single apache httpd instance serving multiple domains with each going to a different CF instance. We really only want specific workers enabled for specific virtual hosts like below. test1.abc.com -- HTTPD test1 VirtualHost -- CF Test1 test2.abc.com -- HTTPD test2 VirtualHost -- CF Test2 test3.abc.com -- HTTPD test3 VirtualHost -- CF Test3 Each CF instance is on a separate host. A developer has managed to get a config working on their local desktop where CF10 runs under windows and apache runs under a linux VM. The real dev environment is a lot more complicated with multiple virtual hosts. CF is the only one where we're going to use mod_jk (CF 8 used mod_jrun22) so this is the first time using mod_jk in our environment. Using the below config I keep getting JkWorkersFile cannot occur within VirtualHost section. Does anyone have any suggestions as to what I need to do to make this work? This is currently apache 2.2.26 compiled from source and mod_jk 1.2.37 compiled from source as well. VirtualHost Example VirtualHost 192.168.253.61:80 http://192.168.253.61/ DocumentRoot /web/app1.dev5.abc.com/scms ServerName app1.dev5.abc.com ServerAlias origin-app1.dev5.abc.com alias /shared-static /web/app1.dev5.abc.com/shared-static ErrorLog |/apps/httpd/bin/rotatelogs /weblogs/app1.dev5.abc-error.%Y%m%d 86400 -480 CustomLog |/apps/httpd/bin/rotatelogs /weblogs/app1.dev5.abc-access.%Y%m%d 86400 -480 combined env=!keepaliveuri DirectoryIndex index.cfm index.html index.html.var #AddDefaultCharset UTF-8 LoadModule jk_module /apps/httpd/modules/mod_jk.so IfModule mod_jk.c JkMount / cfusion JkMount /* cfusion # Where to find workers.properties JkWorkersFile /apps/httpd/conf.d/modjk/app1.dev5.workers.properties JkMountFile /apps/httpd/conf.d/modjk/app1.dev5.uriworkermap.properties # Where to put jk logs JkLogFile /weblogs/mod_jk.app1.dev5.log # custom environment variables JkEnvVar REDIRECT_URL JkEnvVar REDIRECT_REMOTE_HOST JkEnvVar REDIRECT_PATH JkEnvVar REDIRECT_QUERY_STRING JkEnvVar REDIRECT_HTTP_ACCEPT JkEnvVar REDIRECT_HTTP_USER_AGENT JkEnvVar REDIRECT_REMOTE_ADDR JkEnvVar REDIRECT_SERVER_NAME JkEnvVar REDIRECT_SERVER_PORT JkEnvVar REDIRECT_SERVER_SOFTWARE # Where to put jk shared memory JkShmFile /weblogs/app1.dev5.jk_shm # Set the jk log level [debug/error/info] JkLogLevel info # Select the timestamp log format JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkOptions +ForwardDirectories AddHandler jakarta-servlet .cfm .cfml .cfc .cfr .cfswf DirectoryIndex index.cfm Files ~ .hbmxml$ Order allow,deny Deny from all /Files /IfModule /VirtualHost
RE: Could not publish server configuration for Tomcat v7.0 Server at localhost.
Hi Chris, I right click and add my applications there -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Monday, March 03, 2014 10:25 AM To: Tomcat Users List Subject: Re: Could not publish server configuration for Tomcat v7.0 Server at localhost. -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frank, On 3/3/14, 10:58 AM, Frank Lugalla wrote: Hi Guys Just started using Tomcat v7..deployed my application and I am getting this error when I try to run; Could not publish server configuration for Tomcat v7.0 Server at localhost. Multiple Contexts have a path of /etm. Has anyone got this type of error before? This sounds like a deployment-specific problem. How are you deploying to Tomcat? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFKz0AAoJEBzwKT+lPKRYHngP/Rn/lTFot17iCvxjTOvPFQNx 88iaydsU5MTuCIuv56ImCVsfZsnJeaFaCmVjzrBYPjB6WRYnpNtvkV8HzAywZZQD ZxSFscClikKsrfs2lUh8xpmdGMU/NcvbYKEGndZuB5oslFn6clqjNBlXifBUDzBi R9ae7eQxCUKh1cpvLNlkON0TtVdU5128VMbDByj70j2Eo1eQA+bxhgwjOht20eSx 02d0SQtf7L7IEXs4hqfOVJlydE/EY1v9fYPXlkVDjBwELeGARq4A0NSUYrPEZ60D KEVXu8bWKu7ArsolRSPgeYHOkY7/MRWBsainiNQ24pqWMcxPqTD5fnfrA/wasW+T h8oyAP3ebYYYViRSHnTOHJGaSVz1BEBfRbJEM5hkf0encBEb83Da6jHVa53XQOpQ dCuuRtF/X50mFw0qIUlK1JG5WB31OHrEwxaNiuUcECdid7Jh5OVfpojZ7gY/AGWt Iw+hvpBj8lQhMfCcCkw8PUfs1mrMCHlH+ZbmCEngGuNgiFFpeNzplUG8s16DYiHQ bj4x5c2kRj1DHq0KVPMlRAq3oiY7DJKjgmEckXc/2viff6iha62N+zjPLy4y+e1g chaS7rtmYISQ+fOUOHAGDgnjpHVzvbjZbzjYAjKDEMpzksXmaaudm/rc4QXD5Szl kMeJWbR1/2tPn7o+MAwe =nAMg -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
secure reverse proxy to my tomcat server HELP NEEDED
The subject says it, I need help getting a secure reverse proxy to my tomcat server working. There is a lot of doc on the web, and it seems like I have everything configured properly, but I can't quite get the reverse proxy to work on the https side of things. Here is my config: Apache2.4.2 Ubuntu 12.04.2 LTS (GNU/Linux 3.2.0-24-generic x86_64) Tomcat 7.0.33 I simply want the reverse proxy to work so that https://my.webserver.com gets https://my.webserver.com:8443 (which is the secure tomcat server URL). I have the reverse proxy working so that http://my.webserver.com redirects the traffic on port 80 to the normal tomcat server on port 8080, and I also seem to have the secure tomcat server working because I can browse to https://my.webserver.com:8443 However when I bring up https://my.webserver.com, I get the contents of the Apache Root document at port 80. I'm using a self-signed cert. My httpd.conf file basically looks like (at least these are the important lines) Listen 80 ProxyRequests Off ProxyPreserveHost on VirtualHost *:80 ServerName my.webserver.com ProxyPass / http://my.webserver.com:8080/ ProxyPassReverse /app http://localhost:8080/ /VirtualHost proxy http://my.webserver.com:8080/ AllowOverride None Order Deny,Allow Allow from all /proxy Listen 443 VirtualHost *:443 SSLEngine on SSLProxyEngine on SSLCertificateFile /path/to/server.crt SSLCertificateKeyFile /path/to/server.key ServerName my.webserver.com ProxyPass / http://my.webserver.com:8443/ ProxyPassReverse /app http://localhost:8443/ /VirtualHost proxy https://my.webserver.com:8443/ AllowOverride None Order Deny,Allow Allow from all /proxy And my tomcat config (server.xml) connectors are defined like Connector port=8080 protocol=org.apache.coyote.http11.Http11NioProtocol maxHttpHeaderSize=8192 useBodyEncodingForURI=true maxThreads=1000 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=443 acceptCount=100 compression=on compressionMinSize=2048 compressableMimeType=text/html,text/xml,text/javascript,text/css,text/plain connectionTimeout=2 disableUploadTimeout=true URIEncoding=UTF-8/ Connector port=8443 protocol=HTTP/1.1 SSLEnabled=true maxThreads=150 scheme=https secure=false proxyPort=443 proxyName=my.webserver.com keystoreType= PKCS12 keystoreFile=/path/to/server.p12 keystorePass=changeit clientAuth=false sslProtocol=TLSv1 / I fire up tomcat and apache, I have debug loglevel set, and I don't see any real clues. The certificate files seem to be read fine and match my domain name. When I do the https://my.company.com/ request however, I see a debug line that says my client has obtained an HTTP connection to my.company.com. A few lines down, I see a line that says The timeout specified has expired: [client xxx.xxx.xxx.xxx:xxx] AH01991: SSL input filter read failed. But I also see the timeout messsage when I do a (successful) connection to https://my.company.com:8443 Currently no firewall rules set up, so nothing should be blocked. I'm not sure what to try at this point. The logfiles don't seem to any info that appears helpful. ANY suggestions would be appreciated. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: secure reverse proxy to my tomcat server HELP NEEDED
Can you change and retry below lines : ProxyPass / http://my.webserver.com:8443/ toProxyPass / https://my.webserver.com:8443/ http://my.webserver.com:8443/ ProxyPassReverse /app http://localhost:8443/ to ProxyPassReverse /app https://localhost:8443/ http://localhost:8443/ Thanks, Shailesh On Tue, Mar 4, 2014 at 1:44 AM, Jeff Haferman j...@haferman.com wrote: The subject says it, I need help getting a secure reverse proxy to my tomcat server working. There is a lot of doc on the web, and it seems like I have everything configured properly, but I can't quite get the reverse proxy to work on the https side of things. Here is my config: Apache2.4.2 Ubuntu 12.04.2 LTS (GNU/Linux 3.2.0-24-generic x86_64) Tomcat 7.0.33 I simply want the reverse proxy to work so that https://my.webserver.comgets https://my.webserver.com:8443 (which is the secure tomcat server URL). I have the reverse proxy working so that http://my.webserver.comredirects the traffic on port 80 to the normal tomcat server on port 8080, and I also seem to have the secure tomcat server working because I can browse to https://my.webserver.com:8443 However when I bring up https://my.webserver.com, I get the contents of the Apache Root document at port 80. I'm using a self-signed cert. My httpd.conf file basically looks like (at least these are the important lines) Listen 80 ProxyRequests Off ProxyPreserveHost on VirtualHost *:80 ServerName my.webserver.com ProxyPass / http://my.webserver.com:8080/ ProxyPassReverse /app http://localhost:8080/ /VirtualHost proxy http://my.webserver.com:8080/ AllowOverride None Order Deny,Allow Allow from all /proxy Listen 443 VirtualHost *:443 SSLEngine on SSLProxyEngine on SSLCertificateFile /path/to/server.crt SSLCertificateKeyFile /path/to/server.key ServerName my.webserver.com ProxyPass / http://my.webserver.com:8443/ ProxyPassReverse /app http://localhost:8443/ /VirtualHost proxy https://my.webserver.com:8443/ AllowOverride None Order Deny,Allow Allow from all /proxy And my tomcat config (server.xml) connectors are defined like Connector port=8080 protocol=org.apache.coyote.http11.Http11NioProtocol maxHttpHeaderSize=8192 useBodyEncodingForURI=true maxThreads=1000 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=443 acceptCount=100 compression=on compressionMinSize=2048 compressableMimeType=text/html,text/xml,text/javascript,text/css,text/plain connectionTimeout=2 disableUploadTimeout=true URIEncoding=UTF-8/ Connector port=8443 protocol=HTTP/1.1 SSLEnabled=true maxThreads=150 scheme=https secure=false proxyPort=443 proxyName=my.webserver.com keystoreType= PKCS12 keystoreFile=/path/to/server.p12 keystorePass=changeit clientAuth=false sslProtocol=TLSv1 / I fire up tomcat and apache, I have debug loglevel set, and I don't see any real clues. The certificate files seem to be read fine and match my domain name. When I do the https://my.company.com/ request however, I see a debug line that says my client has obtained an HTTP connection to my.company.com. A few lines down, I see a line that says The timeout specified has expired: [client xxx.xxx.xxx.xxx:xxx] AH01991: SSL input filter read failed. But I also see the timeout messsage when I do a (successful) connection to https://my.company.com:8443 Currently no firewall rules set up, so nothing should be blocked. I'm not sure what to try at this point. The logfiles don't seem to any info that appears helpful. ANY suggestions would be appreciated. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: secure reverse proxy to my tomcat server HELP NEEDED
Sorry, I made a couple of typos when I copied my stuff over and edited out my actual FQDN... I do have VirtualHost *:443 SSLEngine on SSLProxyEngine on SSLCertificateFile /path/to/server.crt SSLCertificateKeyFile /path/to/server.key ServerName my.webserver.com ProxyPass / https://my.webserver.com:8443/ ProxyPassReverse / https://my.webserver.com:8443/ /VirtualHost which I think is what you are suggesting? J Java wrote: --089e0160d0b63bc50904f3b99c68 Content-Type: text/plain; charset=ISO-8859-1 Can you change and retry below lines : ProxyPass / http://my.webserver.com:8443/ toProxyPass / https://my.webserver.com:8443/ http://my.webserver.com:8443/ ProxyPassReverse /app http://localhost:8443/ to ProxyPassReverse /app https://localhost:8443/ http://localhost:8443/ Thanks, Shailesh On Tue, Mar 4, 2014 at 1:44 AM, Jeff Haferman j...@haferman.com wrote: The subject says it, I need help getting a secure reverse proxy to my tomcat server working. There is a lot of doc on the web, and it seems like I have everything configured properly, but I can't quite get the reverse proxy to work on the https side of things. Here is my config: Apache2.4.2 Ubuntu 12.04.2 LTS (GNU/Linux 3.2.0-24-generic x86_64) Tomcat 7.0.33 I simply want the reverse proxy to work so that https://my.webserver.comgets https://my.webserver.com:8443 (which is the secure tomcat server URL). I have the reverse proxy working so that http://my.webserver.comredirects the traffic on port 80 to the normal tomcat server on port 8080, and I also seem to have the secure tomcat server working because I can browse to https://my.webserver.com:8443 However when I bring up https://my.webserver.com, I get the contents of the Apache Root document at port 80. I'm using a self-signed cert. My httpd.conf file basically looks like (at least these are the important lines) Listen 80 ProxyRequests Off ProxyPreserveHost on VirtualHost *:80 ServerName my.webserver.com ProxyPass / http://my.webserver.com:8080/ ProxyPassReverse /app http://localhost:8080/ /VirtualHost proxy http://my.webserver.com:8080/ AllowOverride None Order Deny,Allow Allow from all /proxy Listen 443 VirtualHost *:443 SSLEngine on SSLProxyEngine on SSLCertificateFile /path/to/server.crt SSLCertificateKeyFile /path/to/server.key ServerName my.webserver.com ProxyPass / http://my.webserver.com:8443/ ProxyPassReverse /app http://localhost:8443/ /VirtualHost proxy https://my.webserver.com:8443/ AllowOverride None Order Deny,Allow Allow from all /proxy And my tomcat config (server.xml) connectors are defined like Connector port=8080 protocol=org.apache.coyote.http11.Http11NioProtocol maxHttpHeaderSize=8192 useBodyEncodingForURI=true maxThreads=1000 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=443 acceptCount=100 compression=on compressionMinSize=2048 compressableMimeType=text/html,text/xml,text/javascript,text/css,text/plain connectionTimeout=2 disableUploadTimeout=true URIEncoding=UTF-8/ Connector port=8443 protocol=HTTP/1.1 SSLEnabled=true maxThreads=150 scheme=https secure=false proxyPort=443 proxyName=my.webserver.com keystoreType= PKCS12 keystoreFile=/path/to/server.p12 keystorePass=changeit clientAuth=false sslProtocol=TLSv1 / I fire up tomcat and apache, I have debug loglevel set, and I don't see any real clues. The certificate files seem to be read fine and match my domain name. When I do the https://my.company.com/ request however, I see a debug line that says my client has obtained an HTTP connection to my.company.com. A few lines down, I see a line that says The timeout specified has expired: [client xxx.xxx.xxx.xxx:xxx] AH01991: SSL input filter read failed. But I also see the timeout messsage when I do a (successful) connection to https://my.company.com:8443 Currently no firewall rules set up, so nothing should be blocked. I'm not sure what to try at this point. The logfiles don't seem to any info that appears helpful. ANY suggestions would be appreciated. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org --089e0160d0b63bc50904f3b99c68-- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: secure reverse proxy to my tomcat server HELP NEEDED
Jeff Haferman wrote: The subject says it, I need help getting a secure reverse proxy to my tomcat server working. Maybe one question here would be : why ? browser --- HTTPS -- httpd -- HTTPS -- Tomcat The browser encrypts and sends to httpd. httpd decrypts. httpd then re-encrypts and sends to Tomcat. Tomcat decrypts. and vice-versa on the way back. That is quite inefficient. And as your example configuration seems to show, httpd and Tomcat are running inside the same physical host, so the httpd -- Tomcat information does not circulate outside (of the physical host). What is the point then of this double encryption/decryption ? It is more usual in such a configuration to terminate HTTPS at the httpd level, like : browser --- HTTPS -- httpd -- HTTP -- Tomcat or browser --- HTTPS -- httpd -- AJP -- Tomcat and use non-encrypted data between httpd and Tomcat, saving yourself 2 encryption/decryption cycles for each request/response. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 8.0.3 hangs when ISAPI redirector sends an AJP request without request body
-Original Message- From: Konstantin Preißer [mailto:kpreis...@apache.org] Sent: Monday, March 3, 2014 5:38 PM When sending the following request to IIS: POST /TestWebapp/Servlet HTTP/1.1 Host: localhost Connection: keep-alive Content-Length: 0 Then the ISAPI redirector sends the following AJP packet to Tomcat: [...] To me, this looks ok - as the request body is 0 (known in advance) AFAIK only the JK_AJP13_FORWARD_REQUEST packet should be sent to Tomcat. Note, that the Content-Length: 0 header is correctly included in the packet: A0 08 00 01 30 (0xA008 represents Content-Length). I tested this now also with Tomcat 8.0.0-RC1 and 8.0.0-RC2, and found that the problem also happens with RC2 but not with RC1: With RC1, s.read() immediately returns so that the read byte count is 0, whereas with RC2, Tomcat hangs after sending the request. Unfortunately I was not able to find which revision introduced the change, as I was not able to build earlier Tomcat trunk SVN revisions - I always get the following error when running ant (this one was with r1518381): trydownload: BUILD FAILED C:\Users\Name\Desktop\Tomcat\tomcat\trunk\build.xml:2481: The following error occurred while executing this line: C:\Users\Name\Desktop\Tomcat\tomcat\trunk\build.xml:2685: the archive file.tar.gz doesn't exist Regards, Konstantin Preißer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Configuring mod_jk with multiple Apache HTTPD Virtual Hosts
Doug Strick wrote: Hello, I'm currently working on a project where we're migrating from Adobe Coldfusion 8 to CF 10. Adobe CF10 now uses tomcat as the underlying server and mod_jk is the standard connector used. On our test environment we have a single apache httpd instance serving multiple domains with each going to a different CF instance. We really only want specific workers enabled for specific virtual hosts like below. test1.abc.com -- HTTPD test1 VirtualHost -- CF Test1 test2.abc.com -- HTTPD test2 VirtualHost -- CF Test2 test3.abc.com -- HTTPD test3 VirtualHost -- CF Test3 Each CF instance is on a separate host. A developer has managed to get a config working on their local desktop where CF10 runs under windows and apache runs under a linux VM. The real dev environment is a lot more complicated with multiple virtual hosts. CF is the only one where we're going to use mod_jk (CF 8 used mod_jrun22) so this is the first time using mod_jk in our environment. Using the below config I keep getting JkWorkersFile cannot occur within VirtualHost section. Does anyone have any suggestions as to what I need to do to make this work? See http://tomcat.apache.org/connectors-doc/reference/apache.html quote JkWorkersFile The name of a worker file for the Tomcat servlet containers. This directive is only allowed once. It must be put into the global part of the configuration. [...] unquote And the same for the JkShmFile directive. The global part of the configuration refers to the main (or default) Apache httpd configuration file (apache2.conf or httpd.conf e.g.), *outside* of any VirtualHost section. The JkWorkersFile file defines *all* the workers (in mod_jk parlance, a worker is usually one back-end Tomcat instance). So in your case, you would have 3 workers (Test1, Test2 and Test3). Then inside of each VirtualHost section, you would use JkMount directives, to indicate *for this VirtualHost* which URI's should be proxied to which of the known workers. For example, in VirtualHost #1 JkMount /myapp/ Test1 JkMount /myapp/* Test1 in VirtualHost #2 JkMount /myapp/ Test2 JkMount /myapp/* Test2 in VirtualHost #3 JkMount /myapp/ Test3 JkMount /myapp/* Test3 Also, it does not really make much sense to have both JkMount directives directly in your configuration, *and* a JkMountFile directive. Usually, one uses the one or the other. It is less confusing, because both specify lists of URI's which should be/should not be proxied to Tomcat. Another configuration directive which should only be there once, and in the main httpd configuration section (not in VirtualHost) is LoadModule jk_module /apps/httpd/modules/mod_jk.so It is probably ignored when it occurs in a VirtualHost section. See http://httpd.apache.org/docs/2.2/mod/mod_so.html#loadmodule There are some other things which I find a bit strange (or unclear or redundant) in the configuration below, such as the conjunction of : DirectoryIndex index.cfm index.html index.html.var ... JkMount / cfusion JkMount /* cfusion ... AddHandler jakarta-servlet .cfm .cfml .cfc .cfr .cfswf DirectoryIndex index.cfm All in all, it looks a bit like an accumulation of miscellaneous overlapping and contradictory instructions, put together by chance more than by a good understanding of what each one really achieves and in what order they are evaluated. For example : JkMount / cfusion JkMount /* cfusion These directives will result in Apache httpd, in effect, proxying *all* requests to the Tomcat worker named cfusion, leaving none to be handled by Apache httpd itself. But then, these directives : DirectoryIndex index.cfm index.html index.html.var AddHandler jakarta-servlet .cfm .cfml .cfc .cfr .cfswf DirectoryIndex index.cfm are totaly redundant, even among themselves. This is currently apache 2.2.26 compiled from source and mod_jk 1.2.37 compiled from source as well. VirtualHost Example VirtualHost 192.168.253.61:80 http://192.168.253.61/ DocumentRoot /web/app1.dev5.abc.com/scms ServerName app1.dev5.abc.com ServerAlias origin-app1.dev5.abc.com alias /shared-static /web/app1.dev5.abc.com/shared-static ErrorLog |/apps/httpd/bin/rotatelogs /weblogs/app1.dev5.abc-error.%Y%m%d 86400 -480 CustomLog |/apps/httpd/bin/rotatelogs /weblogs/app1.dev5.abc-access.%Y%m%d 86400 -480 combined env=!keepaliveuri DirectoryIndex index.cfm index.html index.html.var #AddDefaultCharset UTF-8 LoadModule jk_module /apps/httpd/modules/mod_jk.so IfModule mod_jk.c JkMount / cfusion JkMount /* cfusion # Where to find workers.properties JkWorkersFile /apps/httpd/conf.d/modjk/app1.dev5.workers.properties JkMountFile /apps/httpd/conf.d/modjk/app1.dev5.uriworkermap.properties # Where to put jk logs
$CATALINA_HOME/conf/context.xml .. restrict a context?
Tomcat 6.X RHEL I tried adding the below in order to limit access to /admin-console It worked, but it limits access to EVERY context, which is odd. I am sure I am doing something wrong or I misunderstand how this works I want to put restrictions on the /admin-console context, but I do not want it inside the admin-console.war Again, this works, but other contexts are denied as well! Context path=/admin-console Valve className=org.apache.catalina.valves.RemoteAddrValve deny=* / /Context
Re: secure reverse proxy to my tomcat server HELP NEEDED
Yes, for development httpd and tomcat are on the same physical machine. Eventually they will be on different machines. But, even if I try browser --- HTTPS -- httpd -- HTTP -- Tomcat by just changing the ProxyPass and ProxyPassReverse directives to use the unencrypted URLs as follows VirtualHost *:443 SSLEngine on SSLProxyEngine on SSLCertificateFile /path/to/server.crt SSLCertificateKeyFile /path/to/server.key ServerName my.webserver.com ProxyPass / http://my.webserver.com:8080/ ProxyPassReverse / http://my.webserver.com:8080/ /VirtualHost the reverse proxy still does not serve the tomcat pages as I would expect. André Warnier wrote: Jeff Haferman wrote: The subject says it, I need help getting a secure reverse proxy to my tomcat server working. Maybe one question here would be : why ? browser --- HTTPS -- httpd -- HTTPS -- Tomcat The browser encrypts and sends to httpd. httpd decrypts. httpd then re-encrypts and sends to Tomcat. Tomcat decrypts. and vice-versa on the way back. That is quite inefficient. And as your example configuration seems to show, httpd and Tomcat are running inside the same physical host, so the httpd -- Tomcat information does not circulate outside (of the physical host). What is the point then of this double encryption/decryption ? It is more usual in such a configuration to terminate HTTPS at the httpd level, like : browser --- HTTPS -- httpd -- HTTP -- Tomcat or browser --- HTTPS -- httpd -- AJP -- Tomcat and use non-encrypted data between httpd and Tomcat, saving yourself 2 encryption/decryption cycles for each request/response. - 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: Configuring mod_jk with multiple Apache HTTPD Virtual Hosts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 André, On 3/3/14, 4:57 PM, André Warnier wrote: Doug Strick wrote: Hello, I'm currently working on a project where we're migrating from Adobe Coldfusion 8 to CF 10. Adobe CF10 now uses tomcat as the underlying server and mod_jk is the standard connector used. On our test environment we have a single apache httpd instance serving multiple domains with each going to a different CF instance. We really only want specific workers enabled for specific virtual hosts like below. test1.abc.com -- HTTPD test1 VirtualHost -- CF Test1 test2.abc.com -- HTTPD test2 VirtualHost -- CF Test2 test3.abc.com -- HTTPD test3 VirtualHost -- CF Test3 Each CF instance is on a separate host. A developer has managed to get a config working on their local desktop where CF10 runs under windows and apache runs under a linux VM. The real dev environment is a lot more complicated with multiple virtual hosts. CF is the only one where we're going to use mod_jk (CF 8 used mod_jrun22) so this is the first time using mod_jk in our environment. Using the below config I keep getting JkWorkersFile cannot occur within VirtualHost section. Does anyone have any suggestions as to what I need to do to make this work? See http://tomcat.apache.org/connectors-doc/reference/apache.html quote JkWorkersFile The name of a worker file for the Tomcat servlet containers. This directive is only allowed once. It must be put into the global part of the configuration. [...] unquote And the same for the JkShmFile directive. The global part of the configuration refers to the main (or default) Apache httpd configuration file (apache2.conf or httpd.conf e.g.), *outside* of any VirtualHost section. The JkWorkersFile file defines *all* the workers (in mod_jk parlance, a worker is usually one back-end Tomcat instance). So in your case, you would have 3 workers (Test1, Test2 and Test3). Then inside of each VirtualHost section, you would use JkMount directives, to indicate *for this VirtualHost* which URI's should be proxied to which of the known workers. For example, in VirtualHost #1 JkMount /myapp/ Test1 JkMount /myapp/* Test1 in VirtualHost #2 JkMount /myapp/ Test2 JkMount /myapp/* Test2 in VirtualHost #3 JkMount /myapp/ Test3 JkMount /myapp/* Test3 Also, it does not really make much sense to have both JkMount directives directly in your configuration, *and* a JkMountFile directive. Usually, one uses the one or the other. It is less confusing, because both specify lists of URI's which should be/should not be proxied to Tomcat. +1 It's bad enough that mod_jk has to have a separate configuration file (it's one of the only significant improvements mod_proxy_ajp has over mod_jk), but separating your configuration into 2 different files is going to confuse you in the long run. Along with this, I note that you are mapping / and /* to your mod_jk worker, and then also using AddHandler as well. I suspect you could probably remove all of your JkMount, JkMountFile, and AddHandler directives and replace them all with these: JkMount /*.cfm cfusion JkMount /*.cfml cfusion JkMount /*.cfc cfusion JkMount /*.cfr cfusion JkMount /*.cfswf cfusion This will *only* send requests for the above URL extensions to Tomcat, and everything else (static content, etc.) will be handled by httpd. You should probably set a DocumentRoot for this VirtualHost. I'm not sure if you ever had a problem with the one frontend - one backend configuration because you don't appear to have gotten that far. It's trivial to configure httpd to do that: just use different worker names for each back-end and then in httpd.conf, simply use one of them. If you ever want to load-balance, just create a balancing-worker that balances between the workers you're already defined and then use /that/ in httpd.conf. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFQAqAAoJEBzwKT+lPKRY4FMP/Axum0yT0E4g3tTuXkT+saHf jOF6/mwAjC60+WZONTJJRS7B2yli+rr50m1oRKuT0MjrBcnaHLjUH4sX0DhipVis 6G4+cYFNxcxPQR9T/qNXASKXb3g0LP+QzZ2Z6tuI7ouvfgG+2qM2tudLuzF82l3i 4ZrxYsD1wSyfLiz+HHpjiaNxmUuLe7CuDlWR1WBSaSet8Ekm1THaNpV7SulJIlOb 7hezzn9W+4DCmNONlMKkGywVTN3xQ0nr7erbDwoz/Q2MytpozN1duXeGC/CoZrQU 3/2FFtA3GxYzCz953p+7+KVnXYU0yrW7raMC7261x3XuHvn2QTQ1DU3BPqEIQWY3 fYvEXdq2tdu9BCrd0NtEd6pTJC9A4u2QqJUW2wgbdjTs+hlyFFS8kCwyWiwJhpbu xcfPEH91rj8pgq6u2lBM4QRtZWNo7fGYhs+EAMrsVoO0bHY8iXige2f6WlbmDHAC x/EW3O8Cpb3XFPofKG9VgFWtL/m8/OXKX4oy4AEpiyS/Sv0TkTiz6NXuIfYG6C9Q e1w1jMNET/CcJKCMtgL7mmS8skA0NXsXug9mLCu5tp1wK/3son9eJ5Eyc0QaoTTK eLO5MeNX5WZiEXGebTmy/wTsd9RXUJtzpqj1bzaye+1vjjd63f904u2vMDOom5ZR h2/oNGT7l3lph86+3giS =KRdb -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For
Re: Tomcat 7.0.52 stops after hours on our Sun Sparc with SunOS 5.10
2014-03-03 21:29 GMT+04:00 Jay mx...@live.com:
Hello,
We newly installed Solaris 10 with all default settings on our Sun Sparc
machine (sun4u sparc SUNW,UltraAX-i2 64-bit sparcv9 kernel modules).
The OS Version: SunOS hostname 5.10 Generic_147147-26 sun4u sparc
SUNW,UltraAX-i2.
We downloaded and installed JDK packages as follows:
jdk-7u51-solaris-sparc.z
jdk-7u51-solaris-sparcv9.z
The Java in the environment:
java version 1.7.0_51
Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) Client
VM (build 24.51-b03, mixed mode, sharing)
We downloaded the apache-tomcat-7.0.52.tar.gz and just unpacked it in
/export/home/tester.
Then we started the Tomcat server just using ./startup.sh without change of
any default settings.
The Tomcat is started ok listening at 8080 and we can see the Tomcat main
page on Web Browser at the port 8080.
But after several hours it stops itself without obvious reason (not manually
killed). and
It seems it was not a Shutdown command as there is no message of A valid
shutdown command was received via the shutdown port. in the log.
Is anyone aware about this issue?
Is it a configuration issue or environment issue?
Can you please provide any clues or check points?
Thanks,
Jay
PS. Here are the outputs from the logs:
#
# cat catalina.out
Feb 28, 2014 4:12:09 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path: /usr/jdk/packages/lib/sparc:/lib:/usr/lib
Feb 28, 2014 4:12:12 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-bio-8080]
Feb 28, 2014 4:12:12 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [ajp-bio-8009]
Feb 28, 2014 4:12:12 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 5782 ms
Feb 28, 2014 4:12:12 PM org.apache.catalina.core.StandardService
startInternal
INFO: Starting service Catalina
Feb 28, 2014 4:12:12 PM org.apache.catalina.core.StandardEngine
startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52
Feb 28, 2014 4:12:12 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/export/home/tester/apache-tomcat-7.0.52/webapps/manager
Feb 28, 2014 4:12:16 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/export/home/tester/apache-tomcat-7.0.52/webapps/docs
Feb 28, 2014 4:12:17 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/export/home/tester/apache-tomcat-7.0.52/webapps/examples
Feb 28, 2014 4:12:21 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/export/home/tester/apache-tomcat-7.0.52/webapps/ROOT
Feb 28, 2014 4:12:21 PM org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory
/export/home/tester/apache-tomcat-7.0.52/webapps/host-manager
Feb 28, 2014 4:12:22 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [http-bio-8080]
Feb 28, 2014 4:12:22 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [ajp-bio-8009]
Feb 28, 2014 4:12:22 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 10031 ms
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [http-bio-8080]
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [ajp-bio-8009]
Mar 01, 2014 2:00:50 AM org.apache.catalina.core.StandardService
stopInternal
INFO: Stopping service Catalina
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler [http-bio-8080]
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler [ajp-bio-8009]
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler [http-bio-8080]
Mar 01, 2014 2:00:50 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler [ajp-bio-8009]
#
# cat localhost.2014-02-28.log
Feb 28, 2014 4:12:21 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Feb 28, 2014 4:12:21 PM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Feb 28, 2014 4:12:21 PM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener:
attributeAdded('org.apache.jasper.compiler.TldLocationsCache',
'org.apache.jasper.compiler.TldLocationsCache@19a2df9')
#
# cat localhost.2014-03-01.log
Mar 01, 2014 2:00:50 AM
Re: $CATALINA_HOME/conf/context.xml .. restrict a context?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ravi, On 3/3/14, 5:10 PM, Ravi Gupta wrote: Tomcat 6.X RHEL I tried adding the below in order to limit access to /admin-console It worked, but it limits access to EVERY context, which is odd. I am sure I am doing something wrong or I misunderstand how this works I want to put restrictions on the /admin-console context, but I do not want it inside the admin-console.war Again, this works, but other contexts are denied as well! Context path=/admin-console Valve className=org.apache.catalina.valves.RemoteAddrValve deny=* / /Context I'm guessing the file you edited was CATALINA_BASE/conf/context.xml? That's not the right file to edit. Undo all the changes you made to conf/context.xml. Instead, you want to edit the META-INF/context.xml file in your own webapp (or CATALINA_BASE/conf/[engine]/[host]/admin-console.xml if you have manually-deployed your application using an XML descriptor). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFQCoAAoJEBzwKT+lPKRYGXQQAKgWOzPpKvC9YvuSJWdDY5Ud 325eSaK73rns77SWz2nUFt3je5GTEFmQAuCyBHueeaGgaFsY9GrkE9/YtsuWxB52 gO22zYywmTtfSY4MNt5z4dolbWfkktcFkLA96FQxa4ZI7ZdvmyL4XRRPJSSKRck3 qushWLC5IhbTknnbbOFm3OAv/xY60dzorB8ashIDjMO1Rm+6xOWf2x3PeTAeuy8K h5rKVi1u2KkMnbMtvJABX2WGdYZA+r/LNozotXHDGApvEVFu4+YtRWpZx2kgeVVG 0pbgLlfmT3cltDGkfOLq7xk11/VJNVR/A276naolfA+lWlqg0ccTVy7T/HrYaVZ8 dHXh09GFAgxneC+JCdMzDGFaI1LEhMaDv9OhyEYCOjoz60c1lYg2idfFXffSTiFj QRgfesyer8jYWD0pyEQ939EOXKLnR2ClbwqkHvXZNKDf8NtitBeF45hUmxixuDhb GBu+tuBVEHWXJpmCkmh/Xd9iwGPU3w2geGnZXPUpDaERdKlKL/zbzLBpxvP9TpOs 0IMc3ZkZ39jnrMVfDbbloNRKMdbxSSlb/OMyDocZheSLw6QlECALfLZumQZCk759 z5BDS8zvINbpdUrUxLG7ZYTW+6ZXpR7N9nVF+ab2BnTC58J5aUb623FtSOuk1J2/ hMPVhRwdGyHLNccn82t4 =YZJb -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: secure reverse proxy to my tomcat server HELP NEEDED
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jeff, On 3/3/14, 5:11 PM, Jeff Haferman wrote: Yes, for development httpd and tomcat are on the same physical machine. Eventually they will be on different machines. But, even if I try browser --- HTTPS -- httpd -- HTTP -- Tomcat by just changing the ProxyPass and ProxyPassReverse directives to use the unencrypted URLs as follows VirtualHost *:443 SSLEngine on SSLProxyEngine on SSLCertificateFile /path/to/server.crt SSLCertificateKeyFile /path/to/server.key ServerName my.webserver.com ProxyPass / http://my.webserver.com:8080/ ProxyPassReverse / http://my.webserver.com:8080/ /VirtualHost the reverse proxy still does not serve the tomcat pages as I would expect. Given the above setup, what /actually/ happens when you try to request a resource that should go to Tomcat? does not serve pages as I expect is not a good description. Oh, and everyone posting NEEDS HELP to it's not necessary to add HELP NEEDED or similar text to your subjects. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFQFUAAoJEBzwKT+lPKRY2HYP+wb7xl7KYjOP6svlQE8qmI6r B8d/wUdteORgBK+kFjVZhsK8w14pvHIg5Ujxzigk8SMfwWXEFF/gwJCR+r/9lBIZ nKqarrMr3fwnY0AubTcnraYSywKofGmOPDXjOJFjZqQ/r9DdVaSVZuNCrdN+WL0I 26NXuRvEv9aJyIcYxTH8NHyFgmqZYhiylkQ7NTtR1Fp5sp9pHvy77JMbfxymaiQq Ac0sNbrNCf7BgmKqwe1E9cWDVcXIoYoYNbKZ0lY06t37IVsOdJW4Qru95XRnSBt9 DgMUBqVB0AQ0cxlu1h6qAhzgt7VuAE685ap3/HGlNv6r6PNgNIO69PRyPb+MvGEX P77avVNGLKKeYz0JtvlxNTwsemNTQMJj3nqYmGiBYOKppJ5l8a6vtFqkfM3Cm3TP hpd1IajBddGSFGSDIrLN4O1RqNPwclP3fce9BGC+5IuQv76wAlovWMoQrK+C+jE/ KA6VpdAIBAm2YvbPZzYJgLaFJY7u1zFqFKactx1qs1XX7hrt4J/Hq9Xk4KsIPuFu cfjrEIppVHhtbrlwoAfqjA8JEqoiS6mO6mdbZfMpzLr2+cMg8Mer7kt9XRV0yE3q E+g3QmLMrVjJQSixrb5525WsQCLavkdf+Ynvg1aIDoXA8usTcP+jb3wLb9OSKYc3 6qVD7hgYoqREEXDt6pOc =WPxU -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Error while upgrading to Tomcat 7.0.52
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Utkarsh, On 3/3/14, 6:11 AM, Utkarsh Dave wrote: Hi Prashant - I assume there will not be any consequence of replacing validateXML with validateTld? Sure there will be. Read the documentation to determine the difference between those two configuration directives. On Mon, Mar 3, 2014 at 4:19 PM, Prashant Kadam prashantkada...@gmail.comwrote: On Mon, Mar 3, 2014 at 3:58 PM, Utkarsh Dave utkarshkd...@gmail.com wrote: To be more specific, i upgraded Tomcat in my application from Tomcat 7.0.41 to 7.0.52. Quick response is appreciable as the build process is on hold critical services are shut down. -Thanks On Mon, Mar 3, 2014 at 3:39 PM, Utkarsh Dave utkarshkd...@gmail.com wrote: Hi, I upgraded my application to 7.0.52 from 7.0.41. After upgrading while building and compiling whole application I am recieving error jasper2 doesn't support the validateXml attribute While looking in 1 of the blogs i found that the solution for this will be available only on 7.0.53 which is not yet available. Can you please let me know how i can proceed with this. If in case you need further details please let me know or feel free to reach to me in India IST. Hi Utkarsh Please use validateTld instead of validateXML. It would work . -Utkarsh Dave +919739903066 Technial Lead Infosys Limited at Cisco. e-city, Bangalore. India -- ~ Prashant Kadam -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFQKCAAoJEBzwKT+lPKRYIwUP/0PxP1ac7cV6gkjBEVojEIiY dKhKRocOCpkvactZ9/aUNyJkfAU0gpZ/REpxk77Un2D1cBhdwdHJFZQpohyUKStc 6uY3An8UCF/i0/ufqdikLAHASG2z9NOox5zphX4X5Vk+TNLq6RinpnHxlPb4uPSG GE4AYOOJW05Qqxv/iHlxsMGL9qb+sbDx+Yf9tbiPmIaMnkVfmTLeQpeBEYPYuTIJ rIfxQ7cIhVEfRUa8npHRGV1E34rWwHwyDOc4HRcP35nuV5dj9wDlL/36R4xFT5ra 7CvoFcRDpGNEt4G1Szn9H3Off2Y+SoKq/EZZVUfWzuq+d52c0jJEuC4H3xfNbGxs ludjO6tF0Ur3A0vLupLTDgrAM46h4u4iOtg2m2BdiPvgSKP5vWFWTI9OnBLLhTAI saZcvwzCfCteDvAozVbyBaYtK2se8CUyvIcxdQ9JU6Zr7zsb+ds7lgWzMlxVfRkO dIs6jUxsCkncXQyKEZpe4t7jcDAXizyO705EmrbvCYRJQN/je49HBqAS64r2qtyq tG2vd3NfWOAgGumyzHupwm56HoqADIFGzP1apjIW2nxYcHHi6eouJs2tghg0cNGl b2dYO6keghOEDWnBeGEujwOX+o5Yo4RR09oavfPE0ZD9jC213/IVuDQ3CRBKTkbW 1AjtwIADF534fV7O8lwo =kG8Q -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7.0.52 issue on our Sun Sparc with SunOS 5.10
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jay, On 2/28/14, 4:09 PM, Jay wrote: Hi Konstantin, Thanks. it did cut the name during the unpacking. I unpacked it using gunzip -c apache-tomcat-7.0.52.tar.gz |tar xvf - and there was no warning or error. The original tar.gz file contains: DrawboardContextListener.class DrawboardContextListener.java But after unpacked, their names are cut as follows: -rw-r--r-- 1 root root 890 Feb 13 02:29 DrawboardContextListener.c -rw-r--r-- 1 root root1346 Feb 13 02:31 DrawboardContextListener.j Are you using gnu tar or Sun tar? I think you'd better use Gnu tar, otherwise weird things can happen. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFQMcAAoJEBzwKT+lPKRYF7MP/0JpoHn6teRvdVIbGK+PEMyo x7HMxxDSWKq12KLRYPdwADuyYUjLjn0bLShh6ejB2AZD51TNiXiMsGS/isrqbe1O 2Fjzfl4SrH2BcWp5rOdu+PTtckka2m9fcWnLGZt1PBztqP0NwIkru2X598aU3rby +MWeSbo+BkgDjFxGQdb47ybYEZ6MdqkBHrjjfOfDNH+Wvl4LL+IZ+tk+xDku/nkS EbgpcKEPQjcxka2U3YaqBGJHODsVKK0d9tb6wphyBSBuhnqEvrTZOatmH7wDWFRe Qbws25U5BPKy3c6PSLKnjoV97Fkgitm8ecjNa7wL+IouqaBUFZfv9Y1EYYpV0ItN 5be898tj6DOBHVR+DH9hvaPnTfSOEr1TU8+P6vqPqJDNHyobT5uefKFFCBH8nfrg VLSwAwT65i6zWa3tI7iyeea7vD3DEUq6NKq24Qxmu85ny3tDUZWk3vvjLgVJDJra 71M6Jhaiq5U7WW0tjkSPgFEG4yZvVy2bWi/E9JeL1bZez3ZKHTc9OX2XHls+Y5y4 TGiGWMAOX1ULqL40f/9vYU6EJtv+2W/oxsXWS9Z/QGBLHDQWhpFgxBzs4mM9qL86 O+0/TLaqGjWbzAN5lNMahgOFdyc+ZZVy09i8PUAQTi1c2Y1RiUGuFylVrqC318KI nTXhJlo0xlSYzaWG4rB7 =i47K -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Could not publish server configuration for Tomcat v7.0 Server at localhost.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Frank, On 3/3/14, 2:38 PM, Frank Lugalla wrote: I right click and add my applications there Given that Tomcat does not have a GUI that allows you to right click and add my applicationsthere... could you be a little more specific? You do use Eclipse? NetBeans? Puppet? Tivoli? - -chris -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Monday, March 03, 2014 10:25 AM To: Tomcat Users List Subject: Re: Could not publish server configuration for Tomcat v7.0 Server at localhost. Frank, On 3/3/14, 10:58 AM, Frank Lugalla wrote: Hi Guys Just started using Tomcat v7..deployed my application and I am getting this error when I try to run; Could not publish server configuration for Tomcat v7.0 Server at localhost. Multiple Contexts have a path of /etm. Has anyone got this type of error before? This sounds like a deployment-specific problem. How are you deploying to Tomcat? -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFQHhAAoJEBzwKT+lPKRYLnUP/1NLq49JFfWfKdjuBM3aTiyA YArnOBimF/JvtkruDPUn1S54g0/W18sYIm0yxZKipT/cVFTghwByw4lTJM3D18Lf cSFRXT/tNP4KLn0s+4aWoor/hMSEh1yycAJ63cBZu110p8M+y9bU5M10qQG2HBTH rytbzMwFeP0Zj4xEOqbUGBdg+aTUjkb6TPNExj+SvTf0K2/k6eDhuCX3aCnCtbdQ Ul+9q1nLclseEfonkmyPcH30/HcyG/WJbeIJ3Hv3fSswyjKuE4moLJVr5aXkcBe+ nyCQCEVLLVuNKEZHWzZOYAxMxBa+0ji0Ep5X1R06JkHE+lBfz8rtrEFf0yvEbUp2 urhA274whehVQxCjXD8/W+R6co3g0ZkutPXwnLCaLKrgPI7OrHEijM87v9+n9nnb Uq0UuVRVwHYCQa1hYivzK/BCMh7LXuIHJfGEUZ++iPAFm0xRkGUKtv0oOTtb/EYB XLR4/rm2YrwRGQcuxaxxaWyU5lEXwAMGOa0LxjArFi/I0lMG+vRb8Rt7jXsIHbTh pPNC2sHolW6XFPYSpOg2dt8bLFhj4JKh3/DaI4PtByajqu6lQndBS479z/3l79pZ oTI6iy/0ZOjUoGaKc76B6RcUjT8CDqmitHfS33tlXIqllkxko3NHnUAqSc6myprd 1XBgxUrYgWJUFqebKMRT =+LJC -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: $CATALINA_HOME/conf/context.xml .. restrict a context?
Thanks, the issue is that my customer does not want to restrict the admin-console in it's war - the rational is anybody can then just redeploy a new admin-console.war and access it (overwrite the restrictions). They want to restrict access to this context from OUTSIDE the actual deployment. Make sense? On Mon, Mar 3, 2014 at 4:22 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ravi, On 3/3/14, 5:10 PM, Ravi Gupta wrote: Tomcat 6.X RHEL I tried adding the below in order to limit access to /admin-console It worked, but it limits access to EVERY context, which is odd. I am sure I am doing something wrong or I misunderstand how this works I want to put restrictions on the /admin-console context, but I do not want it inside the admin-console.war Again, this works, but other contexts are denied as well! Context path=/admin-console Valve className=org.apache.catalina.valves.RemoteAddrValve deny=* / /Context I'm guessing the file you edited was CATALINA_BASE/conf/context.xml? That's not the right file to edit. Undo all the changes you made to conf/context.xml. Instead, you want to edit the META-INF/context.xml file in your own webapp (or CATALINA_BASE/conf/[engine]/[host]/admin-console.xml if you have manually-deployed your application using an XML descriptor). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFQCoAAoJEBzwKT+lPKRYGXQQAKgWOzPpKvC9YvuSJWdDY5Ud 325eSaK73rns77SWz2nUFt3je5GTEFmQAuCyBHueeaGgaFsY9GrkE9/YtsuWxB52 gO22zYywmTtfSY4MNt5z4dolbWfkktcFkLA96FQxa4ZI7ZdvmyL4XRRPJSSKRck3 qushWLC5IhbTknnbbOFm3OAv/xY60dzorB8ashIDjMO1Rm+6xOWf2x3PeTAeuy8K h5rKVi1u2KkMnbMtvJABX2WGdYZA+r/LNozotXHDGApvEVFu4+YtRWpZx2kgeVVG 0pbgLlfmT3cltDGkfOLq7xk11/VJNVR/A276naolfA+lWlqg0ccTVy7T/HrYaVZ8 dHXh09GFAgxneC+JCdMzDGFaI1LEhMaDv9OhyEYCOjoz60c1lYg2idfFXffSTiFj QRgfesyer8jYWD0pyEQ939EOXKLnR2ClbwqkHvXZNKDf8NtitBeF45hUmxixuDhb GBu+tuBVEHWXJpmCkmh/Xd9iwGPU3w2geGnZXPUpDaERdKlKL/zbzLBpxvP9TpOs 0IMc3ZkZ39jnrMVfDbbloNRKMdbxSSlb/OMyDocZheSLw6QlECALfLZumQZCk759 z5BDS8zvINbpdUrUxLG7ZYTW+6ZXpR7N9nVF+ab2BnTC58J5aUb623FtSOuk1J2/ hMPVhRwdGyHLNccn82t4 =YZJb -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: $CATALINA_HOME/conf/context.xml .. restrict a context?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ravi, (Moving the discussion back onto the list: please reply to the list and not to individuals. That's what community is about.) On 3/3/14, 5:29 PM, Ravi Gupta wrote: Thanks, the issue is that my customer does not want to restrict the admin-console in it's war - the rational is anybody can then just redeploy a new admin-console.war and access it (overwrite the restrictions). They want to restrict access to this context from OUTSIDE the actual deployment. Make sense? It makes perfect sense. To deploy your web application in a safe way, you need to do the following: 0. Start with a stopped Tomcat. 1. Put the WAR wherever you want it to live. CATALINA_BASE/webapps is fine. 2. Extract META-INF/context.xml from your WAR file and place it in CATALINA_BASE/conf/[engine]/[host]/[appname].xml 3. Modify [appname].xml to add whatever restrictions you want. 4. Start Tomcat. If you overwrite the WAR file, the restrictions you have set should be maintained. Note that if you /undeploy/ the webapp and then redeploy it, any customizations will be lost and will have to be re-applied. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFQPbAAoJEBzwKT+lPKRYRmoQALE8fXXv+UVHkMCwzBHHfyvI FVfO8pxCEk8oxvrMunLjC/E2+O8KVCCSDYEjWYYuQs0L1cKjEWyuF6w0P8QDo6fB lE1pxuShreC1SMMZBEGf9GX0QORPgAB1C4tFnKEYP7/O/0l0KORGh81/AolhroG+ 8UvlNbFeb0LUR/ABHjdc2PN1UVL3FjruFMhkJSu0ZGqK8TpO7D74VWG2B5JD6zy6 ecFKQVSKf7wCLYJ5vXLpyLFJ/H5DKb6c5BBa7L0Edw+bEM8/YM9f7eoXl77TyBup Lhx19LOzrfFqcDNPXpqiSKy8VCEJH0TNd1iegJwWH4uTK/BYOu38pALspQ6piGjJ re8/goyGahK4Ii7A7B6463I/WqzuSwYxzoNYOMFd0db3gp5gzCq8u6MUgx1jTupA iG4f9SvGC4pvytTKujS/c36uHVipn3YbgTZzbsyhUug7VvTn5uSZUN1e68v+y9LA JV0sLGlzay6STujPamVInO6ICOEiqnY5TuoRoedmlYSLC0dkT5Nvpw9G4trL0WMc WZLVlKKgd3eQU4hUBNqeVfnlmwRuE2LFwHdAC1TpyWVsHkNaTtcCMq/YMkl+xAD0 4uka25gHs3g+j7KmGvvo4gjnPY1ODfTJbYrAdlhSZoMkuesyAW8gaYqG4NR6FoWm /tcZDv4FLrEtv5zXrz9l =L2bz -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: $CATALINA_HOME/conf/context.xml .. restrict a context?
Any idea if the same would work for JBOSS 5.X (uses tomcat under the hood)? perhaps it is not the same, but I tried putting admin-console.xml under jboss-5.1.0.GA/server/default/deploy/jbossweb.sar it contains Context path=/admin-console Valve className=org.apache.catalina.valves.RemoteAddrValve deny=* / /Context But I was still able to access http://localhost:8080/admin-console after a bounce? Any suggestions would be apreciated On Mon, Mar 3, 2014 at 4:36 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ravi, (Moving the discussion back onto the list: please reply to the list and not to individuals. That's what community is about.) On 3/3/14, 5:29 PM, Ravi Gupta wrote: Thanks, the issue is that my customer does not want to restrict the admin-console in it's war - the rational is anybody can then just redeploy a new admin-console.war and access it (overwrite the restrictions). They want to restrict access to this context from OUTSIDE the actual deployment. Make sense? It makes perfect sense. To deploy your web application in a safe way, you need to do the following: 0. Start with a stopped Tomcat. 1. Put the WAR wherever you want it to live. CATALINA_BASE/webapps is fine. 2. Extract META-INF/context.xml from your WAR file and place it in CATALINA_BASE/conf/[engine]/[host]/[appname].xml 3. Modify [appname].xml to add whatever restrictions you want. 4. Start Tomcat. If you overwrite the WAR file, the restrictions you have set should be maintained. Note that if you /undeploy/ the webapp and then redeploy it, any customizations will be lost and will have to be re-applied. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFQPbAAoJEBzwKT+lPKRYRmoQALE8fXXv+UVHkMCwzBHHfyvI FVfO8pxCEk8oxvrMunLjC/E2+O8KVCCSDYEjWYYuQs0L1cKjEWyuF6w0P8QDo6fB lE1pxuShreC1SMMZBEGf9GX0QORPgAB1C4tFnKEYP7/O/0l0KORGh81/AolhroG+ 8UvlNbFeb0LUR/ABHjdc2PN1UVL3FjruFMhkJSu0ZGqK8TpO7D74VWG2B5JD6zy6 ecFKQVSKf7wCLYJ5vXLpyLFJ/H5DKb6c5BBa7L0Edw+bEM8/YM9f7eoXl77TyBup Lhx19LOzrfFqcDNPXpqiSKy8VCEJH0TNd1iegJwWH4uTK/BYOu38pALspQ6piGjJ re8/goyGahK4Ii7A7B6463I/WqzuSwYxzoNYOMFd0db3gp5gzCq8u6MUgx1jTupA iG4f9SvGC4pvytTKujS/c36uHVipn3YbgTZzbsyhUug7VvTn5uSZUN1e68v+y9LA JV0sLGlzay6STujPamVInO6ICOEiqnY5TuoRoedmlYSLC0dkT5Nvpw9G4trL0WMc WZLVlKKgd3eQU4hUBNqeVfnlmwRuE2LFwHdAC1TpyWVsHkNaTtcCMq/YMkl+xAD0 4uka25gHs3g+j7KmGvvo4gjnPY1ODfTJbYrAdlhSZoMkuesyAW8gaYqG4NR6FoWm /tcZDv4FLrEtv5zXrz9l =L2bz -END PGP SIGNATURE-
RE: Tomcat 7.0.52 issue on our Sun Sparc with SunOS 5.10
Hi Chris, This is a tar issue and we can work out. Actually We have a real issue on the Tomcat stopping itself - I just reported again with the new version 7.052. Tomcat 7.0.52 stops after hours on our Sun Sparc with SunOS 5.10. Thanks, Jay -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Monday, March 03, 2014 5:33 PM To: Tomcat Users List Subject: Re: Tomcat 7.0.52 issue on our Sun Sparc with SunOS 5.10 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jay, On 2/28/14, 4:09 PM, Jay wrote: Hi Konstantin, Thanks. it did cut the name during the unpacking. I unpacked it using gunzip -c apache-tomcat-7.0.52.tar.gz |tar xvf - and there was no warning or error. The original tar.gz file contains: DrawboardContextListener.class DrawboardContextListener.java But after unpacked, their names are cut as follows: -rw-r--r-- 1 root root 890 Feb 13 02:29 DrawboardContextListener.c -rw-r--r-- 1 root root1346 Feb 13 02:31 DrawboardContextListener.j Are you using gnu tar or Sun tar? I think you'd better use Gnu tar, otherwise weird things can happen. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFQMcAAoJEBzwKT+lPKRYF7MP/0JpoHn6teRvdVIbGK+PEMyo x7HMxxDSWKq12KLRYPdwADuyYUjLjn0bLShh6ejB2AZD51TNiXiMsGS/isrqbe1O 2Fjzfl4SrH2BcWp5rOdu+PTtckka2m9fcWnLGZt1PBztqP0NwIkru2X598aU3rby +MWeSbo+BkgDjFxGQdb47ybYEZ6MdqkBHrjjfOfDNH+Wvl4LL+IZ+tk+xDku/nkS EbgpcKEPQjcxka2U3YaqBGJHODsVKK0d9tb6wphyBSBuhnqEvrTZOatmH7wDWFRe Qbws25U5BPKy3c6PSLKnjoV97Fkgitm8ecjNa7wL+IouqaBUFZfv9Y1EYYpV0ItN 5be898tj6DOBHVR+DH9hvaPnTfSOEr1TU8+P6vqPqJDNHyobT5uefKFFCBH8nfrg VLSwAwT65i6zWa3tI7iyeea7vD3DEUq6NKq24Qxmu85ny3tDUZWk3vvjLgVJDJra 71M6Jhaiq5U7WW0tjkSPgFEG4yZvVy2bWi/E9JeL1bZez3ZKHTc9OX2XHls+Y5y4 TGiGWMAOX1ULqL40f/9vYU6EJtv+2W/oxsXWS9Z/QGBLHDQWhpFgxBzs4mM9qL86 O+0/TLaqGjWbzAN5lNMahgOFdyc+ZZVy09i8PUAQTi1c2Y1RiUGuFylVrqC318KI nTXhJlo0xlSYzaWG4rB7 =i47K -END PGP SIGNATURE- - 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: $CATALINA_HOME/conf/context.xml .. restrict a context?
According to this, it should match up https://community.jboss.org/wiki/Web-AppContextConfiguration On Mon, Mar 3, 2014 at 4:53 PM, Ravi Gupta rkgupt...@gmail.com wrote: Any idea if the same would work for JBOSS 5.X (uses tomcat under the hood)? perhaps it is not the same, but I tried putting admin-console.xml under jboss-5.1.0.GA/server/default/deploy/jbossweb.sar it contains Context path=/admin-console Valve className=org.apache.catalina.valves.RemoteAddrValve deny=* / /Context But I was still able to access http://localhost:8080/admin-console after a bounce? Any suggestions would be apreciated On Mon, Mar 3, 2014 at 4:36 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ravi, (Moving the discussion back onto the list: please reply to the list and not to individuals. That's what community is about.) On 3/3/14, 5:29 PM, Ravi Gupta wrote: Thanks, the issue is that my customer does not want to restrict the admin-console in it's war - the rational is anybody can then just redeploy a new admin-console.war and access it (overwrite the restrictions). They want to restrict access to this context from OUTSIDE the actual deployment. Make sense? It makes perfect sense. To deploy your web application in a safe way, you need to do the following: 0. Start with a stopped Tomcat. 1. Put the WAR wherever you want it to live. CATALINA_BASE/webapps is fine. 2. Extract META-INF/context.xml from your WAR file and place it in CATALINA_BASE/conf/[engine]/[host]/[appname].xml 3. Modify [appname].xml to add whatever restrictions you want. 4. Start Tomcat. If you overwrite the WAR file, the restrictions you have set should be maintained. Note that if you /undeploy/ the webapp and then redeploy it, any customizations will be lost and will have to be re-applied. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTFQPbAAoJEBzwKT+lPKRYRmoQALE8fXXv+UVHkMCwzBHHfyvI FVfO8pxCEk8oxvrMunLjC/E2+O8KVCCSDYEjWYYuQs0L1cKjEWyuF6w0P8QDo6fB lE1pxuShreC1SMMZBEGf9GX0QORPgAB1C4tFnKEYP7/O/0l0KORGh81/AolhroG+ 8UvlNbFeb0LUR/ABHjdc2PN1UVL3FjruFMhkJSu0ZGqK8TpO7D74VWG2B5JD6zy6 ecFKQVSKf7wCLYJ5vXLpyLFJ/H5DKb6c5BBa7L0Edw+bEM8/YM9f7eoXl77TyBup Lhx19LOzrfFqcDNPXpqiSKy8VCEJH0TNd1iegJwWH4uTK/BYOu38pALspQ6piGjJ re8/goyGahK4Ii7A7B6463I/WqzuSwYxzoNYOMFd0db3gp5gzCq8u6MUgx1jTupA iG4f9SvGC4pvytTKujS/c36uHVipn3YbgTZzbsyhUug7VvTn5uSZUN1e68v+y9LA JV0sLGlzay6STujPamVInO6ICOEiqnY5TuoRoedmlYSLC0dkT5Nvpw9G4trL0WMc WZLVlKKgd3eQU4hUBNqeVfnlmwRuE2LFwHdAC1TpyWVsHkNaTtcCMq/YMkl+xAD0 4uka25gHs3g+j7KmGvvo4gjnPY1ODfTJbYrAdlhSZoMkuesyAW8gaYqG4NR6FoWm /tcZDv4FLrEtv5zXrz9l =L2bz -END PGP SIGNATURE-
Re: secure reverse proxy to my tomcat server HELP NEEDED
Hi Chris - Sorry for the HELP NEEDED. What actually happens is that, just for https://my.webserver.com/, I get served the pages that are at the apache root, *not* what is being served by tomcat at port 8443. I do get the tomcat pages if I explicitly add the port, i.e. https://my.webserver.com:8443/ So, the reverse proxy seems to be broken for https only. The reverse proxy works fine for http, i.e. http://my.webserver.com/ gets the tomcat pages served at http://my.webserver.com:8080/ Jeff Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Jeff, On 3/3/14, 5:11 PM, Jeff Haferman wrote: Yes, for development httpd and tomcat are on the same physical machine. Eventually they will be on different machines. But, even if I try browser --- HTTPS -- httpd -- HTTP -- Tomcat by just changing the ProxyPass and ProxyPassReverse directives to use the unencrypted URLs as follows VirtualHost *:443 SSLEngine on SSLProxyEngine on SSLCertificateFile /path/to/server.crt SSLCertificateKeyFile /path/to/server.key ServerName my.webserver.com ProxyPass / http://my.webserver.com:8080/ ProxyPassReverse / http://my.webserver.com:8080/ /VirtualHost the reverse proxy still does not serve the tomcat pages as I would expect. Given the above setup, what /actually/ happens when you try to request a resource that should go to Tomcat? does not serve pages as I expect is not a good description. Oh, and everyone posting NEEDS HELP to it's not necessary to add HELP NEEDED or similar text to your subjects. - -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat JDBC Connection Pool Resource Name Issue
I'm using the Tomcat JDBC connection pool on apache-tomcat-7.0.30. My context xml resource name is as follows: Resource name=jdbc/mypool ... When running under Tomcat, calling ConnectionPool.getName() from my custom JdbcInterceptor returns Tomcat Connection Pool[1-992158371]. Under JSE (a stand-alone main), it returns the expected value jdbc/mypool. Why is my resource name ignored or otherwise not used when running under the container? Thanks. -- Scott Dudley | Senior Developer Telesoft | 1661 E. Camelback Road, Suite 300 | Phoenix, AZ 85016 P: 602.308.1115 | F: 602.308.1300 | W: www.telesoft.com http://www.telesoft.com/?utm_source=signatureutm_medium=emailutm_campaign=2012 TEM Edge Blog http://www.telesoft.com/blog?utm_source=signatureutm_medium=emailutm_campaign=2012 | LinkedIn http://www.linkedin.com/company/telesoft-corp. | Twitter http://www.twitter.com/_Telesoft
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
On Mon, Mar 3, 2014 at 11:22 AM, Christopher Schultz ch...@christopherschultz.net wrote: Dmitry, On 3/3/14, 6:06 AM, Dmitry Batiyevskiy wrote: Can you advice how we can find the problem in app/environment like this? What are possible ways to debug this? Honestly, I'd try switching to the NIO connector and resume your testing. If all is well, it may point to a bug in the APR connector and/or tcnative itself. If you are having similar problems with the pure-Java connectors, then the problem is likely something you are doing in your application that is causing an invalid state. You'll probably get better information from the Java stack trace than from an assertion-failure. Give that a try and let us know how things go. +1 Chris I have found much /continued/ success using NIO connector across tomcat and atmosphere versions.
Re: java: src/network.c:441: Java_org_apache_tomcat_jni_Socket_send: Assertion failed
Howard, My connector config is the following (i've already posted that): Connector port=8443 maxHttpHeaderSize=8192 maxThreads=15000 enableLookups=false disableUploadTimeout=true acceptCount=100 scheme=https secure=true SSLEnabled=true compression=off SSLCertificateFile=/opt/tomcat/mycompany.com.crt SSLCertificateKeyFile=/opt/tomcat/mycompany.com.key / Also -Dhttps.protocols=TLSv1 option is passed to java machine The reason for me to use apr connector is https performance, isn't NIO much slower in that? Regards, Dmitry Batiyevskiy Ardas Group Inc. www.ardas.dp.ua 2014-03-04 2:04 GMT+02:00 Howard W. Smith, Jr. smithh032...@gmail.com: On Mon, Mar 3, 2014 at 11:22 AM, Christopher Schultz ch...@christopherschultz.net wrote: Dmitry, On 3/3/14, 6:06 AM, Dmitry Batiyevskiy wrote: Can you advice how we can find the problem in app/environment like this? What are possible ways to debug this? Honestly, I'd try switching to the NIO connector and resume your testing. If all is well, it may point to a bug in the APR connector and/or tcnative itself. If you are having similar problems with the pure-Java connectors, then the problem is likely something you are doing in your application that is causing an invalid state. You'll probably get better information from the Java stack trace than from an assertion-failure. Give that a try and let us know how things go. +1 Chris I have found much /continued/ success using NIO connector across tomcat and atmosphere versions.
