> Since your problems occur in the deployed to a clustered > environment, could you accidentally have the redirect="true" > on that action's ActionForwward? Then one of two things could > be happening:
"redirect" is set to "false": <forward name="SeasAdj" path="/content/SeasonalAdj.jsp" redirect="false" /> > 1) You might be redirected to the other server > 2) You might have had the bean in request scope and not > session scope so it would be lost during the HTTP redirect. The bean is certainly in request scope (request.setAttribute("SeasAdjData", sad);). -- Tim Slattery [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]