jetty-users http://dev.eclipse.org/mhonarc/lists/jetty-users/maillist.html jetty-users en-us Wed, 23 May 2012 08:40:09 GMT Wed, 23 May 2012 08:40:09 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) jetty-users http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/jetty-users/maillist.html Re: [jetty-users] [SPAM] Re: jetty-maven-plugin v7.5.0.v20110901 no longer respects system properties? http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02244.html Aaron, Out of curiosity, can you try instead shifting your <systemProperties> up to be the first configuration of the plugin, before any <webApp> (aliased also to <webAppConfig>) or any other elements? Perhaps that will get the system property set before any Jetty classes are loaded that cause the loading of AbstractLifeCycle class and its static LOG reference. Let me know if that works and I'll update the doco. thanks Jan On 22 May 2012 17:20, Pieper, Aaron <PieperA@xxxxxxxxxxxxxx> wrote: > I did a little more research and found out what's causing this conflict between newer versions of Jetty, and Log4j. > > When the AbstractLifeCycle class is loaded in Jetty 7.5.0, it initializes its static LOG field which results in a getLogger call, initializing the Log4j framework. At this time, the "log4j.configuration" system property is unset. ObjectWithFieldsConverter.processConfiguration is later invoked, which sets the system properties appropriately. However, by this time, log4j has already been initialized improperly because of AbstractLifeCycle's getLogger invocation. > > Back in Jetty 7.4.5, setProperty was invoked by ObjectWithFieldsConverter.processConfiguration, but the log was not initialized until later. There were no Jetty calls to getLogger, so the logging system wasn't initialized until my web application started up. The AbstractLifeCycle.LOG field is new to Jetty 7.5.0, and causes the Log4j system to be initialized before the jetty-maven-plugin has a chance to set system properties. > > I was able to work around this problem by using the properties-maven-plugin (http://mojo.codehaus.org/properties-maven-plugin/) to set the system property before Jetty's AbstractLifeCycle class is loaded. However, this seems like a regression in Jetty since after Jetty 7.5.0, the SystemProperties parameter can no longer be used to initialize logging systems like log4j. This regression seems like it would also affect any other logging systems which lazily initialize in response to the first getLogger call. > > - Aaron > > -----Original Message----- > From: jetty-users-bounces@xxxxxxxxxxx [mailto:jetty-users-bounces@xxxxxxxxxxx] On Behalf Of Jan Bartel > Sent: Monday, May 21, 2012 10:07 AM > To: JETTY user mailing list > Subject: [SPAM] Re: [jetty-users] jetty-maven-plugin v7.5.0.v20110901 no longer respects system properties? > Importance: Low > > Can you print out or otherwise examine what the value of the SystemProperty that is set via the pom.xml is at runtime? AFAIK, the system property stuff has not changed in a long time ... BTW, > jetty-7.5 is still a very old version, the most recent being 7.6.3. > > Jan > > On 15 May 2012 20:44, Pieper, Aaron <PieperA@xxxxxxxxxxxxxx> wrote: >> I run Jetty via the jetty-maven-plugin, from the command line, with a >> command like "mvn jetty:run". After upgrading from jetty-maven-plugin >> v7.4.5.v20110725 to v7.5.0.v20110901, my log4j.properties file is no >> longer being parsed. It is not being parsed because the >> log4j.configuration system property is no longer being set when >> running Jetty. I have this configuration in my pom.xml... >> >> >> >> <plugin> >> >> <groupId>org.mortbay.jetty</groupId> >> >> <artifactId>jetty-maven-plugin</artifactId> >> >> <version>7.5.0.v20110901</version> >> >> <configuration> >> >>   <war>${project.build.directory}/${webappName}.war</war> >> >>   ... snip ... >> >>   <systemProperties> >> >>   <systemProperty> >> >>     <key>log4j.configuration</key> >> >> >> <value>file:${project.build.outputDirectory}/log4j.properties</value> >> >>   </systemProperty> >> >> >> >> As of Jetty v7.5.0, this log4j.configuration system property is no >> longer being respected. I can still set the property via the command >> line with "mvn jetty:run >> -Dlog4j.configuration=file:./target/classes/log4j.properties", >> this works fine. I suspect this problem is due to a change in syntax >> of the systemProperties xml element. >> >> >> >> There is documentation for setting up the systemProperties element >> with the Jetty 6 plugin >> (http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin#MavenJettyP >> lugin-sysprops), but I cannot find any comparable documentation for >> the Jetty 7 plugin. The closest thing I can find >> (http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin) says, "For >> more information, see Setting System Properties," but there is no >> hyperlink anywhere. Was this omitted accidentally? >> >> >> >> Thanks, >> >> >> >> - Aaron >> >> >> _______________________________________________ >> jetty-users mailing list >> jetty-users@xxxxxxxxxxx >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > _______________________________________________ > jetty-users mailing list > jetty-users@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/jetty-users > _______________________________________________ > jetty-users mailing list > jetty-users@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/jetty-users ]]> Wed, 23 May 2012 08:31:30 GMT http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02244.html janb@xxxxxxx (Jan Bartel) Re: [jetty-users] [SPAM] Re: jetty-maven-plugin v7.5.0.v20110901 no longer respects system properties? http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02243.html _______________________________________________ jetty-users mailing list jetty-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/jetty-users I did a little more research and found out what's causing this conflict between newer versions of Jetty, and Log4j. When the AbstractLifeCycle class is loaded in Jetty 7.5.0, it initializes its static LOG field which results in a getLogger call, initializing the Log4j framework. At this time, the "log4j.configuration" system property is unset. ObjectWithFieldsConverter.processConfiguration is later invoked, which sets the system properties appropriately. However, by this time, log4j has already been initialized improperly because of AbstractLifeCycle's getLogger invocation. Back in Jetty 7.4.5, setProperty was invoked by ObjectWithFieldsConverter.processConfiguration, but the log was not initialized until later. There were no Jetty calls to getLogger, so the logging system wasn't initialized until my web application started up. The AbstractLifeCycle.LOG field is new to Jetty 7.5.0, and causes the Log4j system to be initialized before the jetty-maven-plugin has a chance to set system properties. I was able to work around this problem by using the properties-maven-plugin (http://mojo.codehaus.org/properties-maven-plugin/) to set the system property before Jetty's AbstractLifeCycle class is loaded. However, this seems like a regression in Jetty since after Jetty 7.5.0, the SystemProperties parameter can no longer be used to initialize logging systems like log4j. This regression seems like it would also affect any other logging systems which lazily initialize in response to the first getLogger call. - Aaron -----Original Message----- From: jetty-users-bounces@xxxxxxxxxxx [mailto:jetty-users-bounces@xxxxxxxxxxx] On Behalf Of Jan Bartel Sent: Monday, May 21, 2012 10:07 AM To: JETTY user mailing list Subject: [SPAM] Re: [jetty-users] jetty-maven-plugin v7.5.0.v20110901 no longer respects system properties? Importance: Low Can you print out or otherwise examine what the value of the SystemProperty that is set via the pom.xml is at runtime? AFAIK, the system property stuff has not changed in a long time ... BTW, jetty-7.5 is still a very old version, the most recent being 7.6.3. Jan On 15 May 2012 20:44, Pieper, Aaron <PieperA@xxxxxxxxxxxxxx> wrote: > I run Jetty via the jetty-maven-plugin, from the command line, with a > command like "mvn jetty:run". After upgrading from jetty-maven-plugin > v7.4.5.v20110725 to v7.5.0.v20110901, my log4j.properties file is no > longer being parsed. It is not being parsed because the > log4j.configuration system property is no longer being set when > running Jetty. I have this configuration in my pom.xml... > > > > <plugin> > > <groupId>org.mortbay.jetty</groupId> > > <artifactId>jetty-maven-plugin</artifactId> > > <version>7.5.0.v20110901</version> > > <configuration> > >   <war>${project.build.directory}/${webappName}.war</war> > >   ... snip ... > >   <systemProperties> > >   <systemProperty> > >     <key>log4j.configuration</key> > >      > <value>file:${project.build.outputDirectory}/log4j.properties</value> > >   </systemProperty> > > > > As of Jetty v7.5.0, this log4j.configuration system property is no > longer being respected. I can still set the property via the command > line with "mvn jetty:run > -Dlog4j.configuration=file:./target/classes/log4j.properties", > this works fine. I suspect this problem is due to a change in syntax > of the systemProperties xml element. > > > > There is documentation for setting up the systemProperties element > with the Jetty 6 plugin > (http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin#MavenJettyP > lugin-sysprops), but I cannot find any comparable documentation for > the Jetty 7 plugin. The closest thing I can find > (http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin) says, "For > more information, see Setting System Properties," but there is no > hyperlink anywhere. Was this omitted accidentally? > > > > Thanks, > > > > - Aaron > > > _______________________________________________ > jetty-users mailing list > jetty-users@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/jetty-users > _______________________________________________ jetty-users mailing list jetty-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/jetty-users ]]> Tue, 22 May 2012 15:20:51 GMT http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02243.html PieperA@xxxxxxx (Pieper, Aaron) Re: [jetty-users] Jetty5: CPU-Usage Problem http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02242.html Some additional infos: root@phobos ~ # uname -a Linux phobos 2.6.32-6-pve #1 SMP Mon Jan 23 08:27:52 CET 2012 x86_64 GNU/Linux root@phobos [...] # ./java -version java version &quot;1.7.0_03&quot; Java(TM) SE Runtime Environment (build 1.7.0_03-b04) Java HotSpot(TM)... Some additional infos: root@phobos ~ # uname -a Linux phobos 2.6.32-6-pve #1 SMP Mon Jan 23 08:27:52 CET 2012 x86_64 GNU/Linux root@phobos [...] # ./java -version java version "1.7.0_03" Java(TM) SE Runtime Environment (build 1.7.0_03-b04) Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode) -----Original Message----- From: jetty-users-bounces@xxxxxxxxxxx [mailto:jetty-users-bounces@xxxxxxxxxxx] On Behalf Of Maximilian Böhm Sent: Tuesday, May 22, 2012 2:51 PM To: jetty-users@xxxxxxxxxxx Subject: [jetty-users] Jetty5: CPU-Usage Problem Hi Guys, We are running jetty5 on approximately ~50 server upwards. Mostly there are more than 40 virtualhosts on a machine. Now we have a 100% cpu-usage on two of this servers. We already switched the hardware to virtualisation and now I replaced all regulary programfiles from files of a working server. Through ps -eLf and jstack I found the following (never ending) Thread: "SocketListener0-7" prio=10 tid=0x0000000001eb7000 nid=0x5d7a runnable [0x00007f569b2fc000] java.lang.Thread.State: RUNNABLE at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:782) - locked <0x00000000d1b33c60> (a java.lang.IllegalMonitorStateException) at java.lang.Throwable.<init>(Throwable.java:250) at java.lang.Exception.<init>(Exception.java:54) at java.lang.RuntimeException.<init>(RuntimeException.java:51) at java.lang.IllegalMonitorStateException.<init>(IllegalMonitorStateException.java:50) at org.mortbay.util.DateCache.format(DateCache.java:250) - locked <0x00000000ddc05c90> (a org.mortbay.util.DateCache) at org.mortbay.http.HttpRequest.getTimeStampStr(HttpRequest.java:154) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:937) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) What can cause this? I know, jetty5... Upgrading and so on. We work on it. We made a mistake ealier, integrating jetty too deep into our software... Best regards & Thanks Max Böhm _______________________________________________ jetty-users mailing list jetty-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/jetty-users ]]> Tue, 22 May 2012 12:54:50 GMT http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02242.html maximilian.boehm@xxxxxxx (Maximilian Böhm) [jetty-users] Jetty5: CPU-Usage Problem http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02241.html Hi Guys, We are running jetty5 on approximately ~50 server upwards. Mostly there are more than 40 virtualhosts on a machine. Now we have a 100% cpu-usage on two of this servers. We already switched the hardware to virtualisation and now I replaced all regu... Hi Guys, We are running jetty5 on approximately ~50 server upwards. Mostly there are more than 40 virtualhosts on a machine. Now we have a 100% cpu-usage on two of this servers. We already switched the hardware to virtualisation and now I replaced all regulary programfiles from files of a working server. Through ps -eLf and jstack I found the following (never ending) Thread: "SocketListener0-7" prio=10 tid=0x0000000001eb7000 nid=0x5d7a runnable [0x00007f569b2fc000] java.lang.Thread.State: RUNNABLE at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:782) - locked <0x00000000d1b33c60> (a java.lang.IllegalMonitorStateException) at java.lang.Throwable.<init>(Throwable.java:250) at java.lang.Exception.<init>(Exception.java:54) at java.lang.RuntimeException.<init>(RuntimeException.java:51) at java.lang.IllegalMonitorStateException.<init>(IllegalMonitorStateException.java:50) at org.mortbay.util.DateCache.format(DateCache.java:250) - locked <0x00000000ddc05c90> (a org.mortbay.util.DateCache) at org.mortbay.http.HttpRequest.getTimeStampStr(HttpRequest.java:154) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:937) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) What can cause this? I know, jetty5... Upgrading and so on. We work on it. We made a mistake ealier, integrating jetty too deep into our software... Best regards & Thanks Max Böhm ]]> Tue, 22 May 2012 12:51:11 GMT http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02241.html maximilian.boehm@xxxxxxx (Maximilian Böhm) Re: [jetty-users] jetty-maven-plugin v7.5.0.v20110901 no longer respects system properties? http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02240.html Can you print out or otherwise examine what the value of the SystemProperty that is set via the pom.xml is at runtime? AFAIK, the system property stuff has not changed in a long time ... BTW, jetty-7.5 is still a very old version, the most recent being 7.6.3. Jan On 15 May 2012 20:44, Pieper, Aaron <PieperA@xxxxxxxxxxxxxx> wrote: > I run Jetty via the jetty-maven-plugin, from the command line, with a > command like “mvn jetty:run”. After upgrading from jetty-maven-plugin > v7.4.5.v20110725 to v7.5.0.v20110901, my log4j.properties file is no longer > being parsed. It is not being parsed because the log4j.configuration system > property is no longer being set when running Jetty. I have this > configuration in my pom.xml... > > > > <plugin> > > <groupId>org.mortbay.jetty</groupId> > > <artifactId>jetty-maven-plugin</artifactId> > > <version>7.5.0.v20110901</version> > > <configuration> > >   <war>${project.build.directory}/${webappName}.war</war> > >   ... snip ... > >   <systemProperties> > >   <systemProperty> > >     <key>log4j.configuration</key> > >     <value>file:${project.build.outputDirectory}/log4j.properties</value> > >   </systemProperty> > > > > As of Jetty v7.5.0, this log4j.configuration system property is no longer > being respected. I can still set the property via the command line with “mvn > jetty:run -Dlog4j.configuration=file:./target/classes/log4j.properties”, > this works fine. I suspect this problem is due to a change in syntax of the > systemProperties xml element. > > > > There is documentation for setting up the systemProperties element with the > Jetty 6 plugin > (http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin#MavenJettyPlugin-sysprops), > but I cannot find any comparable documentation for the Jetty 7 plugin. The > closest thing I can find > (http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin) says, “For more > information, see Setting System Properties,” but there is no hyperlink > anywhere. Was this omitted accidentally? > > > > Thanks, > > > > - Aaron > > > _______________________________________________ > jetty-users mailing list > jetty-users@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/jetty-users > ]]> Mon, 21 May 2012 14:07:25 GMT http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02240.html janb@xxxxxxx (Jan Bartel) Re: [jetty-users] benchmarking sample code http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02239.html the jetty-client is the way we typically test jetty itself there are a number of examples of its usage scattered throughout our test cases, most of what you need in the tests of jetty-client itself I suspect You can also look to the BayeuxClient in the cometd project as a solid example of what can be done with it also the websocket client is based on it as well in jetty-websocket I believe alternately I have heard good things of netty as a client as well if you want to try something different cheers, jesse -- jesse mcconnell jesse.mcconnell@xxxxxxxxx On Thu, May 17, 2012 at 6:51 PM, S Ahmed <sahmed1020@xxxxxxxxx> wrote: > Any advice? > > > On Tue, May 15, 2012 at 7:44 PM, S Ahmed <sahmed1020@xxxxxxxxx> wrote: >> >> I want to benchmark my application, and was hoping there was some sample >> code that I could model my code from. >> >> Basically I need to make a http post to my servlet handler, sending it a >> xml file. >> >> I have used apache bench so far, and looked at jmeter but was hoping I >> could jus write this bit myself as I need to modify the xml file per http >> post (or every x that I post). >> >> I am looking to see how things work when I hit the site and sustain around >> 3K requests per second. >> >> Are there any good samples of this type of benchmarking that I could look >> at? >> >> I have used apache bench already, but want a little more control in terms >> of the xml file that I am posting (the xml file contains user credentials >> that I want to mix and match etc.) > > > > _______________________________________________ > jetty-users mailing list > jetty-users@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/jetty-users > ]]> Fri, 18 May 2012 00:49:42 GMT http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02239.html jesse.mcconnell@xxxxxxx (Jesse McConnell) Re: [jetty-users] benchmarking sample code http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02238.html
On Tue, May 15, 2012 at 7:44 PM, S Ahmed <sahmed1020@xxxxxxxxx> wrote:
I want to benchmark my application, and was hoping there was some sample code that I could model my code from.

Basically I need to make a http post to my servlet handler, sending it a xml file.

I have used apache bench so far, and looked at jmeter but was hoping I could jus write this bit myself as I need to modify the xml file per http post (or every x that I post).

I am looking to see how things work when I hit the site and sustain around 3K requests per second.

Are there any good samples of this type of benchmarking that I could look at?

I have used apache bench already, but want a little more control in terms of the xml file that I am posting (the xml file contains user credentials that I want to mix and match etc.)

]]> Thu, 17 May 2012 23:51:39 GMT http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02238.html sahmed1020@xxxxxxx (S Ahmed) [jetty-users] benchmarking sample code http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02237.html I want to benchmark my application, and was hoping there was some sample code that I could model my code from.Basically I need to make a http post to my servlet handler, sending it a xml file. I have used apache bench so far, and looked at jmeter but was h...
Basically I need to make a http post to my servlet handler, sending it a xml file.

I have used apache bench so far, and looked at jmeter but was hoping I could jus write this bit myself as I need to modify the xml file per http post (or every x that I post).

I am looking to see how things work when I hit the site and sustain around 3K requests per second.

Are there any good samples of this type of benchmarking that I could look at?

I have used apache bench already, but want a little more control in terms of the xml file that I am posting (the xml file contains user credentials that I want to mix and match etc.)
]]> Tue, 15 May 2012 23:44:38 GMT http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02237.html sahmed1020@xxxxxxx (S Ahmed) [jetty-users] jetty-maven-plugin v7.5.0.v20110901 no longer respects system properties? http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02236.html I run Jetty via the jetty-maven-plugin, from the command line, with a command like &#8220;mvn jetty:run&#8221;. After upgrading from jetty-maven-plugin v7.4.5.v20110725 to v7.5.0.v20110901, my log4j.properties file is no longer being parsed. It is not being parsed bec...

