jetty-dev http://dev.eclipse.org/mhonarc/lists/jetty-dev/maillist.html jetty-dev en-us Wed, 19 Jun 2013 23:10:08 GMT Wed, 19 Jun 2013 23:10:08 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) jetty-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/jetty-dev/maillist.html [jetty-dev] Branch jetty-9.1 has been created http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01802.html Just a heads up.The branch jetty-9.1 has been created.It is based off of the existing servlet-3.1-api branch. I'll be merging jetty-9.1 branch to the existing javawebsocket-jsr branch now.And tomorrow morning the javawebsocket-jsr branch will be merged bac...
Just a heads up.

The branch jetty-9.1 has been created.
It is based off of the existing servlet-3.1-api branch.

I'll be merging jetty-9.1 branch to the existing javawebsocket-jsr branch now.
And tomorrow morning the javawebsocket-jsr branch will be merged back into the jetty-9.1 branch.

Eventually, this branch will become master, but as for when, that is still undetermined.


--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Developer advice, services and support
from the Jetty & CometD experts
]]> Wed, 19 Jun 2013 23:00:13 GMT http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01802.html joakim@xxxxxxx (Joakim Erdfelt) [jetty-dev] Newbie question - permission issue trying to utilize Bluetooth on I-Jetty for Android http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01801.html Hi everyone. I&#8217;m brand new to web technologies AND android, so I appreciate your kindness if my questions are particularly ignorant. J I&#8217;ve been able to set up some simple Java Servlets using I-Jetty for Android, and now I&#8217;m trying to utilize the Bluet...

Hi everyone.  I’m brand new to web technologies AND android, so I appreciate your kindness if my questions are particularly ignorant. J

 

I’ve been able to set up some simple Java Servlets using I-Jetty for Android, and now I’m trying to utilize the Bluetooth services so I can effectively use the I-Jetty server as a “bridge” to a Bluetooth device.

 

Currently I’ve run into this problem and I’m stuck – any help would be appreciated.  (FYI – I’ve been able to utilize Bluetooth in Beanshell using the PAW server, so I know its technically possible to do this in Android.  I’m not sure what kind of “magic” PAW uses to make this possible, though – does the I-Jetty manifest need to be recompiled to get Bluetooth permissions or something like that??)

 

HTTP ERROR 500

Problem accessing /BtDemo6/servlet. Reason:

    Need BLUETOOTH permission: Neither user 10077 nor current process has android.permission.BLUETOOTH.

Caused by:

java.lang.SecurityException: Need BLUETOOTH permission: Neither user 10077 nor current process has android.permission.BLUETOOTH.
        at android.os.Parcel.readException(Parcel.java:1425)
        at android.os.Parcel.readException(Parcel.java:1379)
        at android.bluetooth.IBluetooth$Stub$Proxy.isEnabled(IBluetooth.java:550)
        at android.bluetooth.BluetoothAdapter.isEnabled(BluetoothAdapter.java:446)
        at BtDemoServlet.doPost(BtDemoServlet.java:46)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:546)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:479)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:483)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1031)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:406)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:965)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
        at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
        at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)
        at org.eclipse.jetty.server.Server.handle(Server.java:349)
        at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:449)
        at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:910)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:647)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:233)
        at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:76)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:615)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:45)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
        at java.lang.Thread.run(Thread.java:856)

Powered by Jetty://

 

Here’s an excerpt of the relevant code in the servlet:

 

import android.bluetooth.*;

  import android.os.*;

  import android.content.*;

  import java.io.*;

  import java.util.*;

  import javax.servlet.*;

  import javax.servlet.http.*;

  import android.app.*;

  import android.view.*;

  public class BtDemoServlet extends HttpServlet

  {

  

      protected void doPost(HttpServletRequest req, HttpServletResponse resp)

          throws ServletException, IOException

      {

         BluetoothAdapter mBluetoothAdapter;

 

          PrintWriter out = resp.getWriter();

 

          out.println("<html>");

          out.println("<body>");

 

          mBluetoothAdapter = BluetoothAdapter.getDefaultAdapter();

 

          if (!mBluetoothAdapter.isEnabled()) //This is the line that causes the error

          {

…

          }

      }

  }

 

  

  




[CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com

]]> Tue, 11 Jun 2013 16:45:10 GMT http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01801.html mark.salzwedel@xxxxxxx (Salzwedel, Mark) [jetty-dev] WebSocket changes http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01800.html There&#39;s a number of websocket api changes I want to make, both short term and long term.What I need to know is what is appropriate for versioning these changes in. First the short term changes.1)&#xA0;https://bugs.eclipse.org/bugs/show_bug.cgi?id=410175 410175 ...
There's a number of websocket api changes I want to make, both short term and long term.
What I need to know is what is appropriate for versioning these changes in.

First the short term changes.

1) https://bugs.eclipse.org/bugs/show_bug.cgi?id=410175
410175 - WebSocketSession#isSecure() doesn't return true for SSL session on the server side

The heart of this bug ...
Both the isSecure() flag is incorrect (a bug), and the URI returned from UpgradeRequest.getRequetURI() is the URI of the incoming servlet request (in other words the http/https scheme), not the ws:// format scheme.

2) https://bugs.eclipse.org/bugs/show_bug.cgi?id=410370
WebSocketCreator.createWebSocket() should use servlet specific parameters

The createWebSocket() parameters are the generic API UpgradeRequest and UpgradeResponse interfaces.  There has been a request to make that method be servlet specific.
This would introduce in the websocket-servlet package the ServletUpgradeRequest and ServletUpgradeResponse interfaces.
The existing implementations for this in websocket-server is will be adjusted to use this new interface.

This change will also help with the next bug
3) https://bugs.eclipse.org/bugs/show_bug.cgi?id=410372
Make SSL client certificate information available to server websockets

This would expose the SSL client certificate in the new ServletUpgadeRequest interface (and implementation) for use in the WebSocketCreator.

These short term changes would affect the existing API so I don't want to make changes like this lightly, especially with the upcoming 9.0.x release and timing of the future 9.1.x branch.

For the longer term, we have many changes coming as a result of the JSR-356 (Java Websocket API) support, and that might be best put into the 9.1 release.

Any opinions on where and when to make these short term API changes?


--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Developer advice, services and support
from the Jetty & CometD experts
]]> Mon, 10 Jun 2013 18:06:00 GMT http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01800.html joakim@xxxxxxx (Joakim Erdfelt) Re: [jetty-dev] (no subject) http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01799.html Couple of things:

- the xml configuration mode you are talking about is really just a thin skin over java itself, so everything you see in xml is easily doable in java, all the xml does is get processed and then called in java through reflection

-Âhttp://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/tree/example-jetty-embedded/src/main/java/org/eclipse/jetty/embedded/SecuredHelloHandler.java?h=jetty-8 is an example of a simple hash login service being applied to the constraint security handler which handles the meat of the servlet api security configuration...that ought to get you going.

cheers,
jesse

--
Jesse McConnell <jesse@xxxxxxxxxxx>
www.webtide.com â Developer advice, services and support from the Jetty & CometD experts.


On Fri, May 31, 2013 at 9:40 AM, Dennis M Fashimpaur <dfashimpaur@xxxxxxxxx> wrote:

Hello All,

I am not writing as an act of begging for help. As a senior developer I understand the need to research and analyze in order to implement an API for some functionality.

I have an application which uses Jetty 6.1.2 in heavily embedded form. It implements adding UserRealms to the server for each login type for each ofÂJDBC, SSO and LDAP authentication. The use of a specific type depends on the software implementation requirements at a client location.

I am currently trying to upgrade to Jetty 8.1.10 as we only support use of JDK1.6 in our apps at this time.Â

I have been working for nearly a week to complete the upgrade. The only holdback/problem I am incurring relates to setting up the login services and implementÂthem within the embedded classes already created.

The problem I find is that all the API documentation I encounter relating to LoginServices, LoginModules, etc. all are examples of using the XML configuration mode and not theÂâembeddedâ flavor that Jetty recommends.

Can anyone recommend any sites or document any of these login services implemented and associated with an embedded server instance?

Best Regards,

Dennis M Fashimpaur

Â

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev


]]> Fri, 31 May 2013 14:57:52 GMT http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01799.html jesse@xxxxxxx (Jesse McConnell) [jetty-dev] (no subject) http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01798.html Hello All, I am not writing as an act of begging for help. As a senior developer I understand the need to research and analyze in order to implement an API for some functionality. I have an application which uses Jetty 6.1.2 in heavily embedded form. It im...

Hello All,

I am not writing as an act of begging for help. As a senior developer I understand the need to research and analyze in order to implement an API for some functionality.

I have an application which uses Jetty 6.1.2 in heavily embedded form. It implements adding UserRealms to the server for each login type for each of JDBC, SSO and LDAP authentication. The use of a specific type depends on the software implementation requirements at a client location.

I am currently trying to upgrade to Jetty 8.1.10 as we only support use of JDK1.6 in our apps at this time. 

I have been working for nearly a week to complete the upgrade.  The only holdback/problem I am incurring relates to setting up the login services and implement them within the embedded classes already created.

The problem I find is that all the API documentation I encounter relating to LoginServices, LoginModules, etc. all are examples of using the XML configuration mode and not the âembeddedâ flavor that Jetty recommends.

Can anyone recommend any sites or document any of these login services implemented and associated with an embedded server instance?

Best Regards,

