Happy Birthday, Jenkins!

[Harald Wellmann]

hwellmann@handel:~$ ssh ci.ops4j.org
hwellmann@pumpkincay:~$ uptime
17:11:57 up 365 days, 19:02, 1 user, load average: 0.04, 0.07, 0.13

Now that's what I call Continuous :-)

Cheers,
Harald

[Niclas Hedhman]

The now downed srv07, served most of ops4j for a long time, had an uptime well over 1000 days before it was finally shut down in Jan 2012. Part of that was due to a mistake earlier, where I/we thought that it would not recover from a boot, due to corruption of apt database and other configuration. ;-)

Cheers

Niclas

--
You received this message because you are subscribed to the Google Groups "OPS4J Infrastructure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ops4j-infra+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Niclas Hedhman, Software Developer
河南南路555弄15号1901室。
http://www.qi4j.org - New Energy for Java

I live here; http://tinyurl.com/3xugrbk
I work here; http://tinyurl.com/6a2pl4j
I relax here; http://tinyurl.com/2cgsug

[Toni Menzel]

True ;)

Still i used to celebrate birthdays even though there are people older than me .. *g*

1000 days would be a good milestone for the new server. Also interesting would be jvm uptime. But without proper class reloading in jenkins for plugin upgrades this will never be great i suspect.

Merry Chrismas guys! Yes.. late. 

Toni Menzel | rebaze GmbH

toni....@rebaze.com | +49 171 65 202 84

http://www.rebaze.com | twitter @rebazeio | LinkedIn Profile

To unsubscribe from this group and stop receiving emails from it, send an email to ops4j-infra...@googlegroups.com.

[Niclas Hedhman]

he he he --- Good Point.

Well, unfortunately there are too much memory leaks in too many libraries and it is a problem that few people bother much about, since no one expect the JVM to survive very long.

Back in 1999, I was chasing a <1000 bytes/day leak in my industrial control system, because I had the target of multi-year running of that system without restarts. I eventually found that, and the longest running JVM (JDK 1.1.7 I think it was) that I know of reached nearly 5 years. That wouldn't be possible today. In those days, I had a 32MB RAM computer, running Linux, Apache, Postgresql and 2 JVMs. Tried to squeeze in a desktop and Netscape on top of that, but that required an extra 32MB. Times have truly changed.

Since the JVM itself had a serious memory leak a few years later (I think it was 1.3), where StringBuffer instances weren't collected if they had a length > 0 and more than 1 (dead) reference to it, makes me think that it is likely that the highly complex JVM of today is probably also leaking over long periods of time. Java 8's JVM is a sign that PermGen space is a problem in earlier versions, but it wouldn't surprise me if there are a lot of much smaller leaks, which in GB sized memories simply isn't seen over days, but add up over years.

Happy New Year, everyone...

Niclas