From: Wolfgang B. (JIRA) <ji...@co...> - 2006-08-08 15:10:17
|
CruiseControl's (V2.5) Jetty collapse on processing big log files in "Test Results View" ---------------------------------------------------------------------------------------- Key: JETTY-94 URL: http://jira.codehaus.org/browse/JETTY-94 Project: Jetty Issue Type: Bug Environment: Windows 2003 Server 2GB RAM, Java1.4.2_09 (Xmx=512m) Reporter: Wolfgang Brodowski 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Wolfgang B. (JIRA) <ji...@co...> - 2006-08-08 15:14:13
|
[ http://jira.codehaus.org/browse/JETTY-94?page=all ] Wolfgang Brodowski updated JETTY-94: ------------------------------------ Attachment: broken view -test results-.jpg > CruiseControl's (V2.5) Jetty collapse on processing big log files in "Test Results View" > ---------------------------------------------------------------------------------------- > > Key: JETTY-94 > URL: http://jira.codehaus.org/browse/JETTY-94 > Project: Jetty > Issue Type: Bug > Environment: Windows 2003 Server 2GB RAM, Java1.4.2_09 (Xmx=512m) > Reporter: Wolfgang Brodowski > Attachments: broken view -test results-.jpg, finished view - test results -.jpg > > > 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Wolfgang B. (JIRA) <ji...@co...> - 2006-08-08 15:14:17
|
[ http://jira.codehaus.org/browse/JETTY-94?page=all ] Wolfgang Brodowski updated JETTY-94: ------------------------------------ Attachment: finished view - test results -.jpg > CruiseControl's (V2.5) Jetty collapse on processing big log files in "Test Results View" > ---------------------------------------------------------------------------------------- > > Key: JETTY-94 > URL: http://jira.codehaus.org/browse/JETTY-94 > Project: Jetty > Issue Type: Bug > Environment: Windows 2003 Server 2GB RAM, Java1.4.2_09 (Xmx=512m) > Reporter: Wolfgang Brodowski > Attachments: broken view -test results-.jpg, finished view - test results -.jpg > > > 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Artem K. (JIRA) <ji...@co...> - 2006-08-08 16:57:12
|
[ http://jira.codehaus.org/browse/JETTY-94?page=comments#action_71864 ] Artem Kozarezov commented on JETTY-94: -------------------------------------- How long the job is running before giving no or broken output? It is possible that connection timeout happens. > CruiseControl's (V2.5) Jetty collapse on processing big log files in "Test Results View" > ---------------------------------------------------------------------------------------- > > Key: JETTY-94 > URL: http://jira.codehaus.org/browse/JETTY-94 > Project: Jetty > Issue Type: Bug > Environment: Windows 2003 Server 2GB RAM, Java1.4.2_09 (Xmx=512m) > Reporter: Wolfgang Brodowski > Attachments: broken view -test results-.jpg, finished view - test results -.jpg > > > 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Tim V. (JIRA) <ji...@co...> - 2006-08-09 14:13:14
|
[ http://jira.codehaus.org/browse/JETTY-94?page=comments#action_71923 ] Tim Vernum commented on JETTY-94: --------------------------------- 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. > CruiseControl's (V2.5) Jetty collapse on processing big log files in "Test Results View" > ---------------------------------------------------------------------------------------- > > Key: JETTY-94 > URL: http://jira.codehaus.org/browse/JETTY-94 > Project: Jetty > Issue Type: Bug > Environment: Windows 2003 Server 2GB RAM, Java1.4.2_09 (Xmx=512m) > Reporter: Wolfgang Brodowski > Attachments: broken view -test results-.jpg, finished view - test results -.jpg > > > 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Artem K. (JIRA) <ji...@co...> - 2006-08-09 18:03:12
|
[ http://jira.codehaus.org/browse/JETTY-94?page=comments#action_71935 ] Artem Kozarezov commented on JETTY-94: -------------------------------------- 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. > CruiseControl's (V2.5) Jetty collapse on processing big log files in "Test Results View" > ---------------------------------------------------------------------------------------- > > Key: JETTY-94 > URL: http://jira.codehaus.org/browse/JETTY-94 > Project: Jetty > Issue Type: Bug > Environment: Windows 2003 Server 2GB RAM, Java1.4.2_09 (Xmx=512m) > Reporter: Wolfgang Brodowski > Attachments: broken view -test results-.jpg, finished view - test results -.jpg > > > 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Jan B. (JIRA) <ji...@co...> - 2006-08-30 09:45:52
|
[ http://jira.codehaus.org/browse/JETTY-94?page=comments#action_73641 ] Jan Bartel commented on JETTY-94: --------------------------------- Does changing the timeout fix this problem? Can this issue be closed now? > CruiseControl's (V2.5) Jetty collapse on processing big log files in "Test Results View" > ---------------------------------------------------------------------------------------- > > Key: JETTY-94 > URL: http://jira.codehaus.org/browse/JETTY-94 > Project: Jetty > Issue Type: Bug > Environment: Windows 2003 Server 2GB RAM, Java1.4.2_09 (Xmx=512m) > Reporter: Wolfgang Brodowski > Attachments: broken view -test results-.jpg, finished view - test results -.jpg > > > 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
From: Jan B. (JIRA) <ji...@co...> - 2006-09-15 13:23:13
|
[ http://jira.codehaus.org/browse/JETTY-94?page=all ] Jan Bartel closed JETTY-94. --------------------------- Resolution: Won't Fix Closing this issue as no-one has responded negatively to the request to close it. > CruiseControl's (V2.5) Jetty collapse on processing big log files in "Test Results View" > ---------------------------------------------------------------------------------------- > > Key: JETTY-94 > URL: http://jira.codehaus.org/browse/JETTY-94 > Project: Jetty > Issue Type: Bug > Environment: Windows 2003 Server 2GB RAM, Java1.4.2_09 (Xmx=512m) > Reporter: Wolfgang Brodowski > Attachments: broken view -test results-.jpg, finished view - test results -.jpg > > > 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |