You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Jeffrey Janner <Je...@PolyDyne.com> on 2012/07/13 17:53:14 UTC

Poller & CometPoller general questions

I'm more curious here than there being a problem.
Are the Poller & CometPoller threads necessary for Tomcat operation?  If not, how to turn them off, and do I want to turn them off.
Here's my scenario:
Tomcat 6.0.33 with APR on Windows Server 2008 (regular and R2).
Fairly normal server.xml, with generic <connector> implementation, i.e., not explicitly specifying the protocol:
  <!--APR library loader. Documentation at /docs/apr.html -->
  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
    <Connector address="172.16.1.1" port="80" maxHttpHeaderSize="8192"
               maxThreads="10" enableLookups="false" redirectPort="443" acceptCount="100"
               connectionTimeout="20000" disableUploadTimeout="true" />
    <Connector address="172.16.1.1" port="443" maxHttpHeaderSize="8192"
               maxThreads="100" enableLookups="false" acceptCount="100"
               connectionTimeout="20000" disableUploadTimeout="true"
               scheme="https" secure="true" SSLEnabled="true"
               SSLCertificateFile="path to server.crt"
               SSLCertificateKeyFile=" path to server.key"
               SSLCertificateChainFile=" path to _chain.crt"
               SSLPassword="password" />
Web.xml is set up to force everything to HTTPS:
    <user-data-constraint>
      <transport-guarantee>CONFIDENTIAL</transport-guarantee>
    </user-data-constraint>

So Tomcat starts up and creates, in my case, 32 poller threads, 8 poller and 8 cometpoller for each connector.
Now, I know these just sit around waiting on AprEndpoint$Poller, basically doing nothing and really causing no harm, other than taking up some threads out of my available threadpool.
I pretty sure we don't use Comet, so I'd like to turn those off, but it's not clear in the documentation that I can, only looks like there are controls for the NIO connector.
What, if anything, would the standard Poller threads be used for?
Since everything gets forwarded to HTTPS, the HTTP poller threads seam exceptionally useless.

Jeffrey Janner
Sr. Network Administrator
jeffrey.janner@polydyne.com<ma...@polydyne.com>
PolyDyne Software Inc.
Main:   512.343.9100
Direct:  512.583.8930

 [cid:image002.png@01CC0FB7.4FF43CE0]

Speed, Intelligence & Savings in Sourcing

__________________________________________________________________________

Confidentiality Notice:  This Transmission (including any attachments) may contain information that is privileged, confidential, and exempt from disclosure under applicable law.  If the reader of this message is not the intended recipient you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited.  

If you have received this transmission in error, please immediately reply to the sender or telephone (512) 343-9100 and delete this transmission from your system.

Re: Poller & CometPoller general questions

Posted by Abduxkur Ablimit <su...@yahoo.com>.
I think what we are looking for is here :

http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#NIO_specific_configuration

useComet (bool)Whether to allow comet servlets or not. Default value is true.

I set connetor attribute to false useComet to false,but did not work as I expected,

still created those :

Daemon Thread [http-apr-80-Poller-4] (Running)    
Daemon Thread [http-apr-80-CometPoller-3] (Running)    
Daemon Thread [http-apr-80-Poller-3] (Running)    
Daemon Thread [http-apr-80-Poller-5] (Running)    
Daemon Thread [http-apr-80-Poller-7] (Running)    
Daemon Thread [http-apr-80-Poller-0] (Running)    
Daemon Thread [http-apr-80-Poller-2] (Running)    
Daemon Thread [http-apr-80-CometPoller-4] (Running)    
Daemon Thread [http-apr-80-Poller-1] (Running)    
Daemon Thread [http-apr-80-CometPoller-1] (Running)    
Daemon Thread [http-apr-80-CometPoller-6] (Running)    
Daemon Thread [http-apr-80-CometPoller-5] (Running)    
Daemon Thread [http-apr-80-CometPoller-7] (Running)    
Daemon Thread [http-apr-80-CometPoller-2] (Running)    
Daemon Thread [http-apr-80-CometPoller-0] (Running)    
Daemon Thread [http-apr-80-Poller-6] (Running)    
Daemon Thread [http-apr-80-AsyncTimeout] (Running)    
Daemon Thread [http-apr-80-Acceptor-0] (Running)    
Daemon Thread [http-apr-80-Sendfile-0] (Running)    
Daemon Thread [ajp-apr-8009-Poller-0] (Running)    
Daemon Thread [ajp-apr-8009-Poller-1] (Running)    
Daemon Thread [ajp-apr-8009-Poller-6] (Running)    
Daemon Thread [ajp-apr-8009-Poller-2] (Running)    
Daemon Thread [ajp-apr-8009-Poller-7] (Running)    
Daemon Thread [ajp-apr-8009-Poller-5] (Running)    
Daemon Thread [ajp-apr-8009-Poller-3] (Running)    
Daemon Thread [ajp-apr-8009-CometPoller-2] (Running)    
Daemon Thread [ajp-apr-8009-CometPoller-5] (Running)    
Daemon Thread [ajp-apr-8009-Poller-4] (Running)    
Daemon Thread [ajp-apr-8009-CometPoller-6] (Running)    
Daemon Thread [ajp-apr-8009-CometPoller-4] (Running)    
Daemon Thread [ajp-apr-8009-CometPoller-0] (Running)    
Daemon Thread [ajp-apr-8009-AsyncTimeout] (Running)    
Daemon Thread [ajp-apr-8009-CometPoller-3] (Running)    
Daemon Thread [ajp-apr-8009-Acceptor-0] (Running)    
Daemon Thread [ajp-apr-8009-CometPoller-7] (Running)    
Daemon Thread [ajp-apr-8009-CometPoller-1] (Running)    







________________________________
 From: Filip Hanik Mailing Lists <de...@hanik.com>
To: Tomcat Users List <us...@tomcat.apache.org> 
Sent: Wednesday, July 18, 2012 1:38 AM
Subject: Re: Poller & CometPoller general questions
 
In http://tomcat.apache.org/tomcat-7.0-doc/config/http.html
you can read about pollerThreadCount and useComet flags for the APR implementation.
You don't need Comet unless you applications specifically are using it, most likely they are not.

Filip


----- Original Message -----
> From: "Jeffrey Janner" <Je...@PolyDyne.com>
> To: "Tomcat Users List" <us...@tomcat.apache.org>
> Sent: Friday, July 13, 2012 9:53:14 AM
> Subject: Poller & CometPoller general questions
>
>
>
>
> I'm more curious here than there being a problem.
>
> Are the Poller & CometPoller threads necessary for Tomcat operation?
> If not, how to turn them off, and do I want to turn them off.
>
> Here's my scenario:
>
> Tomcat 6.0.33 with APR on Windows Server 2008 (regular and R2).
>
> Fairly normal server.xml, with generic <connector> implementation,
> i.e., not explicitly specifying the protocol:
>
> <!--APR library loader. Documentation at /docs/apr.html -->
>
> <Listener className="org.apache.catalina.core.AprLifecycleListener"
> SSLEngine="on" />
>
> <Connector address="172.16.1.1" port="80" maxHttpHeaderSize="8192"
>
> maxThreads="10" enableLookups="false" redirectPort="443"
> acceptCount="100"
>
> connectionTimeout="20000" disableUploadTimeout="true" />
>
> <Connector address="172.16.1.1" port="443" maxHttpHeaderSize="8192"
>
> maxThreads="100" enableLookups="false" acceptCount="100"
>
> connectionTimeout="20000" disableUploadTimeout="true"
>
> scheme="https" secure="true" SSLEnabled="true"
>
> SSLCertificateFile="path to server.crt"
>
> SSLCertificateKeyFile=" path to server.key"
>
> SSLCertificateChainFile=" path to _chain.crt"
>
> SSLPassword="password" />
>
> Web.xml is set up to force everything to HTTPS:
>
> <user-data-constraint>
>
> <transport-guarantee>CONFIDENTIAL</transport-guarantee>
>
> </user-data-constraint>
>
>
>
> So Tomcat starts up and creates, in my case, 32 poller threads, 8
> poller and 8 cometpoller for each connector.
>
> Now, I know these just sit around waiting on AprEndpoint$Poller,
> basically doing nothing and really causing no harm, other than
> taking up some threads out of my available threadpool.
>
> I pretty sure we don’t use Comet, so I'd like to turn those off, but
> it's not clear in the documentation that I can, only looks like
> there are controls for the NIO connector.
>
> What, if anything, would the standard Poller threads be used for?
>
> Since everything gets forwarded to HTTPS, the HTTP poller threads
> seam exceptionally useless.
>
>
>
> Jeffrey Janner
>
> Sr. Network Administrator
>
> jeffrey.janner@polydyne.com
>
> PolyDyne Software Inc.
>
> Main: 512.343.9100
>
> Direct: 512.583.8930
>
>
>
> cid:image002.png@01CC0FB7.4FF43CE0
>
>
>
> Speed, Intelligence & Savings in Sourcing
>
>
>
>
> __________________________________________________________________________
>
> Confidentiality Notice: This Transmission (including any attachments)
> may contain information that is privileged, confidential, and exempt
> from disclosure under applicable law. If the reader of this message
> is not the intended recipient you are hereby notified that any
> dissemination, distribution, or copying of this communication is
> strictly prohibited.
>
> If you have received this transmission in error, please immediately
> reply to the sender or telephone (512) 343-9100 and delete this
> transmission from your system.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: Poller & CometPoller general questions