Dennis M Fashimpaur

 
]]> Fri, 31 May 2013 14:47:50 GMT http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01798.html dfashimpaur@xxxxxxx (Dennis M Fashimpaur) Re: [jetty-dev] Servlet response times http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01797.html _______________________________________________ jetty-dev mailing list jetty-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/jetty-dev _______________________________________________ jetty-dev mailing list jetty-dev@xxxxxxxxxxx https://dev.eclips... Thank alot for replying.

-- We are not using SSL. I am using JRE 1.6. Dont see any problem with the Java app as such. Just spike in jetty response times. In my case i have a java app that has Jetty embedded.
-- I checked GC that was my first guess too. But GC logs are perfect. Around 4 Young scans per minute and each scan taking ~4 ms. Have not seen full GC in days. Also the time stamp of servlet response times spike does not match GC time stamps.







On Thu, May 30, 2013 at 1:58 PM, Jesse McConnell <jesse.mcconnell@xxxxxxxxx> wrote:
Jetty moved to eclipse ages ago, hence this being an eclipse mailing list and all...


And typically those issues are from things like a stop the world garbage collection, so I would start there.

cheers,
jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx


On Thu, May 30, 2013 at 3:53 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
So we are using BlueBox which depends on Jetty 6x. And so i am stuck with Jetty 6x. Can anyone throw some light on the direction i should follow for my investigation ?


On Thu, May 30, 2013 at 1:39 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
I dont see that many releases post 6.1.26



On Thu, May 30, 2013 at 1:34 PM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
Sorry, but you'll find few people to help with Jetty 6.1.26, it is very old and was End of Life'd back in 2010.
There's been well over 150 stable releases of Jetty since Jetty 6.1.26.

Consider upgrading.


--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Developer advice, services and support
from the Jetty & CometD experts


On Thu, May 30, 2013 at 1:26 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
I have enabled Jetty to log response times. I notice that in our production or load test environment, we have a temporary spike in Jetty response times. Jetty logs would trace response times of 200-400ms for a webservice that would normally take 2 ms. I did not notice particular burst of traffic at that time.

Further i traced through servlet debug logs that we have put in our application. And i never found a log that would reflect the servlet processing took more than 3 ms. For every single invocation which Jetty would report response time as 200-400ms, servlet debug logs would only show 2-3ms of processing.

I am guessing that once servlet execution starts it takes only 2-3 seconds. And latency is due latency between receiving of a request to scheduling of request in a sevlet. So i tried to increase threadpool, even though it did not make sense to increase thread pool. As my traffic comes @ 50-100 RPS and if it takes 2-3 ms to process a request 10 default thread count should be enough. But i did increase the thread count to 20 and lowThreadCount to 25. But still saw spike in response times in jetty logs.

Can anyone throw some light or show some path for further investigation ? I am using jetty-6.1.26


Thanks !



_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev



_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev




_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev



_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev


]]> Thu, 30 May 2013 21:32:11 GMT http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01797.html geegalrawat@xxxxxxx (Rawat) Re: [jetty-dev] Servlet response times http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01796.html Hey, i know this is off-topic, but i hadnt heard of that issue. can you give a pointer? _______________________________________________ jetty-dev mailing list jetty-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/jetty-dev Brad,

Back in the days of Jetty 6.x there were a host of SSL exploits and downright silly stupid bugs in the Java VMs related to it.

Using Java 1.6 pre update 30 opens you up to a host of SSL bugs.
Using Java 1.7 pre update 15 also has similar bugs + others around the TLS layer.

In short, if you are using SSL, make sure your JVM is current.
If you don't use SSL, then no worries, you are safe.


--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Developer advice, services and support
from the Jetty & CometD experts


On Thu, May 30, 2013 at 2:06 PM, Brad McEvoy <brad@xxxxxxxxxxxxxxxxxxxx> wrote:
On 31/05/13 09:04, Joakim Erdfelt wrote:
Sure hope you are not running with SSL and have a Java VM released in the past 6 months.
Hey, i know this is off-topic, but i hadnt heard of that issue. can you give a pointer?

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev

]]> Thu, 30 May 2013 21:10:42 GMT http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01796.html joakim@xxxxxxx (Joakim Erdfelt) Re: [jetty-dev] Servlet response times http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01795.html Hey, i know this is off-topic, but i hadnt heard of that issue. can you give a pointer? On 31/05/13 09:04, Joakim Erdfelt wrote:
Sure hope you are not running with SSL and have a Java VM released in the past 6 months.
Hey, i know this is off-topic, but i hadnt heard of that issue. can you give a pointer?

]]> Thu, 30 May 2013 21:06:27 GMT http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01795.html brad@xxxxxxx (Brad McEvoy) Re: [jetty-dev] Servlet response times http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01794.html _______________________________________________ jetty-dev mailing list jetty-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/jetty-dev _______________________________________________ jetty-dev mailing list jetty-dev@xxxxxxxxxxx https://dev.eclipse... You should write to BlueBox and ask them to update the Jetty version they support, as Jetty 6.x has not been kept current to bugs and exploits for the past 3 years.

