tag:help-archives.hannonhill.com,2010-02-09:/discussions/installation/1219-custom-install-questionsCascade CMS: Discussion 2014-05-23T16:17:48Ztag:help-archives.hannonhill.com,2010-02-09:Comment/267931422013-05-13T20:27:23Z2013-05-13T20:27:39Zcustom install questions<div><p>#1. That sounds accurate. I've not used the native libraries for
Tomcat but it makes sense that you would use their keystore model
and file locations as opposed to the JRE's default. We do all SSL
at the Apache HTTP level and proxy to Tomcat over AJP.</p>
<p>#2. AJP is only necessary if you're connecting to Cascade over
the port. For example, we always put Apache in front of Tomcat in
production and use mod_proxy_ajp to proxy connections from Apache
to Tomcat. We don't specify an HTTP/HTTPS connectors in our
server.xml. <code>maxProcessors</code> was <em>deprecated</em> in
Tomcat 5.5 and removed in Tomcat 6. It can be removed from the
config.</p>
<p>#4. Can you provide any additional context around the SLF4J
logging? Offhand, I think that is informational and not a problem
at all.</p></div>Bradley Wagnertag:help-archives.hannonhill.com,2010-02-09:Comment/267931422013-05-13T21:43:21Z2013-05-13T21:43:21Zcustom install questions<div><p>#2 Is there any benefit to running a reverse proxy to Tomcat
from Apache other than the logging rather than directly accessing
it?</p>
<p>#4 That's all I see referencing SLF4J in the logs. I'm
contacting SA about if there's any SELinux complications but that's
all I see.</p></div>rreynoldstag:help-archives.hannonhill.com,2010-02-09:Comment/267931422013-05-13T22:10:16Z2013-05-13T22:10:16Zcustom install questions<div><p>#2 For us, it's logging, support for software load balancing at
the Apache level, name based virtual hosting. Personally, I also
find SSL easier to setup/maintain in Apache HTTP and have had fewer
problems in Apache with various types of encryption than I have in
Tomcat.</p></div>Bradley Wagnertag:help-archives.hannonhill.com,2010-02-09:Comment/267931422013-05-14T17:07:35Z2013-05-14T17:07:35Zcustom install questions<div><p>#4 Looking over it more, it looks like the package is missing
files to get SLF4J working. You need more files than just the API
to get it working per <a href=
"http://www.slf4j.org/codes.html#StaticLoggerBinder">http://www.slf4j.org/codes.html#StaticLoggerBinder</a>
page. If that doesn't bother you it doesn't me either.</p></div>rreynoldstag:help-archives.hannonhill.com,2010-02-09:Comment/267931422013-05-14T17:16:44Z2013-05-14T17:16:44Zcustom install questions<div><p>We're loading the other JARs from our webapp's WEB-INF/lib
directory. Specifically, the slf4j-log4j12-1.6.0.jar. That's why I
was curious where in the log file you were seeing those warnings.
Could you attach the log that contains them?</p></div>Bradley Wagnertag:help-archives.hannonhill.com,2010-02-09:Comment/267931422013-05-14T17:50:43Z2013-05-14T17:50:43Zcustom install questions<div><p>Here it is.<br>
I can also add log4j12-1.5.8.jar, api-1.5.8.jar,
log4j-over-slf4j-1.5.8.jar from my rhel libraries in the
cascade/lib directory. I've been trying to use those whenever
possible.</p></div>rreynoldstag:help-archives.hannonhill.com,2010-02-09:Comment/267931422013-05-16T18:49:43Z2013-05-16T18:49:43Zcustom install questions<div><p>Alright. It does look like it loads in the webapps directory. If
I add it to the classpath it will error out finding multiple
versions. If I take away the api from the lib directory it'll error
out from missing a class.</p>
<p>I'm guessing adding it as an api in the tomcat libs is a stopgap
to load some expected classes.</p></div>rreynoldstag:help-archives.hannonhill.com,2010-02-09:Comment/267931422014-05-23T16:17:44Z2014-05-23T16:17:44Zcustom install questions<div><p>A quick update here: as of Cascade Server 7.10.2, we're loading
all of these caching and logging libraries from our webapp and are
no longer seeing these warnings from slf4j. Please give this a shot
when you get a chance.</p>
<p>I think that's the last of the questions here.</p></div>Bradley Wagner