I am having an issue running a custom JSP page on my server, it just displays the source code. It appears like the server is
serving the JSP file as text/plain, with no JSP processing, and without telling the browser that it's actually html.
Here is some information I have on hand not sure how useful it is:
- ran /usr/sbin/httpd2 -M and mod_jk is loaded on the server
- ran /usr/sbin/httpd2 -l and it returned:
Compiled in modules:
- ran ps aux | grep -i tomcat and the process was running
- apache: 2.2.15
- tomcat: 6.0.29
- OpenSuse 11.4
- Linux version 2.6.34-12-desktop
I have been stuck at this point for quite some time and am not sure what steps to take to try and resolve this. Any help would be much appreciated!
The details of how the server was put together are probably not important here, if you're seeing the original JSP text come back to the browser. What we need to determine is why the identity of the JSP isn't properly known.
First question is how you deployed said JSP. Are you set up as a proper J2EE webapp with the JSP in a WAR?
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Aug 16, 2011
Thanks for the quick response. I am just loading the jsp file manually through apache by using jkmount.
J2EE is not quite as slapdash as ASP where you can just throw a page at the server and it runs. There are certain architectural requirements for J2EE web applications. On the other hand, there's a reason why ASP is J2EE is one of the preferred platforms for industrial-strength webapps.