Posted by Filip Hanik Mailing Lists <de...@hanik.com>.
In http://tomcat.apache.org/tomcat-7.0-doc/config/http.html
you can read about pollerThreadCount and useComet flags for the APR implementation.
You don't need Comet unless you applications specifically are using it, most likely they are not.

Filip


----- Original Message -----
> From: "Jeffrey Janner" <Je...@PolyDyne.com>
> To: "Tomcat Users List" <us...@tomcat.apache.org>
> Sent: Friday, July 13, 2012 9:53:14 AM
> Subject: Poller & CometPoller general questions
> 
> 
> 
> 
> I'm more curious here than there being a problem.
> 
> Are the Poller & CometPoller threads necessary for Tomcat operation?
> If not, how to turn them off, and do I want to turn them off.
> 
> Here's my scenario:
> 
> Tomcat 6.0.33 with APR on Windows Server 2008 (regular and R2).
> 
> Fairly normal server.xml, with generic <connector> implementation,
> i.e., not explicitly specifying the protocol:
> 
> <!--APR library loader. Documentation at /docs/apr.html -->
> 
> <Listener className="org.apache.catalina.core.AprLifecycleListener"
> SSLEngine="on" />
> 
> <Connector address="172.16.1.1" port="80" maxHttpHeaderSize="8192"
> 
> maxThreads="10" enableLookups="false" redirectPort="443"
> acceptCount="100"
> 
> connectionTimeout="20000" disableUploadTimeout="true" />
> 
> <Connector address="172.16.1.1" port="443" maxHttpHeaderSize="8192"
> 
> maxThreads="100" enableLookups="false" acceptCount="100"
> 
> connectionTimeout="20000" disableUploadTimeout="true"
> 
> scheme="https" secure="true" SSLEnabled="true"
> 
> SSLCertificateFile="path to server.crt"
> 
> SSLCertificateKeyFile=" path to server.key"
> 
> SSLCertificateChainFile=" path to _chain.crt"
> 
> SSLPassword="password" />
> 
> Web.xml is set up to force everything to HTTPS:
> 
> <user-data-constraint>
> 
> <transport-guarantee>CONFIDENTIAL</transport-guarantee>
> 
> </user-data-constraint>
> 
> 
> 
> So Tomcat starts up and creates, in my case, 32 poller threads, 8
> poller and 8 cometpoller for each connector.
> 
> Now, I know these just sit around waiting on AprEndpoint$Poller,
> basically doing nothing and really causing no harm, other than
> taking up some threads out of my available threadpool.
> 
> I pretty sure we don’t use Comet, so I'd like to turn those off, but
> it's not clear in the documentation that I can, only looks like
> there are controls for the NIO connector.
> 
> What, if anything, would the standard Poller threads be used for?
> 
> Since everything gets forwarded to HTTPS, the HTTP poller threads
> seam exceptionally useless.
> 
> 
> 
> Jeffrey Janner
> 
> Sr. Network Administrator
> 
> jeffrey.janner@polydyne.com
> 
> PolyDyne Software Inc.
> 
> Main: 512.343.9100
> 
> Direct: 512.583.8930
> 
> 
> 
> cid:image002.png@01CC0FB7.4FF43CE0
> 
> 
> 
> Speed, Intelligence & Savings in Sourcing
> 
> 
> 
> 
> __________________________________________________________________________
> 
> Confidentiality Notice: This Transmission (including any attachments)
> may contain information that is privileged, confidential, and exempt
> from disclosure under applicable law. If the reader of this message
> is not the intended recipient you are hereby notified that any
> dissemination, distribution, or copying of this communication is
> strictly prohibited.
> 
> If you have received this transmission in error, please immediately
> reply to the sender or telephone (512) 343-9100 and delete this
> transmission from your system.
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org