[
https://issues.apache.org/jira/browse/HADOOP-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley resolved HADOOP-2697.
---------------------------------
Resolution: Fixed
Fix Version/s: hudson
I increased hudson's heap size. File a new issue if you see this again.
> Problems with Hudson
> --------------------
>
> Key: HADOOP-2697
> URL: https://issues.apache.org/jira/browse/HADOOP-2697
> Project: Hadoop Core
> Issue Type: Bug
> Components: build
> Reporter: Jim Kellerman
> Assignee: Nigel Daley
> Fix For: hudson
>
>
> Build 1657 failed after 9 minutes and failed to run the tests
> Build 1656 completed normally (build failed due to findbugs errors)
> When I try to look at the test results for builds 1655 and 1658 I get::
> {code}
> HTTP Status 500 -
> type Exception report
> message
> description The server encountered an internal error () that prevented it
> from fulfilling this request.
> exception
> javax.servlet.ServletException: Servlet execution threw an exception
>
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:52)
>
> hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:28)
>
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55)
>
> org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
>
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55)
>
> org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
>
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55)
>
> hudson.security.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:89)
>
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:55)
>
> hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:44)
> hudson.security.HudsonFilter.doFilter(HudsonFilter.java:69)
> root cause
> java.lang.OutOfMemoryError: Java heap space
> note The full stack trace of the root cause is available in the Apache
> Tomcat/5.5.25 logs.
> Apache Tomcat/5.5.25
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
