hi, I've spent the last couple of weeks migrating our site from webwork 2 to struts 2. The Struts 2 version of the app worked fine on my windows machine, as well as in our qc environment (apache/tomcat 5).
However, when we rolled the code to the production servers, we encountered a rather major problem. s:text calls in the jsp files were randomly failing. You could hit a page several times in a row and all worked, then all of a sudden the s:text tag would fail, and you would see the property keys because the property lookup failed. Refresh the page again, and everything was once again ok. The one main difference in the prod environment, is that the content does NOT live on the same box as the tomcat server. So, i was wondering if the problem might be that the Struts 2 code had occassional problems following linked files? I also thought maybe it was a concurrent access issue, but i hit our qc server with JMeter, and couldnt reproduce the failed s:text problem, so i ruled out the concurrency idea. Has anyone run into issues with Struts 2.0.6 occassionally failing to lookup resources via the s:text tag? Note that the s:text tag calls wrapped inside of the struts i18n tag still worked ok..it only seemed to fail on the plain s:text calls Thanks for any help..i'm pretty much at a loss to explain whats going on, since the same exact code works in test and qc, but not on prod...so thats why i was thinking that the content actually being liked off might be causing a problem (though it does work fine in webwork 2.2) I really want to promote those struts 2 code to production, but if we cant solve this problem, we will have to remain in webwork, and all the migration work i did will be lost. thanks! -jeff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
