I wish I could forward all requests completely to another server.
I was tasked with writing a web application that needs to forward a http request to each server after checking certain headers. Of course I can use a library like apache http client to reconstruct and send the data. But if you think about it, this is a very unreasonable and bad way. Suppose you need to forward a request that uploads a 100 mega file. To forward this, once the servlet receives it as an object, the server memory is already reduced. Couldn't Servlet Engine check and pass only a few headers and pass it in stream format? Even if it is not the above example, I think the servlet may have the ability to have it in a raw state or to return it, like the request strings sent to telnet. I think it would be great if this could be supported by the servlet engine itself. Thank you for reading!
Re: [ANN] New committer: Woonsan Ko
Congratulations! 2018년 12월 19일 (수) 오후 7:23, Raul losoha 님이 작성: > You are welcome !!! > > Shalom , > > Raul Losoha > > From: Felix Schumacher > Sent: Wednesday, December 19, 2018 10:10 AM > To: Tomcat Developers List; Tomcat Users List > Subject: Re: [ANN] New committer: Woonsan Ko > > Am Mittwoch, den 19.12.2018, 09:56 + schrieb Mark Thomas: > > On behalf of the Tomcat committers I am pleased to announce that > > Woonsan Ko (woonsan) has been voted in as a new Tomcat committer. > > > > Please join me in welcoming him. > > Congrats, > Felix > > > > > Kind regards, > > > > Mark > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: lingering mysql connections
Hi, chris. You can use apache commons-dbcp2-2.5.0. This problem is fixed in this version. And ServletContextListener is not necessary! This is make you happy. :-) Have a nice day!!! 2018년 12월 14일 (금) 오전 5:51, Chris Cheshire 님이 작성: > Tomcat 9.0.12, Debian, MySQL Server 5.7.23, Connector/J 5.1.46 > > I am trying to fix a lingering database connection problem. When I > reload a context via the tomcat manager, connections to the > datasources are not being released in mysql. They are still on the 30 > second activity cycle from the eviction thread. I can see this via > 'show processlist' in the mysql client - the 'time' column resets at > 30, and each connection has unique process ids that I can track per > reload. > > I have tomcat home and base split (multiple instances of tomcat across > different users), with the connector/j jar in tomcat_base/lib. > > In my webapp's META-INF/context.xml I have 3 different datasources, > config, data, sched. All have configuration like : > >auth="Container" > type="javax.sql.DataSource" > driverClassName="com.mysql.jdbc.Driver" > > url="jdbc:mysql://localhost:3306/$DBNAME$?useUnicode=true&characterEncoding=utf8&useSSL=false" > factory="org.apache.tomcat.jdbc.pool.DataSourceFactory" > username="$USER$" > password="$PASSWORD$" > maxActive="2" > maxIdle="1" > minIdle="1" > initialSize="1" > maxWait="3" > removeAbandoned="true" > removeAbandonedTimeout="60" > logAbandoned="true" > validationQuery="/* ping */" > testOnBorrow="true" > testWhileIdle="true" > timeBetweenEvictionRunsMillis="3" > defaultAutoCommit="false" > defaultIsolation="READ_COMMITTED" /> > > Connections are obtained via > > Connection dbConn = ((DataSource)new > InitialContext().lookup(resourceName)).getConnection() > > Connections are all closed via > > dbConn.close() > > (Simplified greatly, there's convenience methods with exception > handling in there) > > > > In contextDestroyed() of a ServletContextListener I am calling > > AbandonedConnectionCleanupThread.checkedShutdown(); > > I have an initialization servlet that must be manually called before > the webapp is fully online - it is used to load encrypted > configuration from the conf datasource. It does not touch the data > datasource, only conf and sched by virtue of starting the quartz > scheduler which is configured to use this datasource. > > My observation are : > * It doesn't matter what order I declare the datasources, they are > always getting opened in the order sched, conf, data (judging by > increased thread/process ids in mysql). > * When I start tomcat, I get 3 open connections in mysql, 1 to each of > the databases referenced by the datasources. If I immediately reload > via the manager, all 3 connections are destroyed and 3 new ones are > opened. > * Once I call the initialization servlet, and subsequently reload the > web app via the manager, previous connections to conf and sched are > still open in mysql, as well as new ones > * If I access any part of the web app that uses the data datasource, > those connections now also linger. > * Once I stop tomcat (and the JVM) all lingering connections are > closed in mysql. > * If I put the connector/j jar in my WEB-INF/lib instead of > tomcat_base/lib, I get the following warning on reload/shutdown > > 13-Dec-2018 20:19:53.968 WARNING [ajp-nio-8019-exec-3] > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc > The web application [ct] registered the JDBC driver > [com.mysql.jdbc.Driver] but failed to unregister it when the web > application was stopped. To prevent a memory leak, the JDBC Driver has > been forcibly unregistered. > > * There are no warnings or errors in catalina.out about abandoned > connections during runtime, reload or shutdown of the tomcat instance. > I have every connection being closed after use. (I have seen the > warnings when I have made a code mistake however, so the thread is > doing its job). > * If I remove the abandoned connection and eviction thread > configuration entirely, the connection activity timer resets on a 5 > second cycle in mysql. If I explicitly change > timeBetweenEvictionRunsMillis to -1, the activity timer in mysql never > resets (which implies that the default is not -1 as the documentation > suggests) > > So it seems that once a datasource is accessed, connections to it > perpetually linger in mysql until the JVM is shutdown. > > I have had this issue for a long time, through tomcat 7, 8.5 and 9, > and multiple versions of mysql server and the connector., and also > using the commons pool. On my sandboxes I tend to reload a lot as I > deploy exploded, rather than deploy an entire WAR each time. > > Googling led to multiple old bug reports filed w/ MySQL about the > cleanup thr
Re: Connection pool and parallel deployment problem
I'm glad to solve problem. But I am concerned that the C3p0 is not updated since 2015. Let's hope for a better library. Bye~ 2018년 11월 27일 (화) 오후 6:20, Gilles SCHLIENGER 님이 작성: > Thanks, > > I don't have this problem using C3p0 > > Parallel deployment is working fine so far, especially now that we will > use connection pools configured inside the webapp (no more context xml file) > > Regards > Gilles > > -Message d'origine- > De : HeeGu Lee [mailto:elfhazardw...@gmail.com] > Envoyé : mardi 27 novembre 2018 10:17 > À : Tomcat Users List > Objet : Re: Connection pool and parallel deployment problem > > 1. JMX registration is call by BasicDataSource of apache commons-dbcp2 > library. > It is hidden inside and can not be controlled. > > The name of the spring bean is referenced as part of the JMX name. > You can change the bean name for each distribution. > But that is not smart. > > 2. Usually, JMX is use for system monitoring. > Using tool like grafana, you will see jvm heap momory, running thread > count, network traffic of Tomcat. > > > 2018년 11월 27일 (화) 오후 6:03, Gilles SCHLIENGER 님이 > 작성: > > > Thanks a lot Heegu, > > > > I looked at your project on github. > > 1. Which part of the code is exporting JMX beans ? Is it the @ManagedBean > > annotation ? > > > > 2. What do you use JMX for ? > > > > Thanks again > > Regards > > Gilles > > > > > > -Message d'origine- > > De : HeeGu Lee [mailto:elfhazardw...@gmail.com] > > Envoyé : mardi 27 novembre 2018 08:36 > > À : Tomcat Users List > > Objet : Re: Connection pool and parallel deployment problem > > > > Dear Gilles, > > > > I apologize for the delay in reply. > > > > I make simple webapp and upload to github. In project, my test result is > > included. > > > > https://github.com/elfhazardwork/dbcp2-test > > > > Tomcat's parallel deploy mechanism is deploy new version before undeploy > > old. > > So, If your webapp is use JMX, bean name will duplicate and crush. > > > > The connection pool is used where the developer does not explicitly > declare > > JXM. > > So this is a Tomcat bug. > > Otherwise, you must set JMX bean name dynamically. > > > > I hope this helps. > > > > > > 2018년 11월 27일 (화) 오전 2:03, Chris Cheshire 님이 작성: > > > > > On Mon, Nov 26, 2018 at 9:58 AM Gilles SCHLIENGER > > > wrote: > > > > > > > > Hi, > > > > I understand your needs, but what is your problem, since you don't > use > > > parallel deployment ? > > > > Your connections are not closed but they will not be recreated when > you > > > deploy your webapp again, so there should be no problem ? > > > > > > > > Gilles > > > > > > > > > > I added my 2c because I am seeing what you describe here > > > > > > > > - I undeploy the first version of the webapp > > > > > - I check on my postgresql and mysql database and all connections > are > > > still opened (even if I wait for a long time) > > > > > > > > > Yes I know you are using parallel deployment and I am not, but that > > > doesn't necessarily mean that the problem you see is limited to only > > > parallel deployment. Maybe the problem can be simplified to " > > > Tomcat considers the connections closed, the database doesn't." > > > > > > I could well be wrong, I'll leave it up to the gurus to decide :) > > > > > > > > > > -Message d'origine- > > > > De : Chris Cheshire [mailto:yahoono...@gmail.com] > > > > Envoyé : lundi 26 novembre 2018 15:27 > > > > À : Tomcat Users List > > > > Objet : Re: Connection pool and parallel deployment problem > > > > > > > > I'm interested in what solution there is for this because I have the > > > > exact same problem but without parallel deployment. > > > > > > > > [snip] > > > > > > > > On Mon, Nov 26, 2018 at 3:54 AM Gilles SCHLIENGER > > > > wrote: > > > > > > > > > > Hi Christopher, > > > > > > > > > > Thanks for your email. > > > > > > > > > > About connection pools not being closed, maybe the connection pool > is > > > closed but the connections to the database are not. > > > > > > > > > > Here
Re: Connection pool and parallel deployment problem
1. JMX registration is call by BasicDataSource of apache commons-dbcp2 library. It is hidden inside and can not be controlled. The name of the spring bean is referenced as part of the JMX name. You can change the bean name for each distribution. But that is not smart. 2. Usually, JMX is use for system monitoring. Using tool like grafana, you will see jvm heap momory, running thread count, network traffic of Tomcat. 2018년 11월 27일 (화) 오후 6:03, Gilles SCHLIENGER 님이 작성: > Thanks a lot Heegu, > > I looked at your project on github. > 1. Which part of the code is exporting JMX beans ? Is it the @ManagedBean > annotation ? > > 2. What do you use JMX for ? > > Thanks again > Regards > Gilles > > > -----Message d'origine- > De : HeeGu Lee [mailto:elfhazardw...@gmail.com] > Envoyé : mardi 27 novembre 2018 08:36 > À : Tomcat Users List > Objet : Re: Connection pool and parallel deployment problem > > Dear Gilles, > > I apologize for the delay in reply. > > I make simple webapp and upload to github. In project, my test result is > included. > > https://github.com/elfhazardwork/dbcp2-test > > Tomcat's parallel deploy mechanism is deploy new version before undeploy > old. > So, If your webapp is use JMX, bean name will duplicate and crush. > > The connection pool is used where the developer does not explicitly declare > JXM. > So this is a Tomcat bug. > Otherwise, you must set JMX bean name dynamically. > > I hope this helps. > > > 2018년 11월 27일 (화) 오전 2:03, Chris Cheshire 님이 작성: > > > On Mon, Nov 26, 2018 at 9:58 AM Gilles SCHLIENGER > > wrote: > > > > > > Hi, > > > I understand your needs, but what is your problem, since you don't use > > parallel deployment ? > > > Your connections are not closed but they will not be recreated when you > > deploy your webapp again, so there should be no problem ? > > > > > > Gilles > > > > > > > I added my 2c because I am seeing what you describe here > > > > > > - I undeploy the first version of the webapp > > > > - I check on my postgresql and mysql database and all connections are > > still opened (even if I wait for a long time) > > > > > > Yes I know you are using parallel deployment and I am not, but that > > doesn't necessarily mean that the problem you see is limited to only > > parallel deployment. Maybe the problem can be simplified to " > > Tomcat considers the connections closed, the database doesn't." > > > > I could well be wrong, I'll leave it up to the gurus to decide :) > > > > > > > -Message d'origine- > > > De : Chris Cheshire [mailto:yahoono...@gmail.com] > > > Envoyé : lundi 26 novembre 2018 15:27 > > > À : Tomcat Users List > > > Objet : Re: Connection pool and parallel deployment problem > > > > > > I'm interested in what solution there is for this because I have the > > > exact same problem but without parallel deployment. > > > > > > [snip] > > > > > > On Mon, Nov 26, 2018 at 3:54 AM Gilles SCHLIENGER > > > wrote: > > > > > > > > Hi Christopher, > > > > > > > > Thanks for your email. > > > > > > > > About connection pools not being closed, maybe the connection pool is > > closed but the connections to the database are not. > > > > > > > > Here are the tests I did: > > > > > > > > + TEST 1: > > > > - I deploy my war > > > > - I login to my webapp > > > > - I check on my postgresql and mysql database that connections have > > been opened (select...) > > > > - I undeploy my webapp through the manager webapp > > > > - I check that the connections are still opened > > > > - Tomcat is still running > > > > - I redeploy the exact samed webapp and login to my application > > > > - No other connection is being opened > > > > > > > > + TEST 2: > > > > - I deploy my war > > > > - I login to my webapp > > > > - I check on my postgresql and mysql database that connections have > > been opened (select...) > > > > - I deploy a new version of my application and login with another > > browser > > > > - I check on my postgresql and mysql database that new connexions > have > > been opened (they doubled) > > > > - I undeploy the first version of the webapp > > > > - I check on my postgresql and mysql database and all connecti
Re: Connection pool and parallel deployment problem
Dear Gilles, I apologize for the delay in reply. I make simple webapp and upload to github. In project, my test result is included. https://github.com/elfhazardwork/dbcp2-test Tomcat's parallel deploy mechanism is deploy new version before undeploy old. So, If your webapp is use JMX, bean name will duplicate and crush. The connection pool is used where the developer does not explicitly declare JXM. So this is a Tomcat bug. Otherwise, you must set JMX bean name dynamically. I hope this helps. 2018년 11월 27일 (화) 오전 2:03, Chris Cheshire 님이 작성: > On Mon, Nov 26, 2018 at 9:58 AM Gilles SCHLIENGER > wrote: > > > > Hi, > > I understand your needs, but what is your problem, since you don't use > parallel deployment ? > > Your connections are not closed but they will not be recreated when you > deploy your webapp again, so there should be no problem ? > > > > Gilles > > > > I added my 2c because I am seeing what you describe here > > > > - I undeploy the first version of the webapp > > > - I check on my postgresql and mysql database and all connections are > still opened (even if I wait for a long time) > > > Yes I know you are using parallel deployment and I am not, but that > doesn't necessarily mean that the problem you see is limited to only > parallel deployment. Maybe the problem can be simplified to " > Tomcat considers the connections closed, the database doesn't." > > I could well be wrong, I'll leave it up to the gurus to decide :) > > > > -Message d'origine- > > De : Chris Cheshire [mailto:yahoono...@gmail.com] > > Envoyé : lundi 26 novembre 2018 15:27 > > À : Tomcat Users List > > Objet : Re: Connection pool and parallel deployment problem > > > > I'm interested in what solution there is for this because I have the > > exact same problem but without parallel deployment. > > > > [snip] > > > > On Mon, Nov 26, 2018 at 3:54 AM Gilles SCHLIENGER > > wrote: > > > > > > Hi Christopher, > > > > > > Thanks for your email. > > > > > > About connection pools not being closed, maybe the connection pool is > closed but the connections to the database are not. > > > > > > Here are the tests I did: > > > > > > + TEST 1: > > > - I deploy my war > > > - I login to my webapp > > > - I check on my postgresql and mysql database that connections have > been opened (select...) > > > - I undeploy my webapp through the manager webapp > > > - I check that the connections are still opened > > > - Tomcat is still running > > > - I redeploy the exact samed webapp and login to my application > > > - No other connection is being opened > > > > > > + TEST 2: > > > - I deploy my war > > > - I login to my webapp > > > - I check on my postgresql and mysql database that connections have > been opened (select...) > > > - I deploy a new version of my application and login with another > browser > > > - I check on my postgresql and mysql database that new connexions have > been opened (they doubled) > > > - I undeploy the first version of the webapp > > > - I check on my postgresql and mysql database and all connections are > still opened (even if I wait for a long time) > > > > > > For tests 1 and 2, I used C3p0, DBCP2 and even HikariCP > > > > > > > > > My results are the same. Using mysql, connection pools defined in > > server.xml (for user realm for access control to host manager app) and > > in my context.xml for my application. When I use the host-manager to > > reload an app, the connections are closed (no abandoned connection > > warnings) but not released. It is no until I stop tomcat completely > > and restart it that the connections are released in mysql. This has > > been the case for tomcat 7, 8.5 and 9 versions, with constant updates > > of mysql 5.7 and its driver, using both the apache connection pool and > > the tomcat connection pool. The driver lives in the tomcat/lib > > directory (since it is needed for the user realm datasource). > > > > > > > -Message d'origine- > > > De : Christopher Schultz [mailto:ch...@christopherschultz.net] > > > Envoyé : samedi 24 novembre 2018 17:19 > > > À : users@tomcat.apache.org > > > Objet : Re: Connection pool and parallel deployment problem > > > > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA256 > > > > > > Gilles, > > > > > > On 11/23/18 05:07, Gilles SCHLIENGER wrote: > > > > [snip] > > > > > > > > > The warning/error messages are not actually linked to the > > > > connexions not closed. To ovoid these messages, you can: - move the > > > > jars (connexion pool, drivers...) into TOMCAT/lib - Have a > > > > ServletContextListener that calls > > > > AbandonedConnectionCleanupThread.checkedShutdown(); > > > > > > The Connector/J devs haven't been able to understand how ClassLoaders > > > work, and have never really fixed that long-standing bug in a > > > satisfying way as far as I know. But you should always use a > > > ServletContextListener to attempt to shut-down the > > > AbadonedConnectionCleanuopThread. > > > > > > BTW that thread does not work
Re: Connection pool and parallel deployment problem
I think it is good for your mental health not to use this feature. You just have to think of it as an experimental function like google chrome's about://flags. JMX has subscribe model. However, Tomcat is no ability to receive notifications. And most JDBC implementations are not interested in such features. Both Tomcat and DB vendors are not going to fix it. It's not a tragedy, it's just a comedy. 2018년 11월 21일 (수) 오후 8:00, Gilles SCHLIENGER 님이 작성: > Hi all, > > We are using Tomcat 9 and parallel deployment. > > I use a connection pool defined in the xml context (myApp##1.xml, > myApp##2.xml in my exemple) > > I have the following problem : > - I have myApp##1.war deployed using a connection pool (configured in > myApp##1.xml) > - I deploy myApp##2.war (using a connection pool defined in myApp##2.xml) > - when the last session in myApp##1 expires, myApp##1 is automatically > undeployed (I have undeployOldVersions="true" in server.xml for the Host) > but the connections opened by myApp##1 are not closed. > > I used the Tomcat configuration from the example in : > > https://tomcat.apache.org/tomcat-9.0-doc/jndi-datasource-examples-howto.html#Database_Connection_Pool_(DBCP_2)_Configurations > > type="javax.sql.DataSource" >maxTotal="100" maxIdle="30" maxWaitMillis="1" > destroy-method="close" >username="postgres" password="password" > driverClassName="org.postgresql.Driver" > > url="jdbc:postgresql://localhost:5432/postgres?stringtype=unspecified"/> > > During undeploy, I get the following messages : > > 21-Nov-2018 11:42:54.795 AVERTISSEMENT > [ContainerBackgroundProcessor[StandardEngine[Catalina]]] > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The > web application [myApp##1] registered the JDBC driver > [org.postgresql.Driver] but failed to unregister it when the web > application was stopped. To prevent a memory leak, the JDBC Driver has been > forcibly unregistered. > > ... > > 21-Nov-2018 11:42:54.800 AVERTISSEMENT > [ContainerBackgroundProcessor[StandardEngine[Catalina]]] > org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The > web application [myApp##1] appears to have started a thread named > [Abandoned connection cleanup thread] but has failed to stop it. This is > very likely to create a memory leak. Stack trace of thread: > java.base@10.0.1/java.lang.Object.wait(Native Method) > java.base@10.0.1 > /java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) > > com.mysql.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:64) > java.base@10.0.1 > /java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135) > java.base@10.0.1 > /java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) > java.base@10.0.1/java.lang.Thread.run(Thread.java:844) > > I have tested adding < destroy-method=close > but it did not change > anything > > Is this a bug ? > > Thanks for any help ! > > Regards > Gilles > >
Re: Is it possible to get the benefits of working with apache-tomcat in tomcat at once?
Thank you, chris. You are very kind. 2018년 10월 23일 (화) 오후 11:43, Christopher Schultz < ch...@christopherschultz.net>님이 작성: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > HeeGu, > > On 10/23/18 05:34, HeeGu Lee wrote: > > Hello, Dear Friends! > > > > Usually, to solve the tomcat's SocketException problem and to show > > error page, I will connect Apache using JK Connector. But, two web > > servers is make management difficult. > > > > So, I wish I could be provided with some feature on Tomcat. > > > > > protocol="Proxy (or Delegate) Connector" ... > > > > web browser -> Proxy Connector -> HTTP/1.1 -> Servlet -> ... > > > > This Connector's primary goal is to show error or redirect page > > even all HTTP/1.1 Connector is busy. > > > > Is this a possible idea? > > If I understand, you'd like to be able to reply to the client even > when all the Tomcat back-ends are busy. This is best done using a > reverse-proxy such as Apache httpd, Apache Traffic Server, nginx, > Squid, Varnish, or any number of similar products. > > Yes, "two servers makes management difficult", but that's the price > you have to pay for robustness and high-availability ... which is > maybe not so "high" in this case :) > > Hope that helps, > - -chris > -BEGIN PGP SIGNATURE- > Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ > > iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlvPM4YACgkQHPApP6U8 > pFjfNg//TuYI1SOd35TU6P/D+xySi5KphT5OC+lkC3t5gQ0IxiByq+mGy1J47z4+ > rNShIcciRys5bzWyYTn3MVdOMoWMu1NRfWj2ZLi7vWtniiCxp+mIXaoc3dFc3T4F > SG9osBsrINkM9GqHqfaPRrjlENz3wrJqrRc1fUpgq7uswAUwKVzRnbm9cbSlXN+G > 669W8PSPfSpaDZ7bZhsbjW7RN/Dlo4PHwx1mMgNEcOW7/RAJ4TcSoj4S08p923g1 > jHNL157DxXabdc+kaTX39SWYgkg3EO5ZaZe/zyunzhlYVjsdDKZMX2bcxA39dl9I > rOSKXwM6/i290DqBZQtbY76hukJ72bRsUU9XQAT6LJxLnFELM/gk4UYM0XNp1qBT > DA8ptpPdvK1P43uK9MKPguh/vmwx+fBhTciYCJAO00DB99jzx7yBeYXLwoGFhtP1 > J+8Ae8sM8O81CHDvbFcDgpVJ+2cJtSA9IRuv/yVEefaD50m1p3Rpvy88BNR70VnL > begyYzOB21eMjHTT3aQgfyLsXWRS4LOVFIrHrv1slLV31caznhD4HB/xTTxXWA3b > ecB9yjDpKBtiB19ECdchLRI5tpQBHDKN3edcGPdfhelcuxD8eJT48QqrWEBzFcQl > zIeZm4Ge9F968GmpprReohNUdZebdc7x/dyrfg1sXF8MQw4rUsI= > =2IrO > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Is it possible to get the benefits of working with apache-tomcat in tomcat at once?
Hello, Dear Friends! Usually, to solve the tomcat's SocketException problem and to show error page, I will connect Apache using JK Connector. But, two web servers is make management difficult. So, I wish I could be provided with some feature on Tomcat. Proxy Connector -> HTTP/1.1 -> Servlet -> ... This Connector's primary goal is to show error or redirect page even all HTTP/1.1 Connector is busy. Is this a possible idea? Thank you for reading. Have a nice day!!
