todd_farmer,
I had the same problem before. I had to clean up everything as you did :)
good one:)
Cheers!
Acton
Main Topics
Browse All TopicsHi,
I am using JRun 4 (updater 3) and am encountering a problem with JRun apparently caching deployed code. I updated a SQL statement declared as a static String and redeployed the web application. It immediately failed because the SQL string was incorrect (it lacked a closing parenthesis). I corrected the SQL string, recompiled the WAR and redeployed, but it failed again. When I look at the logs, I see that JRun is still using the incorrect SQL string. I've now redeployed several times over, with the same results. Here's what I have done so far:
1. Redeployed the .WAR file.
2. Restarted the server.
3. Restarted JRun.
4. Deleted the folders under SERVER-INF where the web app was deployed.
5. Rebooted the machine.
6. Opened the compiled .class files to validate that the string was correct in the deployed app (it was.).
I've tried pretty much all of these options in various combinations, and nothing is working. Somehow, JRun is obtaining the bad SQL string, even though the deployed code is correct.
Any ideas what I need to do to make JRun recognize the changes that have been made?
Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: todd_farmerPosted on 2005-09-30 at 10:12:36ID: 14994145
Never mind, I figured it out. Turns out that it was a compilation issue, not a JRun issue. The SQL string was declared as a final static variable, and apparently the compiler optimized the calling classes by including the string in those classes directly. When I changed the String value in the final static variable, but did not change the calling classes, they were not recompiled and retained the old SQL. Time to update my ANT script to clean the build directory before every build.