I’ve had more or less the same sort of challenges with a SISCweb based site I’m running too (http://www.tenspotting.com). Tomcat is awfully hungry for memory. Though SISCweb is just too cool and powerful to pass up using.

I often like to run two instances of my app, one for development purposes and one for production. I suppose using the hack you just came up with, I can save myself a tomcat instance and run them off the same instance.

Thanks! And I’d love to hear more about suggestions you have for optimizing Tomcat + SISCweb.

-Ben