Re: question about APR based native library
On 15 Apr 2010, at 19:15, Bill Au bill.w...@gmail.com wrote: I am using 6.0.26. The native library is loaded. I am not as concern about SSL since most of our application don't use SSL. I am guessing that most people don't use the native library. Why, what makes you think that? One of my concern is stability. With a smaller user community, is the native code less stable than the pure Java code? Less usage could mean that there may be bugs that have not been shaken out yet. You're making an assumption based on assumption. Using APR gives you access to the same code libs used by HTTPD, which has a fairly large community. p Bill On Thu, Apr 15, 2010 at 1:03 PM, Jeffrey Janner jeffrey.jan...@polydyne.com wrote: Other than the different SSL implementation? It depends on the release of Tomcat you are using. 5.5.28 (and some release of 6.x) won't properly recognize the library. That is fixed in current releases. -Original Message- From: Bill Au [mailto:bill.w...@gmail.com] Sent: Thursday, April 15, 2010 9:25 AM To: Tomcat Users List Subject: question about APR based native library Are there any reasons I shouldn't use the APR based native libaray? Or at least things that I should be aware of if I do use it? According to the documentation using the native library will give better scalability and performance. I want to understand if there are any downside since with most things there are both upside and downside. Bill *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and 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 or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. - 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: question about APR based native library
On 4/16/2010 6:17 AM, Pid * wrote: On 15 Apr 2010, at 19:15, Bill Aubill.w...@gmail.com wrote: I am using 6.0.26. The native library is loaded. I am not as concern about SSL since most of our application don't use SSL. I am guessing that most people don't use the native library. Why, what makes you think that? One of my concern is stability. With a smaller user community, is the native code less stable than the pure Java code? Less usage could mean that there may be bugs that have not been shaken out yet. You're making an assumption based on assumption. Using APR gives you access to the same code libs used by HTTPD, which has a fairly large community. ^^ That's probably the understatement of the year so far. D - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: question about APR based native library
Sorry about my assumption(s). I made them based on information I gathered from talking to Tomcat users I know. My sample size is small so my assumptions may not be valid. By smaller user community I don't mean APR. I mean the APR connector Http11AprProtocol. Bill On Fri, Apr 16, 2010 at 6:17 AM, Pid * p...@pidster.com wrote: On 15 Apr 2010, at 19:15, Bill Au bill.w...@gmail.com wrote: I am using 6.0.26. The native library is loaded. I am not as concern about SSL since most of our application don't use SSL. I am guessing that most people don't use the native library. Why, what makes you think that? One of my concern is stability. With a smaller user community, is the native code less stable than the pure Java code? Less usage could mean that there may be bugs that have not been shaken out yet. You're making an assumption based on assumption. Using APR gives you access to the same code libs used by HTTPD, which has a fairly large community. p Bill On Thu, Apr 15, 2010 at 1:03 PM, Jeffrey Janner jeffrey.jan...@polydyne.com wrote: Other than the different SSL implementation? It depends on the release of Tomcat you are using. 5.5.28 (and some release of 6.x) won't properly recognize the library. That is fixed in current releases. -Original Message- From: Bill Au [mailto:bill.w...@gmail.com] Sent: Thursday, April 15, 2010 9:25 AM To: Tomcat Users List Subject: question about APR based native library Are there any reasons I shouldn't use the APR based native libaray? Or at least things that I should be aware of if I do use it? According to the documentation using the native library will give better scalability and performance. I want to understand if there are any downside since with most things there are both upside and downside. Bill *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and 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 or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. - 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: question about APR based native library
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Konstantin, On 4/15/2010 7:17 PM, Konstantin Kolinko wrote: The main competitors are APR connector vs. Nio connector, as both provide multiplexing aka polling, allowing to serve more sockets than the count of your worker threads. The APR connector sure has a bit more longer history, dating back to TC 5.5. The Nio connector is more modern, available since TC 6.x only, but that is several years already. My (as yet unpublished) performance tests show that APR and NIO offer virtually the same performance. Make sure you set sendFile=true if you are doing any significant static-file serving through your Tomcat instance. less stable than the pure Java code Note, that that also depends on the JRE implementation that you would be using. +1 The APR code is more likely to actually crash your JVM than the pure-Java implementation, but I haven't seen any recent complaints about APR crashing at all. Jeffrey is having a bear of a time getting APR working in his environment due to a number of issues that are all piling up. My advice: set up a testing environment where you can play and perform load testing. Compare the performance of the NIO versus APR connectors. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvI0V0ACgkQ9CaO5/Lv0PB1awCbBSPmpnyo1zPSn0pEmXwBBTVm 1kkAoJtNgbJHSRBCEbQpjhiFhg6ucAS1 =U+zf -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
question about APR based native library
Are there any reasons I shouldn't use the APR based native libaray? Or at least things that I should be aware of if I do use it? According to the documentation using the native library will give better scalability and performance. I want to understand if there are any downside since with most things there are both upside and downside. Bill
RE: question about APR based native library
Other than the different SSL implementation? It depends on the release of Tomcat you are using. 5.5.28 (and some release of 6.x) won't properly recognize the library. That is fixed in current releases. -Original Message- From: Bill Au [mailto:bill.w...@gmail.com] Sent: Thursday, April 15, 2010 9:25 AM To: Tomcat Users List Subject: question about APR based native library Are there any reasons I shouldn't use the APR based native libaray? Or at least things that I should be aware of if I do use it? According to the documentation using the native library will give better scalability and performance. I want to understand if there are any downside since with most things there are both upside and downside. Bill *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and 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 or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: question about APR based native library
I am using 6.0.26. The native library is loaded. I am not as concern about SSL since most of our application don't use SSL. I am guessing that most people don't use the native library. One of my concern is stability. With a smaller user community, is the native code less stable than the pure Java code? Less usage could mean that there may be bugs that have not been shaken out yet. Bill On Thu, Apr 15, 2010 at 1:03 PM, Jeffrey Janner jeffrey.jan...@polydyne.com wrote: Other than the different SSL implementation? It depends on the release of Tomcat you are using. 5.5.28 (and some release of 6.x) won't properly recognize the library. That is fixed in current releases. -Original Message- From: Bill Au [mailto:bill.w...@gmail.com] Sent: Thursday, April 15, 2010 9:25 AM To: Tomcat Users List Subject: question about APR based native library Are there any reasons I shouldn't use the APR based native libaray? Or at least things that I should be aware of if I do use it? According to the documentation using the native library will give better scalability and performance. I want to understand if there are any downside since with most things there are both upside and downside. Bill *** NOTICE * This message is intended for the use of the individual or entity to which it is addressed and 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 or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply or by telephone (call us collect at 512-343-9100) and immediately delete this message and all its attachments. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: question about APR based native library
2010/4/15 Bill Au bill.w...@gmail.com: I am using 6.0.26. The native library is loaded. I am not as concern about SSL since most of our application don't use SSL. I am guessing that most people don't use the native library. One of my concern is stability. With a smaller user community, is the native code less stable than the pure Java code? Less usage could mean that there may be bugs that have not been shaken out yet. At the end of the following page there is a table comparing the feature sets provided by the different connector implementations: http://tomcat.apache.org/tomcat-6.0-doc/config/http.html The main competitors are APR connector vs. Nio connector, as both provide multiplexing aka polling, allowing to serve more sockets than the count of your worker threads. The APR connector sure has a bit more longer history, dating back to TC 5.5. The Nio connector is more modern, available since TC 6.x only, but that is several years already. less stable than the pure Java code Note, that that also depends on the JRE implementation that you would be using. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
