Discussion Locked

Best way to debug an application in production?

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi
We have had a new installation of a client server application installed in one of our branch offices (not this one). The users complain that this application keeps locking up (freezing) at random times. I cannot reproduce the problem at this end and the installers/vendor cannot either. I have seen the 'lockup' many times after users have asked me to login but cannot get it to do it myself.

I have done all the usual things such as error log gathering from client and server ends and filemon but nothing is shown in the logs.

I had thought of recording the screen movements for a day on one of the problem PC's but all screen capture utils seem to produce monster AVI files or similar and are not suitable for long periods of recording.

Does anyone have any ideas on how to successfully debug this app (maybe using a combination of utils)?

This has been ongoing since Oct 2008 so i'm being pressured into finding an answer.

Thanks

8 replies

by tony hopkinson

Log4Net or log4J might be the way to go.

If not knocking up a simplified version might be the way to go.

You need more clues. One ove the above can be used to create a log file. best of all you can configure levels of logging from within the app, put it in production code and turn it on/off with a config file.

Course some poor git has to go put it in, but it's a damn useful debugging assist and with a bit more work you can do some performance stuff as well, by banging start and stop messages with a tick time in the log.

When attempting to replicate, have you considered their A/V setup. We've had occasionally funnies on that.

by chris

Hi Tony

I have no control over the actual software, so can't create a simplified version.

It was installed by a third party but not written by them. Software is EAS (Exchange Archiving System). Problem is with the Outlook Addin which enables searching of the archives held on the server. I guess broadly speaking it could be any software really. Trouble is its impossible to predict when it will happen. It could happen 6 times a day and nothing for 1 week then another 2 times in a day.

I will look into both utils you suggested.

Thanks

by chris

Hi Tony
Just looked at the logging utils you suggested. They won't work in this case as it's not a web based application.

Thanks anyway.

by tony hopkinson

Isn't web specific, but if you don't have access to the code, you are stuffed anyway.

It's just a dll, you reference, create an instance, set the properties and then call the methods.

So you can use it from any environemnt capable of instancing a .net component.

Haven't used Log4J, but it should be the same idea.

From the sound of it I think you are going to have to get lucky, been there, it can be a long wait.

by chris

Hi Tony
Yeah. been waiting since Oct for a glimmer of hope as to what it could be!

What about screen recording. If I could work out if there is something the user was doing before each crash. That was my other option but i can't seem to find anything that will record over long periods of time i.e. an 8 hour day.

by tony hopkinson

Analayse and restart very x hours, or at a fault maybe? Asking alot of your clients though.

Short of something glaringly obvious, like clippy ambling across the desktop on every fail, I'm a bit dubious.

You could try old faithful
Change something, say the location of the archive. We could be talking something really horrible here, like an intermittent collision between various requests. Just as a thought have you checked the files for corruption?

Hmmm, some sort of testbed and load testing might get you somewhere. Give it a right good hammering, see if it breaks.

by chris

Hi Tony
Thanks for reply.
Users won't want to stop/restart recording software. I did think about setting a tripod and video camera over the shoulder of one of the users. That would also cover both monitors that they use and run for many hours???

Trouble is with load testing is that the vendor and installer have all but given up on this and if you know EAS you'll know how complicated it is...lot of SQL tables, SP's etc. I'm not qualified to setup anything like this with EAS and wouldn't want to on the production setup.

On the corruption. Yes i can checked for corrupt files and installed and re-installed countless times with different versions etc.

The issue is defo a client issue in my opinion so moving the archive would be a little drastic - it's currently 0.5TB in size so don't fancy doing that anyway! Again...it's not that easy within EAS and not for me to tackle myself.

This discussion is closed to new replies.