Skip to main content

Static Variables: The wild goose chase ends here.

(Continued from yesterday..)

So we dint know what was copying the instance attributes to other instances. If it was not the Batch Job, There is definitely a non thread safe code that's doing it. But with so many threads, how easy is it to track down the cause. A wild card search for static would result in a lot of static variables in code.

Thank fully, there was a small market tracking method. This method profiled all the requests. And the data collected was stored in DB. so we were able to look at the requests that were *possibly* causing this. From there it was only a matter of debugging the code.

Unfortunately, We didn't find anything statically referring in our code. but we soon realised it was happening in a (our own) library module that employed its own threading pattern. And there was a STATIC transactional variable. The rest of the story is imaginable. Remove the static reference rebuild the lib and deploy it.

But there are important lessons to be learnt here.

Of all the things, Stop declaring static for transactional variables. static - means static - IT should rarely change!! and by definition *common* in nature. If there is a user account object. It can never be static. even if you are using a HOLDER object, it should not be static. Get a clear picture on that.

And then, Stop using Threads in JEE unless you completely know what you are doing. The main reason threads were used here was that they were trying to implement pooling for connections to Mainframe. A better suggestion would be to employ Connection pools in the container. Stop using your own.

Finally, Keep options to profile your application. Once your application goes into production, you have a totally different picture than that of your Dev. Keeping a way to track the application solves a lot of headache and reduces speculation.

Popular posts from this blog

One page Stock

Alright.. That was a long absence. The whole last week I dint blog. I dint go away. I was "occupied". I was learning stock trading. Its very fascinating. I have a good weeeked blog for you all. Here is my experience. I can literally hyper-link every word from the following paragraphs, but I am writing it as simple as I can so you can look up the italicised words in wikipedia . I got a paper trading account from a brokerage firm . You need one brokerage account first. Then it can be an Equity account where all your money is yours or a Margin account , where some of the money is lent by the brokerage firm. Then I get Buying power , which is the dollor value of how much stocks you can buy. I can make profit by simple rules. Buy when Price is low. Sell when price is high. There is another more intersting way of earning money. Selling short . Thats when price is not high, per say, but when are confident that the price WILL go down. then buy back when its lowest. This is what

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.

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>