Tag: jrebel

Posted on

JRebel 5.0 – 5.1

I was on the verge of doing a new write up but due to work I couldn’t get very far. I had compiled some text into a file and here it is:

In JRebel 5.0 I noticed some stuff.

It seems that JPA NamedQueries are not changed on reload. It is not certain that this is supported, about that unsure I am.
Spring 3.1 MVC Controllers are not reloaded (Luckily there is always the nightly build of JRebel and it fixed that when I was using 5.0!)
Another thing I noticed is that Spring Reloadable Message bundle new properties are not reloaded
And then the good stuff! better IDE integration, easier single click activation of JRebel for multiple projects thanks to the JRebel Config Center making a developers life much much more comfortable. Almost all latest Java Frameworks are supported!

JRebel 5.1

At work I’m making an app called ECW it’s not that big, only 11k lines of code. But I got some stats, and remarks by that statistics.

Tomcat Startup times:
ECW no JRebel = INFO: Server startup in 6255 ms
ECW with JRebel = INFO: Server startup in 13420 ms

Of course the doubled startup time is is neglectable! Why? You almost don’t have to restart tomcat the whole day!

an issue I had an fixed was:
Java 7 and Java 6 mixed … Not working. By default JRebel seems to be using Java Version of eclipse, instead of the version used for project/compilation/running tomcat, setting JAVA_HOME to java6 and still using -vm jdk7 to run eclipse , fixed the issue. This is probably documented in the documentation but I didn’t see it come up in the google search 🙂

And then some more stats:

JRebel 5.1.0 (201210161346)
[2012-11-27 21:57:38] (c) Copyright ZeroTurnaround OU, Estonia, Tartu.
[2012-11-27 21:57:38]
[2012-11-27 21:57:38] Over the last 30 days JRebel prevented
[2012-11-27 21:57:38] at least 193 redeploys/restarts saving you about 2.4 hours.
[2012-11-27 21:57:38]
[2012-11-27 21:57:38] Over the last 84 days JRebel prevented
[2012-11-27 21:57:38] at least 577 redeploys/restarts saving you about 7.1 hours.

Stats are always fun! What can ZeroTurnaround do to make them more fun?
Add a total time a server was running with JRebel. And perhaps the total deploys that happened during that time. Instead of just notifying the time saved. In the case of the above stats 2.4 hours seems very little, and 7.1 hours over 84 days, maybe even less. IMHO the stats would say much more if the total manual deploys are visible too.
Something like:
[2012-11-27 21:57:38] Over the last 84 days JRebel prevented
[2012-11-27 21:57:38] at least 577 redeploys/restarts saving you about 7.1 hours.
You had 168 (taking about 3.7 hours) manual deployments over a total running time of 240h.

You can do the math yourself from the above stats. Suppose that I had to manually deploy those 577 everytime. I would have lost 1 day in 240h ( 30days).

Points where JRebel could improve. If technically possible.

Deploy new classes, and a whole class tree (e.g. when a superclass changed), add new properties that are added in properties files. (Disclaimer: perhaps JRebel can do all that and is illconfigured at my side)

What did I conclude from using JRebel the last 3 months?

  • the bigger the app the more useful it gets!
  • if I disable it for a day I have to go to a rehab center
  • stats can be more irie
  • I love zeroturnaround, but it’s to far from home to even consider sending them my resumé

Note: Now that they made LiveRebel free for 2 servers it is time to try it! (and buy it for all your servers)

 

Disclaimer: I do not work for ZeroTurnaround, neither am I affiliated to them in any way!

Posted on

JRebel 5.0

Yeah JRebel 5 is there.

If you work with Eclipse the first thing you notice is the improved integration. You no longer manually have to generate the rebel.xml file. Activating the rebel on a project only requires 1 click, saving you more time to code. Not that much more but it’s much more convenient and easier to deploy.

Also the remote and livedeploy integration seems really improved. I regret that I can’t really use it at the moment to test it out. At my current employer they stick to old school building.

I even have trouble to convince the developers to try out JRebel, 2 tried it, then got back to waiting on deployments and restarts don’t know why. Although it’s currently saving me between 11 to 15h each 30 days. Maybe I’m more nerd/geek than them, way more.

Every developer should give it a try!

Posted on

3 months of JRebel

Found this post in draft status. Seemed to have forgotten to publish it. Here it goes.

I’ve used JRebel for 3 months. The demo license has come to an end in January and I’m already missing it.

In 3 months time JRebel saved my about 3 days, that is a day a month. Now I must confess, I haven’t had to start up webapps for at least one month and another month was 3 weeks of holidays . So these stats actually count for only a month and a half, which makes them even look better!

Currently I’m without JRebel, restarting the jersey/spring web applications every 2 deploys. I’m trying to advertise the usage of JRebel a bit, but with the crisis it seems there is no money. If I only was a manager …

Why should you use JRebel? That has been summed up before see here and here

Wouldn’t everyone want a tool like that?

I would like to see LiveRebel in action where I work now, but don’t think the workplace wants it 🙁

note: I’m not affiliated with zeroturnaround in any way!