Multiple Mid-Tier, single Tomcat

I did this years ago, and can confirm that it worked in 7.6.04, but I'm trying it again in 8.1 and it's not working. In previous versions, if you created a second context of Mid-Tier, Tomcat would complain about native dll's being already loaded, and you needed to separate them out so that the

Multiple Mid-Tier, single Tomcat

LJ, Perfectly valid but I don't think it's going to be the best way to deploy Mid Tier. The biggest issue with Mid Tier, the issue that hasn't been correctly addressed in the last 8 years, is the poor memory consumption and cache performance. As such, multiple Mid Tiers means multiple sets of

Re: Multiple Mid-Tier, single Tomcat

I agree that it's not ideal, nor is it recommended by BMC...but I have had reasons to run in this configuration MANY times over the years. and BTW...I figured out what was happening. The PermGen space was being exhausted (by the memory hungry application)...so increasing the permgen space

Multiple Mid-Tier, single Tomcat

PermGen is for long term storage, ie class file definitions, and I thought (but am not sure) that the memory would be shared between different classloader and hence web applications. Therefore, the AR API Field class is stored once and shared between multiple Mid Tier instances. But maybe I'm