Hi, I am facing a strange issue with WAS 3.5.4 on AIX. We have some log statements in the JSPat the beginning, and the end, to track the performance. The first time we hit the JSP, the log statements print the name of the resultant Java class from the JSP(For ex: _a_jsp for a.jsp). The second time we hit it however, it takes almost two minutes to print the first log statement at the beginning of the JSP, and the statement prints _jspService(_a_jsp) as the class name. While the class name itself should be of no concern, the time lag of two minutes is vital to our performance. The subsequent requests show the class name as _jspService(_a_jsp), but we do not see the time lag. Again, if it happens only for the second time, we can live with it. But, what if this appears more often? That will deteriorate our application's performance. Has any one seen this? It almost looks like after the first compilation, WebSphere is creating a separate class with _jspService(_jspname), and that's the reason it takes 2 minutes to log the first statement? Another interesting observation is, the page execution time remains constant through out the process, and that this happens only in a few pages. I've gone thru some redbooks for WebSphere, but didn't find any thing related to this. Any help in this matter will be highly appreciated. Thanks in Advance. -Bala.