2013년 3월 26일 화요일

[TechNote] The behavior of servlet init processing differs between WAS7.0 and WAS8.0

The behavior of servlet init processing differs between WAS7.0 and WAS8.0

Technote (troubleshooting)

Problem(Abstract)

The behavior of servlet init processing differs between WAS7.0 and WAS8.0

Symptom

Error in init() method of servlet handled differently in WebSphere Application Server version 7 and 8.

Cause

WebSphere version 7 behavior:
In WebSphere version 7, if the init() method or servlet gets into an exception, webcontainer will mark that servlet unavailable for life of that jvm process.

WebSphere version 8 behavior:
In WebSphere Version 8, if the init() method of servlet gets into an exception, servlet is not initialized and webcontainer will NOT mark it unavailable permanently. On subsequent request of that servlet, webcontainer will it try again second time. If exception occurs again (second time) in init() method, webcontainer will now mark that servlet unavailable for like of that jvm process.

Explanation:
There is no change in servlet specification in this area. WebSphere Versoin 8 is designed to be more flexible than WebSphere Version 7 around this area of servlet specification

댓글 없음:

댓글 쓰기