Clear JBoss Cache The TeamSite Way

Can anyone (ok, rpoulin will probably beat everyone to it :-) ) tell me the "best" way to clear the JBoss cache using TeamSite tools, iwreset -a perhaps? Does bouncing the JBoss server clear the cache? Doesn't look like it based on what I'm seeing. Thanks.

Find more posts tagged with

Comments

Rick Poulin

Now, now.. what are you implying? Smiley Tongue

Depends on what cache you're talking about. What artifacts are you looking to 'refresh'?

PS. iwreset is almost by definition never the fastest way to do anything because it restarts absolutely everything to do with the UI. There's always a faster way for specific use cases, unless you've made a bunch of changes to multiple facets of the app.

JRomeo

Implying? Me, nothing. I'm not lookin' a gift horse in the mouth. I overwrote one of the base widget JSPs, /iw-cc.war/base/widget/tabs/tabset_renderer.jsp to be exact. I ran iwreset -a but no change occurred. I still saw the same output of the overwritten file.

I then used a text editor to make a simple whitespace change to the file, reloaded the page and the file worked as expected.

I believe JBoss had this JSP cached, and did not check for new content until I made a change and saved it. There has to be a scripted way to clear this kind of cache or otherwise manage the file checking behavior. JBoss surely has a way to do it, but I'll wager there's a method or two that might be better, more TeamSitey, if you please.

Rick Poulin

Gotcha. Yes, most app containers cache the compiled version of a JSP and don't usually recompile it unless the file size and/or moddate changes. You can manually clear this cache by locating the corresponding files under the AppContainer/server/default/(deploy/)?work folder.. in this case, yours would be in a sublocation that is something like work/iw-cc.war/org/apache.jspc/base/widget/tabs/tabset_renderer005something.class (saying this from memory so it's probably not 100% accurate). Delete these files and the next time you access the JSP it'll get recompiled -- no JBoss restart necessary.