...
[13:54:38 CST(-0600)] <dd_> yup
[13:55:42 CST(-0600)] <EricDalquist> are you on *nix? or windows?
[13:55:57 CST(-0600)] <dd_> redhat
[13:56:06 CST(-0600)] <EricDalquist> in your webapps folder
[13:56:07 CST(-0600)] <EricDalquist> run
[13:56:23 CST(-0600)] <EricDalquist> find . -name '*.xml' | xargs grep ResourceServer.cacheManager
[13:56:38 CST(-0600)] <EricDalquist> so uP 3.2.4 shipped with WebProxyPortlet 1.1.1
[13:56:45 CST(-0600)] <EricDalquist> and looking at https://source.jasig.org/portlets/WebproxyPortlet/tags/WebProxyPortlet-1.1.1/src/main/webapp/WEB-INF/applicationContext.xml
[13:56:57 CST(-0600)] <EricDalquist> the cache manager name is defined as WebProxyPortlet.CacheManager
[13:57:19 CST(-0600)] <EricDalquist> so I'm at a loss as to how/why your web proxy portlet is trying to register a cache manager in JMX with the name ResourceServer.cacheManager
[13:57:28 CST(-0600)] <dd_> ./ResourceServingWebapp/WEB-INF/applicationContext.xml: <property name="cacheManagerName" value="ResourceServer.cacheManager" />
[13:57:46 CST(-0600)] <EricDalquist> that was the only hit?
[13:57:53 CST(-0600)] <dd_> yup
[13:58:00 CST(-0600)] * EricDalquist is rather confused
[13:59:36 CST(-0600)] <EricDalquist> I'd try nuking your tomcat/work dir
[13:59:47 CST(-0600)] <EricDalquist> and then re-run "ant clean deploy-ear" in uPortal
[13:59:52 CST(-0600)] <EricDalquist> and see if that resolves this issue
[14:00:08 CST(-0600)] <dd_> what's the work directory for?
[14:00:19 CST(-0600)] <EricDalquist> it is tomcat's scratch dir
[14:00:24 CST(-0600)] <EricDalquist> JSPs get compiled there
[14:00:30 CST(-0600)] <EricDalquist> some stuff from JARs gets cached there
[14:00:35 CST(-0600)] <EricDalquist> it is 100% generated cotnent
[14:00:37 CST(-0600)] <EricDalquist> content
[14:00:41 CST(-0600)] <dd_> ok
[14:00:44 CST(-0600)] <EricDalquist> so it is safe to completely delete it
[14:22:36 CST(-0600)] <dd_> nope, same thing