Troubleshooting

Email me at blaine.simpson@admc.com if you want me to address any problems.

Tomcat logs are at CATALINA_HOME/logs by default. Exim Webapp logs are at CATALINA_HOME/logs/exim by default. (Exim logging can be fine tuned by editing the log4j config file at CATALINA_HOME/webapps/exim/WEB-INF/classes/log4j.xml. See http://logging.apache.org/log4j/docs/ for instructions on the many things you can do with the logs.

If you prefer old-fashioned "properties" log4j config files instead of the newer xml style, you can replace log4j.xml with your own log4j.properties file.

Deployment fails. One of the Tomcat logs complains about an

invoker servlet. Old versions of Tomcat have the invoker turned on by default. Comment out the <servlet> and <servlet-mapping> elements for invoker in CATALINA_HOME/conf/web.xml and restart Tomcat.

Next time I do a build, I plan to get rid of the dependency on the invoker servlet altogether. This problem will then not occur for anybody.

When I bring up new sub-windows, the old windows go away (or

get lost). The sub-windows right where they were. The problem is, your main browser window gets focus and obscures them. This is a limitation of a simple web front-end simulating a MDI application. I think that this annoyance is much less than the limitations that you have to live with with exiscan.

My recommended workaround is

1. Do not run with with your browser maximized.
2. When you open a sub-window, move it so that a part of it extends beyond the edges of the main browser window. If you want for a specific sub-window to remain completely visible, then move it completely off of the main browser window.
3. Now, whenever you want to see an obscured sub-window, you can click on a visible edge of it to bring it to the foreground.

My web.xml edits get lost every damned time that I re-deploy the war!

The simplest solution is to copy the web.xml file off and restore it to the same place after redeploying (then restart the app). (The Installation section of this doc says where the web.xml resides... I guess you already know where it is if you have this complaint).

If you like Ant, then you can very easily install and build from source. When you build the war from source, your web.xml changes are preserved. Just run "ant" and it will tell you what entries you need to add to the build.xml file. See the Resources section of this doc.

I don't see any Exim Webapp version like you said I should.

The very earliest versions of Exim Webapp didn't advertise their version. If you don't see a version, consider it version 0.

If you just downloaded the war recently and still see no version, then that's my fault-- in the Installation section of this document I neglected to update a link. That link continued to point to a version 0 war until I just noticed it and fixed it. If you're using the Tomcat Web App Manager, it's very easy to undeploy a Web App and then deploy the war again. Don't forget to copy off your web.xml file and restore it (see previous item).

I can log in and view the queue, but when I try to X a message,

the sub-window tells me that the action failed. This is an Exim configuration or permission problem. The exact command that fails is shown inside square brackets (with the arguments separated by commas instead of whitespace). su to the tomcat user and run the same exact command.