[msharma@objectgain.com]

I can debug the JSPs fine withe weblogic 8.1. However, everytime I put a break point on a JSP, I have to redploy for the server to stop a the break point. I do not need to redeploy for Java code though. Is there something I can do so that it does not require me to redeploy when I put a breakpoint in the JSPs ?

Thanks

[Riyad Kalla]

That’s very strange… is this only when debugging JSPs that haven’t been debugged already? For example, if you debug foo.jsp, then remove the break point, then add one back, does it still work? I think this might be a sign that you are running off of a cache of JSP pages that were compiled *without* debugging information in them and redeploying is forcing the app server to rebuild those JSPs now with debugging information (did you check our FAQ and set that debug flag in the server settings?)

[moreinforequired]

Thanks for the reply. Yes, once the the JSP has been debugged, then after that I can add or remove breakpoints at will. It is only the new JSPs (or JSPs being debugged for the first time) that have issues. And yes, I do have all the correct flags set, otherwise it would not even let me debug.

So probably it is the cache. Is there any way to clean the cache and restart the server ?

Thansks

[Riyad Kalla]

I’m not sure exactly where WEblogic keep’s its compiled files, on Tomcat there is a /work directory where it keeps them. Is there a temp dir somewhere under the weblogic install dir?

[Author]

Posts