Re: [jetty-users] Jetty Hightide still around?
Thanks Jesse for the quick and thorough explanation. Otis -- Performance Monitoring - http://sematext.com/spm/index.html Search Analytics - http://sematext.com/search-analytics/index.html On Tue, Dec 4, 2012 at 1:45 PM, Jesse McConnell jesse.mcconn...@gmail.comwrote: Originally Hightide (with jetty6) was a tight integration of some extra software components into a full on separate offering from the traditional jetty download. This was when both concepts of 'jetty' and 'hightide' were housed at The Codehaus. Then in 2009 or so we decided to move the project to The Eclipse Foundation and were suddenly having to sort out how to distribute a split project as not everything was able to come to eclipse because of IP reasons (they are very strict about what can and can't be downloaded from eclipse) and we had to work for years with a org.eclipse.jetty:jetty-distribution and then _something_ that contained some of the stuff that was left at The Codehaus. That extra distribution took on the monikor of hightide and over time things started getting removed from it that made it different from the normal jetty-distribution. Ultimately it because nothing more then a thin skin over the jetty-distribution so we have decided to let it fade away as something unique. Now with jetty-9 there is no 'Hightide' distribution per se...and no more active components at The Codehaus for jetty-9. We have migrated the jetty-maven-plugin over from codehaus to eclipse and any active remaining modules as well. Moving forward we will have one release on release day, a jetty-9 release whereas before with jetty7 and jetty8 releasing simultaneously on both the eclipse and codehaus sides release day was comprised of 4 separate releases at the same time. With jetty-9 we would like to have a more 'plugin' friendly setup for third party integrations but we shelved our early efforts in that setup as not ready for prime time and we'll pick it back up when we have a more clear need and use cases. Should the integrations formerly known as hightide surface in jetty-9 it would be through such a plugin mechanism as opposed to a full on separate distribution artifact as before. cheers, jesse -- jesse mcconnell jesse.mcconn...@gmail.com On Tue, Dec 4, 2012 at 12:26 PM, Otis Gospodnetic otis.gospodne...@gmail.com wrote: Hi, I was looking for information about Jetty Hightide and was unable to find out if Jetty Hightide is something that belongs to the past, or if Jetty Hightide is a packaging of Jetty that is still available with every new Jetty 7/8/9 release? I looked at http://download.eclipse.org/jetty/ and could not find any mention of Hightide, which makes me think Jetty Hightide doesn't really exist any more? Thanks, Otis Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
Re: [jetty-users] Vert.x-like functionality in Jetty?
Hi, Are you saying CometD provides the same scalability and concurrency Vert.x claims to provide? If CometD provides (and has been providing for years) the high scalability and concurrency support, what's all Vert.x all about? Is it the case that while CometD may provide the same stuff Vert.x does, CometD is not widely known or is at least not as popular? (if so, that can be critical for its future) Thanks, Otis Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm From: Simone Bordet sbor...@intalio.com To: Otis Gospodnetic otis_gospodne...@yahoo.com; JETTY user mailing list jetty-users@eclipse.org Sent: Thursday, May 24, 2012 2:48 AM Subject: Re: [jetty-users] Vert.x-like functionality in Jetty? Hi, On Thu, May 24, 2012 at 7:04 AM, Otis Gospodnetic otis_gospodne...@yahoo.com wrote: Hi, Is there anything in Jetty (any version) that is Vert.x (see http://vertx.io/ ) like? I'm mainly referring to scalability and concurrency, as well as that distributed event bus. You should have a look at CometD, http://cometd.org. CometD is a web messaging platform, it scales well (see http://webtide.intalio.com/2011/09/cometd-2-4-0-websocket-benchmarks/), it's mature (years of experience) and has been successfully deployed on small and large systems for years now, relying on standard technologies such as Servlets and WebSocket. What is it that appealed you in Vert.x, apart the (frankly irrealistic) benchmark it was published some time ago, that you would like to see in Jetty/CometD ? Simon -- http://cometd.org http://intalio.com http://bordet.blogspot.com Finally, no matter how good the architecture and design are, to deliver bug-free software with optimal performance and reliability, the implementation technique must be flawless. Victoria Livschitz ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
Re: [jetty-users] Vert.x-like functionality in Jetty?
Thanks Simone, I think Vert.x has more than just a spike of tweets, though :) What I'm after is something that can handle a high number of concurrent connections from an HTTP client (e.g. Apache HttpClient) to an HTTP server (Jetty?). You can see in my sig why I'm interested in this Thanks, Otis Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm - Original Message - From: Simone Bordet sbor...@intalio.com To: Otis Gospodnetic otis_gospodne...@yahoo.com; JETTY user mailing list jetty-users@eclipse.org Cc: Sent: Thursday, May 24, 2012 5:16 PM Subject: Re: [jetty-users] Vert.x-like functionality in Jetty? Hi, On Thu, May 24, 2012 at 8:59 PM, Otis Gospodnetic otis_gospodne...@yahoo.com wrote: Hi, Are you saying CometD provides the same scalability and concurrency Vert.x claims to provide? Look carefully at the Vert.x benchmark: they open 6 (six) connections and pipeline on each 2000 requests. How realistic is such traffic ? I am sure Vert.x 1.0 is a fine framework and all that, but I'd like to see a more realistic benchmark before expressing an opinion. That is what we tried to achieve with the CometD benchmark, which implements a chat application, with 1k, 5k 10k up to 200k connected users to a single server and different message rates. If CometD provides (and has been providing for years) the high scalability and concurrency support, what's all Vert.x all about? Ask them :) To me, it's about diversity. Why there exist more than one servlet container ? Is it the case that while CometD may provide the same stuff Vert.x does, CometD is not widely known or is at least not as popular? (if so, that can be critical for its future) Not sure what Vert.x provides yet (have not looked in details), but CometD provides authentication hooks, fine-grained access control, message acknowledgment and guaranteed server-to-client message delivery on short network failures, a fully extensible framework, transport independence and fallback, automatic reconnections, and I can continue for a while. I heard about Vert.x one month or less ago, actually, so I personally do not classify it as popular just because it had a spike in tweets. Evaluate both frameworks and choose the one that fits your case better. You have not said what is it in Vert.x that appeals you. It's just the benchmark result ? Simon -- http://cometd.org http://intalio.com http://bordet.blogspot.com Finally, no matter how good the architecture and design are, to deliver bug-free software with optimal performance and reliability, the implementation technique must be flawless. Victoria Livschitz ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
Re: [jetty-users] Apache HttpClient vs Java UrlConnection
Joakim, That's probably a good question from HttpClient mailing list I'd be curious about what info you can get there... Otis Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm From: Joakim Erdfelt joa...@intalio.com To: Otis Gospodnetic otis_gospodne...@yahoo.com; JETTY user mailing list jetty-users@eclipse.org Sent: Thursday, May 24, 2012 5:38 PM Subject: Apache HttpClient vs Java UrlConnection Is apache httpclient still viable? Speaking from experience using both it and standard java UrlConnection on Android (key piece of info there), the standard java UrlConnection is faster in all aspects of http, from establishing the connection, handling the streams, authenticating, and even concurrent active connections than the Apache HttpClient on the same device. No amount of tweaking of the apache httpclient could even get close to the standard naive implementation using Java UrlConnection. Why is that? Really, why? Before this experience i was a huge fan of apache httpclient (i like the control I have over the http transactions), but now... -- Joakim Erdfelt On Thu, May 24, 2012 at 2:32 PM, Otis Gospodnetic otis_gospodne...@yahoo.com wrote: Thanks Simone, I think Vert.x has more than just a spike of tweets, though :) What I'm after is something that can handle a high number of concurrent connections from an HTTP client (e.g. Apache HttpClient) to an HTTP server (Jetty?). You can see in my sig why I'm interested in this Thanks, Otis Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm - Original Message - From: Simone Bordet sbor...@intalio.com To: Otis Gospodnetic otis_gospodne...@yahoo.com; JETTY user mailing list jetty-users@eclipse.org Cc: Sent: Thursday, May 24, 2012 5:16 PM Subject: Re: [jetty-users] Vert.x-like functionality in Jetty? Hi, On Thu, May 24, 2012 at 8:59 PM, Otis Gospodnetic otis_gospodne...@yahoo.com wrote: Hi, Are you saying CometD provides the same scalability and concurrency Vert.x claims to provide? Look carefully at the Vert.x benchmark: they open 6 (six) connections and pipeline on each 2000 requests. How realistic is such traffic ? I am sure Vert.x 1.0 is a fine framework and all that, but I'd like to see a more realistic benchmark before expressing an opinion. That is what we tried to achieve with the CometD benchmark, which implements a chat application, with 1k, 5k 10k up to 200k connected users to a single server and different message rates. If CometD provides (and has been providing for years) the high scalability and concurrency support, what's all Vert.x all about? Ask them :) To me, it's about diversity. Why there exist more than one servlet container ? Is it the case that while CometD may provide the same stuff Vert.x does, CometD is not widely known or is at least not as popular? (if so, that can be critical for its future) Not sure what Vert.x provides yet (have not looked in details), but CometD provides authentication hooks, fine-grained access control, message acknowledgment and guaranteed server-to-client message delivery on short network failures, a fully extensible framework, transport independence and fallback, automatic reconnections, and I can continue for a while. I heard about Vert.x one month or less ago, actually, so I personally do not classify it as popular just because it had a spike in tweets. Evaluate both frameworks and choose the one that fits your case better. You have not said what is it in Vert.x that appeals you. It's just the benchmark result ? Simon -- http://cometd.org http://intalio.com http://bordet.blogspot.com Finally, no matter how good the architecture and design are, to deliver bug-free software with optimal performance and reliability, the implementation technique must be flawless. Victoria Livschitz ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
[jetty-users] Vert.x-like functionality in Jetty?
Hi, Is there anything in Jetty (any version) that is Vert.x (see http://vertx.io/ ) like? I'm mainly referring to scalability and concurrency, as well as that distributed event bus. Thanks, Otis Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
[jetty-users] Streaming data TO Jetty?
Hello, I'd like to be able to push data (more or less a continuous stream) from clients (e.g. using Apache HttpClient library) TO Jetty. I currently have a system where clients make use of KeepAlives, which is nice, but they still issue an explicit HTTP POST request to Jetty every N seconds. Is there a way to avoid making explicit HTTP requests like that and would streaming the data (somehow) actually be more scalable than issuing explicit POSTs? Is this doable and how exactly does one stream data to Jetty? Thank you, Otis Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
[jetty-users] (Am I) using persistent connections with Jetty
Hello, Would using Jetty (7? 8?) and persistent connections make sense in situations where clients more or less constantly stream data to the server? For example, imagine a system where client applications: * are running on hundreds of nodes of some cluster * are constantly collecting performance metrics * are sending these metrics via HTTP to some server Qs: * Would it make more sense to have clients keep persistent connections with the server instead of opening/closing them? * If I'm not explicitly closing HTTP connections on either client (using HttpClient lib) or server (servlet running in Jetty 7.*) side, am I effectively already keeping all connections open/persistent? Thanks, Otis Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
Re: [jetty-users] monitoring jetty threads and sockets
Hi Paulo, I think you get that from http://sematext.com/spm/index.html (it's currently free and even when non-free plans are introduced, the intro plan will stay free). The service is not 100% polished, but will give you information about the OS and the JVM, including memory (RAM and heap) and JVM threads. We'd love to get more Jetty-specific metrics from JMX in there, so if anyone has interest, we'd love to hear what aspects of Jetty people like to monitor. I'm all ears/eyeballs! Otis Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem search :: http://search-lucene.com/ From: Paulo Silveira - Caelum paulo.silve...@caelum.com.br To: jetty-users@eclipse.org Sent: Thursday, June 16, 2011 11:37 AM Subject: [jetty-users] monitoring jetty threads and sockets Hello I would like to monitor simple data from jetty, using only a web context. Is there anything like that, besides the codehaus documentation page about java-monitor? Basic info, as numbers from ThreadMXBean, MemoryUsage and so one. Tomcat/Lambda probe also lists each thread status and stacktrace, making possible to easily detect even deadlocks. Through java.lang.management we can get all this data, but using jetty's internal API could we get even more important info, as number of sockets waiting/ready for the selector? thanks -- Paulo Silveira Caelum | Ensino e Inovação www.caelum.com.br ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users ___ jetty-users mailing list jetty-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/jetty-users