I run Jetty via the jetty-maven-plugin, from the command line, with a command like “mvn jetty:run”. After upgrading from jetty-maven-plugin v7.4.5.v20110725 to v7.5.0.v20110901, my log4j.properties file is no longer being parsed. It is not being parsed because the log4j.configuration system property is no longer being set when running Jetty. I have this configuration in my pom.xml...

 

<plugin>

<groupId>org.mortbay.jetty</groupId>

<artifactId>jetty-maven-plugin</artifactId>

<version>7.5.0.v20110901</version>

<configuration>

  <war>${project.build.directory}/${webappName}.war</war>

  ... snip ...

  <systemProperties>

  <systemProperty>

    <key>log4j.configuration</key>

    <value>file:${project.build.outputDirectory}/log4j.properties</value>

  </systemProperty>

 

As of Jetty v7.5.0, this log4j.configuration system property is no longer being respected. I can still set the property via the command line with “mvn jetty:run -Dlog4j.configuration=file:./target/classes/log4j.properties”, this works fine. I suspect this problem is due to a change in syntax of the systemProperties xml element.

 

There is documentation for setting up the systemProperties element with the Jetty 6 plugin (http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin#MavenJettyPlugin-sysprops), but I cannot find any comparable documentation for the Jetty 7 plugin. The closest thing I can find (http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin) says, “For more information, see Setting System Properties,” but there is no hyperlink anywhere. Was this omitted accidentally?

 

Thanks,

 

- Aaron

]]> Tue, 15 May 2012 18:44:43 GMT http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02236.html PieperA@xxxxxxx (Pieper, Aaron) Re: [jetty-users] Streaming data TO Jetty? http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02235.html Depends on the loads we're talking about. I have seen Jetty serving 40k and more POSTS per second, so &quot;more scalable&quot; depends on your mileage. A good viable alternative is to use WebSocket. Jetty has a WebSocket client that you can use to stream data to t... Hi, On Mon, May 14, 2012 at 7:20 AM, Otis Gospodnetic <otis_gospodnetic@xxxxxxxxx> wrote: > 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? Depends on the loads we're talking about. I have seen Jetty serving 40k and more POSTS per second, so "more scalable" depends on your mileage. > Is this doable and how exactly does one stream data to Jetty? A good viable alternative is to use WebSocket. Jetty has a WebSocket client that you can use to stream data to the server, and that is way more efficient than HTTP. For a comparison, see http://webtide.intalio.com/2011/09/cometd-2-4-0-websocket-benchmarks/. A full fledged solution would be to use CometD (http://cometd.org), that gives you authentication, network failure detection and automatic reconnection, an extensible framework (with already available extensions, for example for message acknowledgement, etc.), transport fallback, etc., etc. 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 ]]> Mon, 14 May 2012 08:43:02 GMT http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02235.html sbordet@xxxxxxx (Simone Bordet)