We've been using gwt-log for a while, we love it! However, we've never had success w/ server-side stack trace deobfuscation. Finally I decided to dig into this issue. I found that the -deploy on compile wasn't getting the job done anymore, adding -extra did generate the symbolMaps folders. So, I deployed to my local OC4J server in script mode and was still not getting detailed stacks. So, on Fred Saur's advice I ran stepped through StackTraceDeobfuscator.class - which turned out to not be finding the symbolMap files. It was looking in the wrong folder. So, we run the app from our Eclipse project under ".../workspace/my_project/war". However, I found that StackTraceDeobfuscator was looking under /j2ee/home/my_project/WEB-INF/ deploy/my_module/symbolMaps/...". Then I deployed to one of our servers to see if it was just due to our funky path difference...there I found it still looked under "../j2ee/home/WEB-INF/...", where it should be looking under "../j2ee/my_container/my_project/WEB- INF/...". Is there a different way I could pass my parameter, or do I need to override the StackTraceDeobfuscator class?
Thanks to anyone who has any ideas. We are getting a lot of client- side stack traces right now as well as having to restart our production servers frequently - I know there is an issue in my code somewhere - but I need these stack traces to help me find it! -- You received this message because you are subscribed to the Google Groups "gwt-log" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gwt-log?hl=en.
