WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

WAS Administration: Channel Framework

By WILL DIETZ posted Thu May 16, 2019 12:09 PM

  
As a support team, we find the WebSphere Application Server customers run into common channel framework issues. It is important to understand the cause behind these issues and how to resolve them when they arise.

WAS Channel Framework


Like most technology standards, the internet and the OSI model were partially pieced together by the ISO organization using ideas from previous “home-grown” solutions such as those used in ARPANET, CYCLADES, and other private pre-Internet networks. The OSI model is divided the way it is based on the conflicts from which it arose. With seven different layers, there is a lot of wiggle room for modifying and amending standards as technology evolves. Many of the OSI layer concepts map to their actual implementations in WebSphere Application Server, which we refer to as the Channel Framework.

Timeouts


In the WAS Channel Framework there are four types of timeout: Read, Write, Persist, and Connect. These timeouts indicate that their corresponding I/O operation did not complete in the configured time interval. We will be going over why these occur, what they look like within the WAS log files and how to analyze the logs to determine the root cuase, and how to resolve this type of issue.

Connection Issues with I/O Return Codes


Connection Issues in the Channel Framework often contain I/O Return Codes. Each platform describes the nature of I/O errors through I/O Return Codes. These I/O Return Codes are then received and used by the Channel Framework to handle connection issues. We will go over the why you may see an I/O error, what these look like within the WAS log files and how to analyze the logs to determine the root cause, and the options for resolving this type of error.

Join Us For Our Webinar on June 04, 2019


In this session, we will be talking about problem determination in the channel framework, the must gather information from the channel framework point of view, and the two most common issues we encounter, the timeouts and connection issues. We will conclude with a short trace analysis of both of these issues.


Click here to register!
0 comments
17 views

Permalink