Skip to main content

Static Variables: Grave Danger

I lost the whole last week on a very small issue. Issue of a kind that would be considered very silly if looked at later. Static variables for holding a Transactional object. This is probably a very naaive concept in Java (or any other language with statics). But mistakes are mistakes. We learn from them everyday. This time, I leart from some one else's. Not the static concept itself, but the sleepless nights it may drive you into for no reason.

The issue started last monday. We were seeing transactional attributes of an object replicated in other objects in the database. An application that stood well in multiple regression tests, load tests, stress tests, failed dramatically in production. To add to confusion, this was happenning exactly at a time where we had a batch job running, a lot of users logging in (of the order 50 logins/ sec), and most of these first time users.

To narrow down our variables, we stopped the batch job. that was in our control. Still There logins, a lot of them. We dint know what the users action was and what was causing it..

(To be continued..)

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

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.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>