This paper describes some of the problems that can be encountered when using the WebSphere Application Server V6 messaging component. Typically, this type of failure would manifest itself as an application that fails to start, an application hang, or an application that fails to receive an expected message. There might or might not be an accompanying error message from the application itself.

Although WebSphere Application Server V6 can use messaging mechanisms familiar to users of WebSphere Application Server V4 and V5 (WebSphere MQ provider and generic message providers), the default messaging provider included with V6 is very different to its predecessors. This paper confines itself to investigating messaging problems that are specific to the default messaging provider that is included with WebSphere Application Server.

This paper applies to WebSphere Application Server V6 for distributed systems only. It does not cover WebSphere Application Server for z/OS.