org.glassfish.jersey.servletServletContainer.service() hanging for too long
I was analysing some slow API requests with Dynatrace. I saw this one that took 623 ms and it caught my attention. I was able to see the PurePath of the request and the first thing that happens is org.glassfish.jersey.servletServletContainer.service() spend 590 ms before calling the next method, as can be seen below:
The scenario of the test is like this:
Apache JMeter with 1 thread performing the same request everytime. On the first 100 seconds or so, the average response times is around 5 ms and then suddenly the response time increases and stay high until the end of the test. After the increase in response time, all the requests look like the on in the image. There is a huge hang time (apparently from Jersey).
I'm using the following Jersey/Jersey REST versions:
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-server</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-servlet</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-util</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.core</groupId>
<artifactId>jersey-server</artifactId>
<version>2.22.2</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-servlet-core</artifactId>
<version>2.22.2</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-jetty-http</artifactId>
<version>2.22.2</version>
</dependency>
Is it a documented problem? Have anyone experienced that?
Edit 1:
I was able to reproduce this with Postman.
JMeter is sending Connection: close on the request header. JMeter's Connect time is low and the response time is higher than normal. It doesn't seem to be a problem of opening a new connection on every request.
java jersey
jetty jersey-2.0 dynatrace asked Nov 21 '18 at 18:20
luizfzsluizfzs
65011028
add a comment |
I was analysing some slow API requests with Dynatrace. I saw this one that took 623 ms and it caught my attention. I was able to see the PurePath of the request and the first thing that happens is org.glassfish.jersey.servletServletContainer.service() spend 590 ms before calling the next method, as can be seen below:
The scenario of the test is like this:
Apache JMeter with 1 thread performing the same request everytime. On the first 100 seconds or so, the average response times is around 5 ms and then suddenly the response time increases and stay high until the end of the test. After the increase in response time, all the requests look like the on in the image. There is a huge hang time (apparently from Jersey).
I'm using the following Jersey/Jersey REST versions:
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-server</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-servlet</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-util</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.core</groupId>
<artifactId>jersey-server</artifactId>
<version>2.22.2</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-servlet-core</artifactId>
<version>2.22.2</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-jetty-http</artifactId>
<version>2.22.2</version>
</dependency>
Is it a documented problem? Have anyone experienced that?
Edit 1:
I was able to reproduce this with Postman.
JMeter is sending Connection: close on the request header. JMeter's Connect time is low and the response time is higher than normal. It doesn't seem to be a problem of opening a new connection on every request.
java jersey
jetty jersey-2.0 dynatrace asked Nov 21 '18 at 18:20
luizfzsluizfzs
65011028
As with all things jmeter related, are you opening new HTTP/1.1 persistent connections for each request? (a super common mistake). Are you sending data? (POST/PUT/etc) if so, are you reading all of that data on the server side? What does the Jetty Server Dump tell you?
– Joakim Erdfelt
Nov 21 '18 at 19:10
@JoakimErdfelt added info. I'm not able to see Jetty Server log at the moment. I'll add info if I can access it.
– luizfzs
Nov 21 '18 at 19:25
add a comment |
I was analysing some slow API requests with Dynatrace. I saw this one that took 623 ms and it caught my attention. I was able to see the PurePath of the request and the first thing that happens is org.glassfish.jersey.servletServletContainer.service() spend 590 ms before calling the next method, as can be seen below:
The scenario of the test is like this:
Apache JMeter with 1 thread performing the same request everytime. On the first 100 seconds or so, the average response times is around 5 ms and then suddenly the response time increases and stay high until the end of the test. After the increase in response time, all the requests look like the on in the image. There is a huge hang time (apparently from Jersey).
I'm using the following Jersey/Jersey REST versions:
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-server</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-servlet</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-util</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.core</groupId>
<artifactId>jersey-server</artifactId>
<version>2.22.2</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-servlet-core</artifactId>
<version>2.22.2</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-jetty-http</artifactId>
<version>2.22.2</version>
</dependency>
Is it a documented problem? Have anyone experienced that?
Edit 1:
I was able to reproduce this with Postman.
JMeter is sending Connection: close on the request header. JMeter's Connect time is low and the response time is higher than normal. It doesn't seem to be a problem of opening a new connection on every request.
java jersey
jetty jersey-2.0 dynatrace asked Nov 21 '18 at 18:20
luizfzsluizfzs
65011028
I was analysing some slow API requests with Dynatrace. I saw this one that took 623 ms and it caught my attention. I was able to see the PurePath of the request and the first thing that happens is org.glassfish.jersey.servletServletContainer.service() spend 590 ms before calling the next method, as can be seen below:
The scenario of the test is like this:
Apache JMeter with 1 thread performing the same request everytime. On the first 100 seconds or so, the average response times is around 5 ms and then suddenly the response time increases and stay high until the end of the test. After the increase in response time, all the requests look like the on in the image. There is a huge hang time (apparently from Jersey).
I'm using the following Jersey/Jersey REST versions:
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-server</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-servlet</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-util</artifactId>
<version>9.2.3.v20140905</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.core</groupId>
<artifactId>jersey-server</artifactId>
<version>2.22.2</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-servlet-core</artifactId>
<version>2.22.2</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-jetty-http</artifactId>
<version>2.22.2</version>
</dependency>
Is it a documented problem? Have anyone experienced that?
Edit 1:
I was able to reproduce this with Postman.
JMeter is sending Connection: close on the request header. JMeter's Connect time is low and the response time is higher than normal. It doesn't seem to be a problem of opening a new connection on every request.
java jersey
jetty jersey-2.0 dynatrace java jersey
jetty jersey-2.0 dynatrace asked Nov 21 '18 at 18:20
luizfzsluizfzs
65011028
asked Nov 21 '18 at 18:20
luizfzsluizfzs
65011028
edited Nov 21 '18 at 19:17
luizfzs
asked Nov 21 '18 at 18:20
luizfzsluizfzs
65011028
asked Nov 21 '18 at 18:20
luizfzsluizfzs
65011028
asked Nov 21 '18 at 18:20
luizfzsluizfzs
65011028
65011028
As with all things jmeter related, are you opening new HTTP/1.1 persistent connections for each request? (a super common mistake). Are you sending data? (POST/PUT/etc) if so, are you reading all of that data on the server side? What does the Jetty Server Dump tell you?
– Joakim Erdfelt
Nov 21 '18 at 19:10
@JoakimErdfelt added info. I'm not able to see Jetty Server log at the moment. I'll add info if I can access it.
– luizfzs
Nov 21 '18 at 19:25
add a comment |
As with all things jmeter related, are you opening new HTTP/1.1 persistent connections for each request? (a super common mistake). Are you sending data? (POST/PUT/etc) if so, are you reading all of that data on the server side? What does the Jetty Server Dump tell you?
– Joakim Erdfelt
Nov 21 '18 at 19:10
@JoakimErdfelt added info. I'm not able to see Jetty Server log at the moment. I'll add info if I can access it.
– luizfzs
Nov 21 '18 at 19:25
As with all things jmeter related, are you opening new HTTP/1.1 persistent connections for each request? (a super common mistake). Are you sending data? (POST/PUT/etc) if so, are you reading all of that data on the server side? What does the Jetty Server Dump tell you?
– Joakim Erdfelt
Nov 21 '18 at 19:10
As with all things jmeter related, are you opening new HTTP/1.1 persistent connections for each request? (a super common mistake). Are you sending data? (POST/PUT/etc) if so, are you reading all of that data on the server side? What does the Jetty Server Dump tell you?
– Joakim Erdfelt
Nov 21 '18 at 19:10
@JoakimErdfelt added info. I'm not able to see Jetty Server log at the moment. I'll add info if I can access it.
– luizfzs
Nov 21 '18 at 19:25
@JoakimErdfelt added info. I'm not able to see Jetty Server log at the moment. I'll add info if I can access it.
– luizfzs
Nov 21 '18 at 19:25
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53418314%2forg-glassfish-jersey-servletservletcontainer-service-hanging-for-too-long%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53418314%2forg-glassfish-jersey-servletservletcontainer-service-hanging-for-too-long%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
As with all things jmeter related, are you opening new HTTP/1.1 persistent connections for each request? (a super common mistake). Are you sending data? (POST/PUT/etc) if so, are you reading all of that data on the server side? What does the Jetty Server Dump tell you?
– Joakim Erdfelt
Nov 21 '18 at 19:10
@JoakimErdfelt added info. I'm not able to see Jetty Server log at the moment. I'll add info if I can access it.
– luizfzs
Nov 21 '18 at 19:25