Warm Regards,
Jordan Michaels
The config also sets up a mod_jk log file that is set to log to the same
directory as your Apache logs.
/var/log/apache2/mod_jk.log (ubuntu) or /var/log/httpd/mod_jk.log (rhel)
I'd check that log or the Apache error log to see what's causing the
current 500 error.
HTH!
Warm Regards,
Jordan Michaels
At any rate, the one thing I should probably change about the
installer's methods is that it uses Tomcat's default worker, named
ajp13. This worker is only created when there's no worker config file
(workers.properties) and I'm guessing that you installing your own
version of mod_jk there was a workers.properties file.
I guess the question you should be asking yourself is if you wanted to
stick with the installer's mod_jk install or proceed configuring it
yourself. Either way will work and I'll be happy to help you, but you'll
need to pick one so they don't trample on each other.
Warm Regards,
Jordan Michaels
Now you just need to update the mod_jk config to apply to your CFML
requests.
Open the /etc/apache2/apache2.conf file and at the very bottom you'll
see this:
<IfModule mod_jk.c>
JkMount /*.cfm ajp13
JkMount /*.cfc ajp13
JkMount /*.do ajp13
JkMount /*.jsp ajp13
JkMount /*.cfchart ajp13
etc.....
</IfModule>
Change all those "ajp13's" to "ajp13_worker" and then restart Apache.
Your workers.properties file is already pointing to port 8009 which is
what Railo's Tomcat should be listening on.
If it doesn't work, we can do away with all the extra fluff and just
stick with the installer's config.
Let us know how it works!
Warm Regards,
Jordan Michaels
You can test the connection to port 8009 using "telnet" from within Ubuntu:
$ telnet localhost 8009
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
If you don't get the above, something is blocking you. If you DO get the
above, then good. =) You can exit this interface by hitting CTRL+], then
Enter, and you'll be dumped to the "telnet" prompt:
telnet> _
Type "quit" to exit telnet.
What happens when you type this below?
$ sudo iptables -L
you'll be prompted for your password but then you hopefully be shown
your firewall config. If you have a firewall in place, but aren't
allowing connections from localhost to 8009, then that's the problem
right there. ;)
Hope this helps!
Warm Regards,
Jordan Michaels
Try:
$ telnet 127.0.0.1 8009
Still work okay?
Warm Regards,
Jordan Michaels
>> read more �
I admit I'm a little stumped right now. If you're able to connect to it
from the command line, then mod_jk should be able to connect to it as well.
I wonder if there's some aspect of the config I'm not considering. Would
you be willing to tell me what tutorial you used to install mod_jk?
Maybe that'll give us some leads.
Warm Regards,
Jordan Michaels
>> read more �
Can we make sure you're working with a fresh copy of the logs? Try
removing the mod_jk.log file and restarting Apache. That should create a
fresh log file for you,
If you were tailing it, then this won't help one bit, but I want to make
sure that Tomcat is NOT able to access the AJP port while at the same
time you can access it just fine via telnet. That part totally confuses me.
Thanks!
Warm Regards,
Jordan Michaels
>> read more �
Warm Regards,
Jordan Michaels