Jetty

100% of CPU used in WebSocketConnection.handle()

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 7.1.6
  • Fix Version/s: None
  • Component/s: Servlet
  • Labels:
    None
  • Environment:
    Sun Solaris 11. Jetty 7.1.6.
  • Number of attachments :
    0

Description

I'm using WebSockets in production. Over time threads will start to hang in the following place:

WebSocketConnection.handle() line: 168
SelectChannelEndPoint.run() line: 506
QueuedThreadPool$2.run() line: 436
Thread.run() line: 619

A new thread hangs about once a day and after I few days I'm forced to restart my server.
Please let me know if there's any other info I can provide to help diagnose this bug!

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. JETTY-1391 Apparent Race Hazard / Flushing Problem In Websockets

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

No work has yet been logged on this issue.

People

  • Assignee:
    Greg Wilkins
    Reporter:
    Andrew Lee
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: