Yes, that helps considerably. 2009/10/1 Daniel Wittenberg <dwittenberg2...@gmail.com>: >>> Daniel Wittenberg wrote: > tomcat5-5.5.23-0jpp.7.el5_3.2
Great. Not the most up-to-date, but at least 5.5.23 isn't *too* ancient :-). > INFO: The Apache Tomcat Native library which allows optimal performance > in production environments was not found on the > java.library.path: > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/../lib/amd64:/opt/oracle/lib:/usr/lib:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib Not a problem, Tomcat will run fine without it. > WARNING: A docBase /var/lib/tomcat5/webapps/rhn inside the host appBase > has been specified, and will be ignored That's some very poor configuration somewhere in your conf/server.xml - if that's the CentOS default, then some packager needs their wrists slapping. Hard. > Sep 30, 2009 8:13:08 PM org.apache.catalina.loader.WebappClassLoader > validateJarFile > INFO: > validateJarFile(/usr/share/tomcat5/webapps/rhn/WEB-INF/lib/jspapi.jar) - > jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: > javax/servlet/jsp/JspPage.class Same again - if rhn is a RedHat-supplied app, including the API jars is Very Poor Practise. Tomcat's smart enough to ignore them, but it's a good indication that whoever wrote this didn't know what they were doing. > Sep 30, 2009 8:13:44 PM com.mchange.v2.resourcepool.BasicResourcePool > $AcquireTask run > WARNING: com.mchange.v2.resourcepool.BasicResourcePool > $acquiret...@60ab835a -- Acquisition Attempt Failed!!! Clearing pending > acquires. While trying to acquire a needed new resource, we failed to > succeed more than the maximum number of allowed acquisition attempts > (30). Looks like the app's using c3p0 connection pooling. I think that's a consequence of... > 2009-09-30 20:13:44,630 [main] WARN org.hibernate.cfg.SettingsFactory - > Could not obtain connection metadata > java.sql.SQLException: Connections could not be acquired from the > underlying database! > at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:104) [...] > at > com.redhat.rhn.common.hibernate.ConnectionManager.createSessionFactory(ConnectionManager.java:173) That's the rhn app being unable to get hold of a database connection, probably because you haven't configured one. Do you need this app or can you bin it? > Looks like the only ports it's opening is 8080: > # netstat -nap |grep -i listen > tcp 0 0 :::8080 :::* > LISTEN 2651/java Then I'm very worried, as you should at least have a shutdown port (usually 8005). Could you post your conf/server.xml here, preferably with comments stripped and any sensitive hostnames, usernames and passwords blanked? That would tell us a lot more. You might have to hunt for it, but it should be a file called server.xml *somewhere* on your system! It looks like Spacewalk is trying to talk from Apache httpd to Tomcat via AJP (which uses port 8009), but Tomcat's not configured with an AJP connector to listen on 8009. That would certainly give the symptoms you're observing. - Peter --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
