For the past couple of days, I have been trying to deploy the web services I have written. It was a lot harder than I ever imagined. I had configured everything and it was running fine in my local setup. I took my time and made the perfect deployment plan. It was supposed to be just a matter of updating the context followed by a restart of the application server. Needless to say, it was nowhere near that!
It is a matter of great discomfort when you are deploying a set of new configurations, which works perfectly in your local box, refuse to work in the live server. To make matter worse, the error doesn’t give any clear indication and the log file behaves like just another day in the office!
Fortunately though, the air has cooled down, all the issues are resolved now at the expense of couple of days of frustration and head scratching debugging.
My collegue yesterday noticed I was unusually quite (even for my standard) and wondered whether this sort of problematic patch is frequent in programming. Frequent or not, the aftermath is surely worth it and more. 
# The likelihood of problems occurring is inversely proportional to the amount of time remaining before the deadline.
# You will always discover errors in your work after you have printed/submitted it.
I had to churn through Murphy’s law site to find the most appropriate thing to comment..
May be you should have also written what was wrong and how you fixed it.
Does it really matter?
Well maybe next time..