|
|
(EMERGENCY) ajp12: ping: no reply |
| Ok, You will get this error for a few reasons. Unfortunately, most of which can be hard to debug. I'm going to do a really good job pointing you to the reasons the error occurs and what you might be able to do about it, although, you WILL have to debug this on your own so don't go crying on the java-apache-users mailing list about this problem.
Reason Number 1 There are two parts to Apache JServ. A C portion and a Java portion. For most configurations, when Apache starts up, the C portion (mod_jserv) attempts to also start up the Java portion (the JVM). The C portion communicatates with the Java portion via a protocol called ajpv12. If the C portion is not able to start up the Java portion and then "ping" it, then you will get this error. Essentially, what is happening is that the Java portion just won't start up. This is 99% of the time due to a configuration or setup error on your part. The first thing to do is to make 100% sure that all the paths in all your configuration files are correct. If anything is wrong, the Java portion will not start. The next thing to do is to make 100% sure that your log files, there are TWO of them, can be written to by the process that the httpd is running as (generally this is "nobody"). chown the files to be owned by nobody or make them writtable by everybody. If Apache JServ cannot write to these files, then nothing will be logged and you will be at a loss. We can't show you any errors because we don't ahve permissions to! If you think that you have all of the above correct AND you are still getting this error, GO BACK AND CHECK AGAIN!!!!!
Reason Number 2
Reason Number 3
Reason Number 4 | |
| [Append to This Answer] |
| Previous: |
|
| Next: |
|
| ||||||||||