I have two machines that I want to cluster, load-balance and replicate. Tomcat & Apache both start up... no errors. When I browse to the URL, the browser just shows the contents of the XML file. It doesn’t parse the file, it just displays the actual code in the browser window. Tomcat Version 6.0.18 Apache 2.2.11 Mod_jk 1.2.22 Server 2003 x64 I've attached config files... and log files my app path is: W:\Tomcat\webapps\thr3 and the files needed to be served are at: W:\Tomcat\webapps\thr3\jsp\* Anyone know why its doing this? if i browse to http://tomcat-a, it displays the actual XML code of the home.jsp file located in W:\Tomcat\webapps\thr3\jsp\. But if i manually browse to http://tomcat-a/thr3/jsp/home.jsp, then the entire website works fabulously. http://www.nabble.com/file/p22663205/tomcat-a%2Bserver.xml.txt tomcat-a+server.xml.txt http://www.nabble.com/file/p22663205/tomcat-b%2Bserver.xml.txt tomcat-b+server.xml.txt http://www.nabble.com/file/p22663205/tomcat-a%2Bhttpd.conf.txt tomcat-a+httpd.conf.txt http://www.nabble.com/file/p22663205/tomcat-b%2Bhttpd.conf.txt tomcat-b+httpd.conf.txt http://www.nabble.com/file/p22663205/%22tomcat-a%2Bworkers.properties.txt%3C%2Fnabble_a http://www.nabble.com/file/p22663205/%22tomcat-b%2Bworkers.properties.txt%3C%2Fnabble_a http://www.nabble.com/file/p22663205/%22tomcat-a%2Bcatalina.2009-03-23.log.txt%3C%2Fnabble_a http://www.nabble.com/file/p22663205/%22tomcat-b%2Bcatalina.2009-03-23.log.txt%3C%2Fnabble_a http://www.nabble.com/file/p22663205/%22tomcat-a%2Bthr3.log.txt%3C%2Fnabble_a http://www.nabble.com/file/p22663205/%22tomcat-b%2Bthr3.log.txt%3C%2Fnabble_a -- View this message in context: http://www.nabble.com/apache-XML-parsing-problem--tp22663205p22663205.html Sent from the Apache HTTP Server - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|