Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 344035

Summary:

long stack trace

Product:

[RT] Jetty

Reporter:

Tore Halset <halset>

Component:

server

Assignee:

Greg Wilkins <gregw>

Status:

RESOLVED INVALID

QA Contact:

Severity:

normal

Priority:

CC:

jetty-inbox

Version:

unspecified

Target Milestone:

7.2.x

Hardware:

Other

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
a very long stack trace	none

Description Tore Halset

2011-04-27 15:36:04 EDT

Build Identifier: jetty-distribution-7.3.0.v20110203

Our jetty is behind a apache httpd using mod_proxy. Some times we observe very high cpu usage with not much traffic. Typically 300-600% cpu. The site is still responsible and usable. Using jstack -l show very strange stack traces. See attached stack trace as an example.

Reproducible: Sometimes

Steps to Reproduce:
have not found a way to reproduce. it happens after the server has been running for some time

Comment 1 Tore Halset

2011-04-27 17:04:45 EDT

Created attachment 194215 [details]
a very long stack trace

Comment 2 Greg Wilkins

2011-05-06 02:00:17 EDT

Wow,

that is quiet a big stack trace!!!!!

but I don't see anything there that suggests that it is a jetty problem.  The issue appears to be with

 com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:346)

which is dispatching again and again and again.    Jetty appears to be handling all those dispatches correctly, so the question is why is faces making all those dispatches.

I suggest raising an issue with the faces project and see what they have to say.  It could well be a jetty issue at the bottom of it, but we will need the faces people to analyse what is happening so they can tell us what the issue is.