Sure hope you are not running with SSL and have a Java VM released in the past 6 months.

--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Developer advice, services and support
from the Jetty & CometD experts


On Thu, May 30, 2013 at 1:53 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
So we are using BlueBox which depends on Jetty 6x. And so i am stuck with Jetty 6x. Can anyone throw some light on the direction i should follow for my investigation ?


On Thu, May 30, 2013 at 1:39 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
I dont see that many releases post 6.1.26



On Thu, May 30, 2013 at 1:34 PM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
Sorry, but you'll find few people to help with Jetty 6.1.26, it is very old and was End of Life'd back in 2010.
There's been well over 150 stable releases of Jetty since Jetty 6.1.26.

Consider upgrading.


--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Developer advice, services and support
from the Jetty & CometD experts


On Thu, May 30, 2013 at 1:26 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
I have enabled Jetty to log response times. I notice that in our production or load test environment, we have a temporary spike in Jetty response times. Jetty logs would trace response times of 200-400ms for a webservice that would normally take 2 ms. I did not notice particular burst of traffic at that time.

Further i traced through servlet debug logs that we have put in our application. And i never found a log that would reflect the servlet processing took more than 3 ms. For every single invocation which Jetty would report response time as 200-400ms, servlet debug logs would only show 2-3ms of processing.

I am guessing that once servlet execution starts it takes only 2-3 seconds. And latency is due latency between receiving of a request to scheduling of request in a sevlet. So i tried to increase threadpool, even though it did not make sense to increase thread pool. As my traffic comes @ 50-100 RPS and if it takes 2-3 ms to process a request 10 default thread count should be enough. But i did increase the thread count to 20 and lowThreadCount to 25. But still saw spike in response times in jetty logs.

Can anyone throw some light or show some path for further investigation ? I am using jetty-6.1.26


Thanks !



_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev



_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev




_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev


]]> Thu, 30 May 2013 21:04:22 GMT http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01794.html joakim@xxxxxxx (Joakim Erdfelt) Re: [jetty-dev] Servlet response times http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01793.html _______________________________________________ jetty-dev mailing list jetty-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/jetty-dev _______________________________________________ jetty-dev mailing list jetty-dev@xxxxxxxxxxx https://dev.eclipse... Jetty moved to eclipse ages ago, hence this being an eclipse mailing list and all...

http://central.maven.org/maven2/org/eclipse/jetty/jetty-project/

And typically those issues are from things like a stop the world garbage collection, so I would start there.

cheers,
jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx


On Thu, May 30, 2013 at 3:53 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
So we are using BlueBox which depends on Jetty 6x. And so i am stuck with Jetty 6x. Can anyone throw some light on the direction i should follow for my investigation ?


On Thu, May 30, 2013 at 1:39 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
I dont see that many releases post 6.1.26



On Thu, May 30, 2013 at 1:34 PM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
Sorry, but you'll find few people to help with Jetty 6.1.26, it is very old and was End of Life'd back in 2010.
There's been well over 150 stable releases of Jetty since Jetty 6.1.26.

Consider upgrading.


--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Developer advice, services and support
from the Jetty & CometD experts


On Thu, May 30, 2013 at 1:26 PM, Rawat <geegalrawat@xxxxxxxxx> wrote:
I have enabled Jetty to log response times. I notice that in our production or load test environment, we have a temporary spike in Jetty response times. Jetty logs would trace response times of 200-400ms for a webservice that would normally take 2 ms. I did not notice particular burst of traffic at that time.

Further i traced through servlet debug logs that we have put in our application. And i never found a log that would reflect the servlet processing took more than 3 ms. For every single invocation which Jetty would report response time as 200-400ms, servlet debug logs would only show 2-3ms of processing.

I am guessing that once servlet execution starts it takes only 2-3 seconds. And latency is due latency between receiving of a request to scheduling of request in a sevlet. So i tried to increase threadpool, even though it did not make sense to increase thread pool. As my traffic comes @ 50-100 RPS and if it takes 2-3 ms to process a request 10 default thread count should be enough. But i did increase the thread count to 20 and lowThreadCount to 25. But still saw spike in response times in jetty logs.

Can anyone throw some light or show some path for further investigation ? I am using jetty-6.1.26


Thanks !



_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev



_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev




_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev


]]> Thu, 30 May 2013 20:58:44 GMT http://dev.eclipse.org/mhonarc/lists/jetty-dev/msg01793.html jesse.mcconnell@xxxxxxx (Jesse McConnell)