Wednesday, July 30, 2008

Finding and resolving Axis2/C realted issues

While working with Axis2/C and related projects for last couple years following are some steps to follow in order as a developer when you encounter something not working as expected..

1. Capture the messages using a tool like TCPMON and check.
2. Check the log and see whether there are log messages as errors.
3. If it crashes, run in the debug mode and check the back trace.
4. If the back trace is not giving enough information then debug the suspected code segments
5. Run through a memory profiling tool like valgrind or purify and check for following,
- Invalid frees
- Invalid Writes
- Invalid Reads

6. If you have to debug in a loop or in a threaded environment try putting additional printfs and log messages to capture the culprit.

7. If none of this help then get the support from some other developer or put a mail describing the problem to the mailing list

No comments: