I expect this was just a thing we overlooked, but we didn't initially catch on to the fact that tomcat-cp-conf has, it seems, no significance if you are running windows. We only cottoned onto this by using jstat (as SYSTEM, not that straightforward when you are logged in as luminis admin) to look at our tomcat cp process memory usage. It was using the default out of the box tomcat values (64MB permGen space). Evidently it was just not using tomcat-cp-conf. We checked with sungard who explained that you should use the tomcatcpw GUI to admin your Java environment options. Well, that fixed the issue of running out of permGen space (imagine a techie praying hard at this point). Now, I'm sure no-one else would make this mistake of thinking tomcat-cp-conf would set Windows Java Options but just in case I thought I'd put it in my blog.....
Recent comments
51 min 49 sec ago
2 days 20 min ago
2 days 3 hours ago
2 days 4 hours ago
2 days 4 hours ago
2 days 4 hours ago
2 days 5 hours ago
2 days 9 hours ago
2 days 12 hours ago
2 days 23 hours ago