Chapter 9 Managing a Production Emergency

Do you sometimes feel that your WebSphere team is guilty until proven innocent? Do you sometimes feel that people wrongfully blame the WebSphere team for production issues? If you feel this way, you may be right. Many serious system and application issues can first manifest themselves as WebSphere system anomalies, even though for the majority of the cases, you can eventually prove that the WebSphere system is not the root cause of the problem. For example, a corrupted database table may cause Java Database Connectivity (JDBC) connection pool saturation. An application code defect that jams a huge number of large objects into the memory may express itself as Java Virtual Machine (JVM) garbage collection ...

Get WebSphere Engineering: A Practical Guide for WebSphere Support Managers and Senior Consultants now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.