-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Running on Solaris 10 (sparc). Tomcat 6.0.29. Jenkins 401 and 404. This was not an issue in Hudson 380. JVM is set to 1.5GB on one system and 2GB on another.
Run a build that generates a large console output. Say around 10MB or more. View the console log for the build. It should work just fine. Add the timestamper and run the build again (version 0.6). View the console log. Select to view full log. This frequently crashes Jenkins/Tomcat. Sometimes I actually get the whole log. This has occurred after a restart as well as after it has been running for a bit. I don't see the issue when view logs without the timestamper enabled (at least not yet).
Irrespective of whether the timestamper plugin is causing jenkins to use too much memory the error in the log is that the operating system has run out of memory to give to Jenkins
You need to ensure that your operating system has enough physical memory (or swap space) to allocate the memory that you have told Java it can use.