Actually , though the site is db-driven, the changes I'm making are as simple as
change: <table width="400"> to: <table width="500"> This is the type of change that is not being reflected. (and yes, I'm triple-sure that this is not a client-side cache issue) > -----Original Message----- > From: Justin Ruthenbeck [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 23, 2003 1:57 PM > To: Tomcat Users List > Subject: RE: JSP not reloading > > > > Are you sure nothing changed on the DB side? Some seemingly inocuous > performance tweak? Do you have some odd rouge connection > holding a lock > on the table(s) you're trying to update and your app is > failing to report > the problem? Stuff like this is almost always something "small" and > almost always user error. Heaven knows I've made my share. ;) > > To isolate the problem, are you absolutely sure nothing is getting > between your code and the conn pool? Have you tried a very simple > version of an update (say a jsp that gets a connection, does > a select, > increments the selected number, and updates) to isolate the > problem to > Tomcat/DBPool? Have you tried hitting the same database from > a different > Tomcat app to see if you can update()? > > I know you want an explanation of what's going on -- sorry, > can't help > you there. I'd put money down that you'll find out it's > something simple > though. > > All I can offer is encouragment and ideas. :) > justin > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
