Skip to main content

ReplayDirector - Something on my radar

On my Job as a J2EE consultant, I have encountered situations where I am unable to reproduce a problem QA encountered. For one, it may be a really hard-to-reproduce or not-realistically-probable situation in a normal user interaction and just that QA stumbled on it. Or it could be a piss port job by QA that they just broke it, no idea how - but the user might have higher probability of reaching that state. Either way, My job as a developer is to see that NO probabilistic known scenario should break my application. So here is one scenario I know the system is broken but I don't know how to fix it, because I just know the problem not its cause. Its a very challenging albeit annoying situation. I find myself very energetic in the beginning but as time passes without being able to find the cause, I get stressed.

I guess many of you in the business, have had this situation some or the other time. Here is where recording the whole state of jvm comes into picture. ReplaySolutions has an innovative product that does something like that. It records all the activity (Even in a JEE with multi-tier stack) and records them as isolated sessions. This is (their caption) Tivo for Java programs. These Isolated sessions are completely replay able, independent of the dependencies. By Idea, this should eliminate all those variables and give you exactly all the state which caused the bug to occur. I haven't seen this in action my self (I am yet to be invited on their beta program). But They have a demo posted on Eclipse live, if you are interested to catch it in action. There are some important features like being able to capture the screens, submit a session directly as a Bug etc. They claim this is a light weight Byte analysing agent that binds itself to the JVM. I just have to wait and see how this all gels in. May be some day, I dont have to go through all that stress of - "O come on man, How the heck did QA get this - let me just mark it unreproducible".

Leave comments in Guestbook

Popular posts from this blog

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

Using Equinox CommandProvider to make OSGi console interactive.

After fiddling with the First Bundles that "Hello World"-ed upon Activation, You want to see more interactivity in OSGi. Although Using OSGi for an interactive Command Line Application would be like this one would be, well, a callable over-kill, I am going to start with an example and Expand it in later posts. So, please Welcome CommandProvider. CommandProvider is an EQUINOX specific API for extending the Console. This basic Example illustrates how to get a command from console and do something in java and also gets your feet wet on Service Registry package com.so.examples.commandconsole; import org. eclipse .osgi.framework.console .CommandInterpreter; import org.eclipse.osgi.framework.console.CommandProvider; public class DisplayMessageCommand implements CommandProvider { public void _say(CommandInterpreter ci) { ci.print("You said:" + ci.nextArgument()); } @Override public String getHelp() { return "\tsay - repeats what you say\n"; } }

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour