1) you had no success with windows ( https://coderanch.com/t/83869/Tomcat/Request-Tomcat-remote-machine
) so now you're trying an operating system that is known to be "less user friendly". I don't mean to start a flame war between windows/nix, but c'mon.
>> I wasn't trying to imply that I thought it would be easier on Linux than Windows, but rather that I thought I'd have more success getting some help.
2) So the trouble is not in the difference between localhost and remote access. It probably has to do with how you've configured JK. This is known to be a tricky thing for many.
>> As it stands now, yes, that is my problem; I can get access to the Apache content from an internet connection (www.mysite.com) and I can access the Tomcat content locally through the mod_jk connector (http://localhost/myApp/hello
). I'm dead in the water with the next step; accessing Tomcat through Apache using the mod_jk connector (www.mysite.com/myApp/hello). I'm looking for some help/feedback regarding issues with the mod_jk configuration.
3) It's inappropriate to even suggest you need a full-blown J2EE container. If you're not writing EJBs, then stick with Tomcat.
>> I asked this question because J2EE was suggested. As I mentioned, I only just learned this stuff in school (programming side) and, based on the lack of information out there regarding configuration of internet access to Tomcat content, my thinking was that Tomcat might be used primarily as a development tool, and therefore I wanted some clarification. Your answer clarified that and I appreciate your feedback.
4) 8080 through the firewall??? Where in this url do you see 8080? http://www.mysite.com/myApp/hello...Perhaps
that was in reference to what you had tried in the very first post (testing tomcat stand-alone).
>> Yes, you're right. Originally, I just tried gaining access to the Tomcat content directly. However, after trying and not having any success, I installed the mod_jk connector. As I mentioned above, this is where I'm at now, however I can't get the internet access to work (www.mysite.com/myApp/hello). This is where I need some help/suggestions.
5) Redhat has its own particular flavour of Apache installed....
>> When I installed Linux, I did not install any of the web server components. I downloaded Apache from their site and installed.
6) At this point, are you willing to try Tomcat stand-alone? From my own experience, it seems easier to get Tomcat working, and then add apache in front, after the fact.
>> I tried that. I installed Linux, then installed, configured and tested Tomcat. I got it working on http://localhost:8080/myApp/hello
but was unable to get the internet access to work (www.mysite.com/myApp/hello). At that point, I installed Apache, tested it to make sure I could access the machine remotely (www.mysite.com). When this worked, I realized that my problem is with configuring the remote access to Tomcat. It was at this point, I installed the mod_jk connector and that brings me to where I am today.
I guess I'm guilty of not articulating my situation clearly. If I've offended/frustrated anyone by my choice of wording or the way I've described my situation, I'm sorry; it was not intentional.
Once again, if anyone can help me out, I'd appreciate it greatly. Thank you. David.