I'm migrating an enterprise application which has Websphere server 5.1 as the base server to WAS 6.1. After deploying the ear file in new WAS6.1, I can't login to web-application. When I invoke the Login Action class, screen displays with few html open tags. After debugging I found that issue happens in one of the four custom filters. So when the request passes through the four filters everything is ok but when response is send back and it reaches the second filter it produces an error saying 'Response already committed: cannot forward response'. Whole code including filter implementation was working fine in WAS5.1, so I think there is no need for change in filter implementation. Does any one knows any custom property to resolve this issue ?