Re: Mark async-supported=true for non-asynchronous servlets
Getting back to my original question... is there any harm if I make the front servlet async-supported all the time, even though not all my application servlets support asynchronous mode? Thank you! On Wed, Jul 15, 2015 at 4:55 PM, Rilak Kun kunri...@gmail.com wrote: Thanks Chris for the suggestion, but since our application runs in OSGi, we need a different mechanism for loading classes/plugins lazily (and our servlet classes need to be loaded using OSGi class loader). We are using Equinox servletbridge library, which defines a bridge servlet I mentioned earlier, for delegating requests to our application servlets, and doing the tedious job of setting the right class loader and loading application plugins at the right time. In the long run, we should look into a different way of registering our OSGi servlets which will allow us to control the async mode of each servlet independently, but this is not a trivial task, so I am trying to see if there are any possible workarounds meanwhile. Any additional feedback or pointers are welcome! Rilak On Wed, Jul 15, 2015 at 2:31 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rilak, On 7/14/15 11:06 PM, Rilak Kun wrote: Our application is running in OSGi. Servlets are contributed via Eclipse extension point, so they can be registered in different plugins without changing the web.xml. When a servlet is registered, you can map it to a URL at the same time programmatically. Modifying web.xml is not necessary. - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVptEoAAoJEBzwKT+lPKRYln4P/R/Z9dD8RqNo+HXVoNfoRwXe NU/XROl0gYsIvioGqfJvPrVQiS4gBWKD81/O2LGNeHBYGNqC5kUdYhtEKS52V1He 03H80TIkTB17b2Xv6zknoKjnsxUIBDYe3jn5DIfQvh20jVDr75jWTHKSYh4hGMqc LiQpxCotijltA0BDtHFgixH0FVaXQQumh9ylMN7LOMwLDul+8NPrbRrqAobWTs+t eS999tK4Uu++qQdXCUXysF9bESWtpkzXeAPuEPEgSQaFaxhVHZwSr74pgD2playt /ZKO0u397sMwSyI4uE96B5DlGu5cPNhHknTw7/VKuo4VfYcd4FmSzo9hCV4YRx0n qKUi/vnWOAXCvoy1/VCmyrIRttVYSuq29q/8sIRjapDNnszxRJsxy5i5jvHR7xgV /HdsPLKw7QbBxMd3jERpc2TWOaAwBq5/XqOXdc9zk6I936gQWZU+ayW49oYg9RL/ Ea+jZQsDdLypTCinry3p+5On9FPc9AUblUDhwSYyWrlGpHAyASNgjOiAJIxxEDej 2UcOWpfeO9ueJFQba9fyzBVfG+8p+qv8DhBMiBhSE9S8hYK47eVLtACea6aAv0Sb APbIg9K5z4LtIu/7M7xaDNHmOxkiqyzJLcBa5wIe461Dfstm20TXUhlHGmamABdk 0I5q6RuKTAc9FJa48EvX =Kap9 -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: Mark async-supported=true for non-asynchronous servlets
This is great news. Thank you Mark! On Thu, Jul 16, 2015 at 1:57 PM, Mark Thomas ma...@apache.org wrote: On 16 July 2015 21:49:33 CEST, Rilak Kun kunri...@gmail.com wrote: Getting back to my original question... is there any harm if I make the front servlet async-supported all the time, even though not all my application servlets support asynchronous mode? No. Assuming that your front servlet isn't doing anything that will break under async (from your description of it I think you'll be ok). Mark Thank you! On Wed, Jul 15, 2015 at 4:55 PM, Rilak Kun kunri...@gmail.com wrote: Thanks Chris for the suggestion, but since our application runs in OSGi, we need a different mechanism for loading classes/plugins lazily (and our servlet classes need to be loaded using OSGi class loader). We are using Equinox servletbridge library, which defines a bridge servlet I mentioned earlier, for delegating requests to our application servlets, and doing the tedious job of setting the right class loader and loading application plugins at the right time. In the long run, we should look into a different way of registering our OSGi servlets which will allow us to control the async mode of each servlet independently, but this is not a trivial task, so I am trying to see if there are any possible workarounds meanwhile. Any additional feedback or pointers are welcome! Rilak On Wed, Jul 15, 2015 at 2:31 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rilak, On 7/14/15 11:06 PM, Rilak Kun wrote: Our application is running in OSGi. Servlets are contributed via Eclipse extension point, so they can be registered in different plugins without changing the web.xml. When a servlet is registered, you can map it to a URL at the same time programmatically. Modifying web.xml is not necessary. - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVptEoAAoJEBzwKT+lPKRYln4P/R/Z9dD8RqNo+HXVoNfoRwXe NU/XROl0gYsIvioGqfJvPrVQiS4gBWKD81/O2LGNeHBYGNqC5kUdYhtEKS52V1He 03H80TIkTB17b2Xv6zknoKjnsxUIBDYe3jn5DIfQvh20jVDr75jWTHKSYh4hGMqc LiQpxCotijltA0BDtHFgixH0FVaXQQumh9ylMN7LOMwLDul+8NPrbRrqAobWTs+t eS999tK4Uu++qQdXCUXysF9bESWtpkzXeAPuEPEgSQaFaxhVHZwSr74pgD2playt /ZKO0u397sMwSyI4uE96B5DlGu5cPNhHknTw7/VKuo4VfYcd4FmSzo9hCV4YRx0n qKUi/vnWOAXCvoy1/VCmyrIRttVYSuq29q/8sIRjapDNnszxRJsxy5i5jvHR7xgV /HdsPLKw7QbBxMd3jERpc2TWOaAwBq5/XqOXdc9zk6I936gQWZU+ayW49oYg9RL/ Ea+jZQsDdLypTCinry3p+5On9FPc9AUblUDhwSYyWrlGpHAyASNgjOiAJIxxEDej 2UcOWpfeO9ueJFQba9fyzBVfG+8p+qv8DhBMiBhSE9S8hYK47eVLtACea6aAv0Sb APbIg9K5z4LtIu/7M7xaDNHmOxkiqyzJLcBa5wIe461Dfstm20TXUhlHGmamABdk 0I5q6RuKTAc9FJa48EvX =Kap9 -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 - 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: Mark async-supported=true for non-asynchronous servlets
Thanks Chris for the suggestion, but since our application runs in OSGi, we need a different mechanism for loading classes/plugins lazily (and our servlet classes need to be loaded using OSGi class loader). We are using Equinox servletbridge library, which defines a bridge servlet I mentioned earlier, for delegating requests to our application servlets, and doing the tedious job of setting the right class loader and loading application plugins at the right time. In the long run, we should look into a different way of registering our OSGi servlets which will allow us to control the async mode of each servlet independently, but this is not a trivial task, so I am trying to see if there are any possible workarounds meanwhile. Any additional feedback or pointers are welcome! Rilak On Wed, Jul 15, 2015 at 2:31 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rilak, On 7/14/15 11:06 PM, Rilak Kun wrote: Our application is running in OSGi. Servlets are contributed via Eclipse extension point, so they can be registered in different plugins without changing the web.xml. When a servlet is registered, you can map it to a URL at the same time programmatically. Modifying web.xml is not necessary. - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVptEoAAoJEBzwKT+lPKRYln4P/R/Z9dD8RqNo+HXVoNfoRwXe NU/XROl0gYsIvioGqfJvPrVQiS4gBWKD81/O2LGNeHBYGNqC5kUdYhtEKS52V1He 03H80TIkTB17b2Xv6zknoKjnsxUIBDYe3jn5DIfQvh20jVDr75jWTHKSYh4hGMqc LiQpxCotijltA0BDtHFgixH0FVaXQQumh9ylMN7LOMwLDul+8NPrbRrqAobWTs+t eS999tK4Uu++qQdXCUXysF9bESWtpkzXeAPuEPEgSQaFaxhVHZwSr74pgD2playt /ZKO0u397sMwSyI4uE96B5DlGu5cPNhHknTw7/VKuo4VfYcd4FmSzo9hCV4YRx0n qKUi/vnWOAXCvoy1/VCmyrIRttVYSuq29q/8sIRjapDNnszxRJsxy5i5jvHR7xgV /HdsPLKw7QbBxMd3jERpc2TWOaAwBq5/XqOXdc9zk6I936gQWZU+ayW49oYg9RL/ Ea+jZQsDdLypTCinry3p+5On9FPc9AUblUDhwSYyWrlGpHAyASNgjOiAJIxxEDej 2UcOWpfeO9ueJFQba9fyzBVfG+8p+qv8DhBMiBhSE9S8hYK47eVLtACea6aAv0Sb APbIg9K5z4LtIu/7M7xaDNHmOxkiqyzJLcBa5wIe461Dfstm20TXUhlHGmamABdk 0I5q6RuKTAc9FJa48EvX =Kap9 -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: Mark async-supported=true for non-asynchronous servlets
Hello Chris, Our application is running in OSGi. Servlets are contributed via Eclipse extension point, so they can be registered in different plugins without changing the web.xml. Thank you! Rilak On Tue, Jul 14, 2015 at 8:24 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Rilak, On 7/14/15 9:20 PM, Rilak Kun wrote: I have only one servlet definition in my web.xml. This servlet acts as a bridge servlet for delegating requests to the actual 50 servlets in my application. I would like to make one of the 50 servlets async-supported. I'm curious: why not use those servlets directly instead of through a front-servlet? - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVpdJ9AAoJEBzwKT+lPKRYK4AQAKsSXvmytsE/LHwA8v2oEJA5 G7kY2ojAZEGE89J280oKqoe8u4LipkYo52t2nO24wekhtK6taZ1Ez8tmrb96F7/M /H6knth7FOLWaqbPyCi8Bu7Wxk54UJG12QmfGYmI/cXGMgGkJTGufD3FZK+rdVo2 zKZQ3/AsbWyH8F6lKsJH5jfzY40d0HgPYwAQhoPN91aeeqJZYGhaY6+gcnmm8Cku 1lyu1xau+TuftC+NtA9Tl6oIE+4HkBbsknr4+AvRQtYUmvQnMeEvSb2InxwPbayt KBE36F4R+79X3L12fBJ1tI5zYFfqpUvVPWcawHnitNlubfv2A1oIsNPBDbwBBKql B/kaWJiXvNK7o/yhB//HS49wlvyH+/F0+IF3aSQD519tRlfU27NeYrl2JaSw1KlY DsjDxWoQZ2+o8P0ca2wmryWw+cDRyALY1cegKLDJGGx6RQmxIiI4VYPAFP5kB7tn 16PkD4ILcLQH4DOuwpSXeMXD00bkQtTZn2p7tGMTlQTzRWxuYfb5OZwOU2TLr87R 38eChXCJdFIY5ZE7uh1m9ma07L6OK2CpWuZDXv6cy6bALEZCUO9/GiZqz8f4acif +XqNqcwfXNwpMLmh6dgObJswGw60C1VEfGznS+xB8Dzb5oq2f9iHNC1a8iG+DH2o TlzSsGarFNk3oSA4T/56 =HwO2 -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
Mark async-supported=true for non-asynchronous servlets
Hello, I have only one servlet definition in my web.xml. This servlet acts as a bridge servlet for delegating requests to the actual 50 servlets in my application. I would like to make one of the 50 servlets async-supported. I can think of two ways to do it: 1. Create another bridge servlet for handling asynchronous servlets, and specify async-supported=true only for this servlet. 2. Just add async-supported=true to the existing servlet definition, even though only 1 out of my 50 servlets supports asynchronous mode. Are there any bad implications for going with option #2? I did a quick test with #2 and my application seems to run fine, but I am not sure if it will create performance or scalability issues. I try to look for similar question in the forum and from the web, but I am not able to find an assertive answer to it. I am running Tomcat 7.0. Thank you! - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org