Jetty

CruiseControl's (V2.5) Jetty collapse on processing big log files in "Test Results View"

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    Windows 2003 Server 2GB RAM, Java1.4.2_09 (Xmx=512m)
  • Number of attachments :
    2

Description

Having big logfiles (2MB and up) from a cruisecontrol job which have many fails in there junit test part lets the conversion to html stop either with no output or normally after an refresh a broken output in a textual style (not html). Seems to be an "out of memory" problem of the vm, but setting memory to a higher value (i.e. 1024M) does not help. Smaller files (i.e. 512k) are no problem for the process

I've no idea, what todo besides giving more (and more) memory to the engine, Maybe the memory isn't the problem, but the process must be configured to get work for all file sizes

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. JETTY-93 SelectChannelConnector much to slow in windows

  • Critical - Crashes, loss of data, severe memory leak.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Artem Kozarezov added a comment -

How long the job is running before giving no or broken output? It is possible that connection timeout happens.

Show
Artem Kozarezov added a comment - How long the job is running before giving no or broken output? It is possible that connection timeout happens.
Hide
Permalink
Tim Vernum added a comment -

Last time I looked a CruiseControl it was XSLT based and really slow to render.
It wouldn't surprise me if it's a timeout problem.

Show
Tim Vernum added a comment - Last time I looked a CruiseControl it was XSLT based and really slow to render. It wouldn't surprise me if it's a timeout problem.
Hide
Permalink
Artem Kozarezov added a comment -

Currently the MaxIdleTime parameter of the Connector is the only way to control timeouts in Jetty.
You should try to increase it to 60000 or more.

Show
Artem Kozarezov added a comment - Currently the MaxIdleTime parameter of the Connector is the only way to control timeouts in Jetty. You should try to increase it to 60000 or more.
Hide
Permalink
Greg Wilkins added a comment -

May be related to JETTY-93 if you are running a windows server?

Show
Greg Wilkins added a comment - May be related to JETTY-93 if you are running a windows server?
Hide
Permalink
Jan Bartel added a comment -

Does changing the timeout fix this problem? Can this issue be closed now?

Show
Jan Bartel added a comment - Does changing the timeout fix this problem? Can this issue be closed now?
Hide
Permalink
Jan Bartel added a comment -

Closing this issue as no-one has responded negatively to the request to close it.

Show
Jan Bartel added a comment - Closing this issue as no-one has responded negatively to the request to close it.

People

  • Assignee:
    Unassigned
    Reporter:
    Wolfgang Brodowski
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: