12.07.2005 ~ '80004005'
« February 2012 »
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29Tags
- .50
- 02
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 80s
- aircraft
- airsoft
- amiga
- amusing
- ArmA
- army
- arse
- babylon5
- backpage
- battlestar
- bebo
- caprica
- casa
- cat
- chinaDoll
- ciws
- clonmel
- code
- coen
- college
- computers
- cti
- custom
- Damn useful
- dev
- dez
- disappointing
- dublin
- fecking
- ffs
- frontpages
- funny
- gallery
- games
- google 12
- graffitti
- guard
- guns
- handy
- history
- I_don't_like_u
- iPad
- iPhone
- jfk
- karma
- landrover
- life
- lost
- love
- madonna/whore
- maritime
- meteor
- microsoft
- military
- mkiscript
- movie
- movies
- musing
- narc
- oh_its_you
- oldDaze
- pach
- pegasus
- phishing
- phone
- piltown
- podcasting
- police
- pussy
- quote
- rant
- religion
- retro
- right/wrong
- RIP
- Schrodinger
- ships
- simpsons
- sms
- software
- something
- song
- southpark
- spam
- spoiler
- struggle
- time_and_tide
- tv
- twilight
- ui
- unusual
- war
- weapon
- web2.0
- webdev
- weird
- what
- who
- windows
- women
- work
- wow
- writing
- xda
On Twitter
wtfF0nzie: RT @eircom: Technology Career Opportunities #eircom are looking for "skilled specialists with expertise in a variety of areas" - http:// ...
Fri, 03 Feb 2012 16:17:03
It isn't very often that I'm led so drastically off the desired path by a search engine. Two examples that I'm not going to detail come to mind, but this one is new!
Imagine the scenario:
A vague error message in a well established scripting language. The first natural response? Hit the documentation! Nothing. The error is intermittent, has something to do with an application variable being emptied and only occurs after the first day or so of uptime. Hit the search engines! A collection of database and dictionary object related fixes are returned - the term application is considered to be web application not the application object.. The code:
application(item) = ""
For the record the item var has a value! The results offered by google and clusty don't help at all (I did a series of refined searches that yielded the same results!). So I consider the problem:
- It is intermittent - not consistent (having checking across browser, platform, time of day, striped or chequer underwear).
- The site is on a shared hosting plan.
- In dedicated environments over the past three years under high workload the issue didn't present itself.
The Solution:
A shot of jack daniels! No really! Exception handling is basic but effective in asp. Jack thought me that many years ago, he reminded me today. Some additional error handling helped identify a small related issue on the front-end - and in the space of seconds one of the most annoying bugs I've ever crossed is quashed . I love you Jack =x
The moral?
Virtual hosting can be good for measuring performance problems - this was a bug stress testing never exposed. And keep your variable names short kids. And never run with scissors!